This issue has been fixed in the EzeScan 4.2.34 EzeScan Patch.

To fix this issue please upgrade your EzeScan installation to this version (or higher).

If the isse is still occuring after the upgrade please contact us for further assistance.

Direct link to FAQ