After a month of using the latest version of CIS, today I ran into this problem: when I try to reset the Sandbox it gets stuck. Basically, it just keeps trying to reset it forever and goes nowhere; if I look within CIS’ Task Manager it shows the Reset Sandbox task status as “Starting”, even if it has been running for an hour. This happens every time a sandbox reset is attempted, even after rebooting and even after complete uninstallation & reinstallation of CIS.
It seems this issue has been reported as a bug already by the above two thread starters. However my issue seems different in the sense that even a reinstallation does not help. Does anyone have any ideas? How can I figure out what causes this problem? Thanks.
Edit: to add some details, I’m using Windows 8.1
When I uninstalled CIS I simply used the “remove programs” feature by Windows… Is there a specific clean-up program I should use to remove Comodo files with? And until I figure out how to fix the issue, is there a “manual” way to reset the sandbox so that I could keep using my browsers sandboxed?
Edit 2: These keep appearing in my Event Viewer (under ‘Security’ category) and I’m wondering if there’s a connection:
"Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
I followed your advice: skipping the first two programs (because I have a 64 system, and Windows 8.1), uninstalled CIS using the Windows remove programs feature and then rebooted to safe mode to use the CIS Removal Tool.
After reinstalling CIS, however, I’m still faced with the same issue. Sandbox will not reset.
Thanks for the tip. However, it didn’t help. The problem still persists.
EricJH, do you think it’s possible that this entry in my event logs might have something to do with the issue?
""Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
Someone told me it could be a compatibility issue between CIS and Windows 8’s own security program, but I was under the impression that CIS was supposed to be Win 8 compatible.