Why is cmdagent is using a lot of my CPU?

I have an i5 processor with 16gb RAM with Windows 7 PRO. I notice from time to time, my PC will slow to a crawl and when I check task manager, I see cmdagent using from 25-50% of my CPU. Why is this and what can be done to correct it?

What version of CIS are you using?

As always make sure there are no leftovers of security programs you had installed in the past. A possible left over can cause all sort of “strange effects”. Please run clean up tools for all security programs you had in the past. A list can be found here at the Eset website: ESET Knowledgebase .

What other security programs do you have installed and which one(s) are running in the background alongside CIS? One of them might be interfering.

I have MalwareBytes Pro, CCleaner Pro, WinPatrol Pro and Advanced System Care Ultimate.

What version of CIS are you using?

Please try adding the folders of all three programs to the exclusions of the AV real time shield.

Also try adding the CIS installation folders to the exlcusions of MBAM Pro.

Does that make a difference? When that doesn’t help could you post a screenshot of the D+ logs?

Thank you for taking the time to reply. I am actually quite put out with CIS at the moment. I’ve been struggling with this problem, plus another I have posted in the Bug forum, for quite a number of days. I am a very long time user of CIS, plus the above mentioned programs and Firefox, and have recommended CIS for years to my clients. As of this morning, I disabled CIS and installed another anti-virus and firewall for testing. After doing so, I re-booted and immediately noticed an increased speed in which Windows loads. To be sure, I re-booted again and again and my Windows is very much faster. I will monitor my system for a few more days, perhaps a week, and see what happens. I am not inclined to do any more trouble shooting and trials with CIS. I will keep open the option to remove CIS.

Thanks to all for your input.

Sorry to see you go.

It is a common practice to mutually exclude them when having two anti malware solutions monitoring on access to prevent performance issues.

A bug will not get fixed within a couple of days. A bug report goes through a process of getting a proper bug report, Comodo QA trying to reproduce the problem and when needed contacting the reporter for more information, then its gets prioritized, etc…

It pains me to end it like this, especially after all we’ve been through all these years! But I guess there comes a point in time when one must move on. It seems as if we are no longer compatible. I’ve met someone else who is meeting my needs so I guess this is it. CIS, I wish you the best.