Hi @jfernand15,
This bug is already fixed in VisualARQ 2.1.2, which has been just released:
Regards,
Enric