@seflorance this issue has been fixed in VisualARQ 2.8.5 version: VisualARQ 2 - Version 2.8.5 released