If you could read, you’d realize I reported the problems, but the only suggestions I ever got were to uninstall other security apps that I had running on my systems. Well guess what? I’m not willing to do that to make Comodo work properly when it’s not necessary for other security suites. BTW, the other security apps I had running were Microsoft Security Essentials and Secunia PSI. I had CIS’s antivirus turned off, so there should be no conflict between the remaining CIS components and MSSE. If there is, it’s just an indication that CIS needs work to be able to coexist with other apps. Spend a little time with Google, and you’ll find comments all over the web about how CIS is a resource hog and conflicts with many other apps.
Specifically, the most significant problem I had was with cfp.exe and cmdagent.exe using excessive amounts of CPU cycles for no apparent reason. The only suggestions for resolving this I ever got were to exclude the CIS processes in MSSE, which I did (it helped for a while, but the problem returned), and to uninstall MSSE. Since MSSE works fine, and it caught some malware that CIS didn’t (when I still had the CIS antivirus turned on), and since excluding the CIS processes in MSSE helped, but didn’t eliminate the problem even with the CIS antivirus turned off, I wasn’t willing to uninstall an app that was working well to try to get CIS to work right. On top of that, CIS antivirus apparently cannot clean an infected file, since the only actions it ever offers when it finds an infection are to quarantine the file or to delete it. MSSE successfully removes malware from most infected files leaving the file intact and usable. Even PC Magazine’s Neal Rubenking said, “Comodo Internet Security’s antivirus scanner recognizes most threats, but fails to remove them properly.”
Try searching the Comodo forums for “cfp cpu” and “cmdagent cpu”. There are close to 100 posts dating from 2006 through Feb. 2011 complaining of high cpu usage for these two processes. Even if these could all be resolved by removing some other company’s software, it’s a very strong indication that CIS has a problem, and since other security suites are able to run well in the exact same environment, Comodo should take a good, hard look at both the software and their user support policies. When there are a significant number of users reporting the same problem over a period of at least five years, there’s something that isn’t right, and trying to blame other software for the problem just doesn’t cut it.
moan all you want, but it’s very clear to me, and apparently lots of other folks that have tried using CIS, it takes a very specific software environment for CIS to run well, and most computers don’t match up with those requirements. If it works well for you, that’s great. If you’re willing to turn your computer inside out to get it to work right, that’s fine too. Most users aren’t willing to do that. I’m not willing to do that. Instead of uninstalling other software to try to get CIS to run without hogging resources on my computer, it made a lot more sense to me to get rid of the software causing the problems, CIS, and replace it with another security suite that runs well and doesn’t hog resources in the exact same environment. I can even run Outpost with its antivirus enabled and MSSE at the same time with no resource problems. I’m still looking around for another suite that’s more to my liking and is low on resource usage, like Outpost. If Comodo decides to fix the CIS resource usage levels and improve its ability to clean malware from files while leaving the file intact, I’d be happy to give it another try.
Feel free to continue dissing me in this thread, as I won’t be looking at it again, since all you’re willing to do is criticize users who aren’t willing to mess up their computer configuration to compensate for CIS bugs and incompatibilities. Your hostile reactions to my post make me realize that this “community of users” isn’t as benevolent as it makes itself out to be.
Edited to remove language
