Hi Dan, we have just released VisualARQ 2.10, which fixes this error: VisualARQ 2 - Version 2.10 released