@Toni_Osterlund we have officially released VisualARQ 2.10 that fixes this error: VisualARQ 2 - Version 2.10 released