Hi,
So yesterday, I decided I would finally make the switch from v5.x to v6.x.
I did a complete uninstall of v5 (using the removal tool afterwards as well) before installing v6, so hopefully that isn’t causing any problems.
I’m having two main issues right now, the first being relatively less important than the second.
First, the GUI is rather sluggish for me. It takes about 10-20 seconds to open the main GUI from the tray icon, and another 10-20 seconds each to open any of the settings windows. (Sometimes I have to click twice, since it seems that it doesn’t “notice” the first click – but maybe that’s just a mistake on my part.)
Second, whenever a HIPS/Defense+ alert pops up and I have it set to remember my answer, it takes forever for it to actually “remember my answer” before continuing on. This behavior does not occur when the “Remember my answer” box is unchecked, nor does it seem to occur with firewall alerts (regardless of whether the box is checked or not).
I used Process Explorer to look at what’s going on, and this is what I have found to happen:
[ol]- Program does something that would trigger an alert from Defense+.
- The cis.exe process (one of them, at least
) briefly spikes to around 30% CPU (probably to load the alert message or something) and then the alert pops up.
- I check “Remember my answer” and respond to the alert.
- The cmdagent.exe process goes up to around 30% CPU for about 3-5 seconds, then returns to normal (0%).
- Immediately afterwards, the “System” process goes up to around 20-40% CPU (it fluctuates between those values). When I right-click the process in Process Explorer and look at the threads it’s running, I see that the thread for cmdguard.sys is responsible for this CPU usage. This continues for about 50-60 seconds (!) before going back to normal. (The program that triggered the alert is still frozen during this time)
- As the System process is finishing up whatever it’s doing, the CPU usage of the process that triggered the alert goes up to about 30-40% for another 10-15 seconds before going back to normal and then continuing its execution.[/ol]
Some general info about my configuration:
I run Windows XP SP3 (32-bit) on a netbook (1.6 GHz Intel Atom processor, 2 GB RAM – so yeah, it’s not exactly the fastest thing).
I use Comodo only for firewall & HIPS (the antivirus component is not installed).
I use MSE as my antivirus (I added the Comodo processes to the exceptions list already. I’ve also tried disabling MSE, but that doesn’t seem to have any effect whatsoever on the behavior described above.).
I removed all traces of any previous security software way back when I uninstalled them using both their uninstallers and their removal tools, so that (hopefully) shouldn’t be causing any problems.
As far as the actual configuration for Comodo, I have it set to the Proactive Security configuration.
Both the firewall and HIPS are set to Safe Mode.
I currently have very few rules set for either (I opted to start fresh instead of importing my old v5 configuration).
I disabled auto-sandbox (I prefer to use Sandboxie).
I also disabled Enhanced Protection Mode to see if it would make any difference (it didn’t).
Any ideas what’s going on here?
(On a side note, why am I getting so many more “direct disk access” alerts than I did with v5?)