Hi @jerry.bakowski, I’m glad to say we have fixed this issue in VisualARQ 2.11, just released!
VisualARQ 2 - Version 2.11 released