@11181 This bug has been fixed in VisualARQ 2.3, that is already available to download. VisualARQ 2 - Version 2.3 released