Hello, This issue has been fixed in VisualARQ 2.4 that is already available to download: VisualARQ 2 - Version 2.4 released