CIS is significantly slowing down my entire system

The developers picked their cutoff based on real-world malware. !ot!

It was never my intention and I believe I didn’t write anywhere anything like that.
Still I appologize, I just wanted to help.
I am withdrawing from this correspondence. :-X

Very well then… I trust their judgment :slight_smile: :-TU
I was going with the usability approach since scanning such large files are taxing his HDD, and this was a try on a temporary time, not something he would keep forever. I just wanted to see if it’s gonna ease up the machine a little bit…

It did help.

Try turning the AV heuristics to OFF. lets see if that has any performance boost…

May be left overs of previously installed security programs are in the way. Try using removal tools for those programs. Here is a list of removal tools for common av programs: ESET Knowledgebase .

Otherwise do a Google search with terms “removal tool” and * name of product or vendor*.

Does this help or does the situation stay the same?

To take another angle. Do you defragment your system on a regular basis? If not, please defragment it and see if that brings any change.

Maybe it’s left overs from previous CIS installs? I found 5 Comodo drivers still installed on my W7 x64 Home Premium machine, and this was AFTER using the unofficial uninstall tool after a standard uninstall via programs and features.;msg529511#msg529511

There aren’t leftovers, this is happening even on freshly installed system.

I think the best “solution” in this case is to dump cmdagent’s memory and send this dump directly to developers. I’ve seen cases when cmdagent cpu usage skyrocketed to 100% while it’s trying to scan (?) some very particular file. Very frustrating, but nearly non-reproduceable on another system with no such file.

not sure what a N00B (with zeros) or an NOOB (with letter O’s) is?
perhaps computer “lingo” of which as an old person am not familiar

And cerainly don’t want to insult any body. But can only say that also had to give up the new version of the program, since it persisted with the cmdagent using 50 to 60 per cent of the machine. Am hoping that the new version you mention nr. 5.8 maybe has fixed that, and eager to retry since otherwise an excellent program. I became so familiar with all its functions that hated to have to give it up.