@Ben_B This issue has been fixed in the VisualARQ 3.4 RC1 version, which is available to download here: VisualARQ 3 - Version 3.4 RC1 released
@Ben_B This issue has been fixed in the VisualARQ 3.4 RC1 version, which is available to download here: VisualARQ 3 - Version 3.4 RC1 released