Hi @avatarlucas
I let you know this issue has been fixed in VisualARQ 3.11 RC2: VisualARQ 3 - Version 3.11 RC2 released