continous harddisk-access of cmdagent.exe


I get continous harddisk-access of cmdagent.exe:

Defense is disabled and the even if I set the firewall to disabled, the disk-access occur.

What can I do to stop this?

Thank you!

Bye, MK

Has nobody an idea? This might probably kill our SSD’s over time… :frowning:

I have the same problem, my HD light blinks constantly without interruption, and Process Monitor show hundreds of disk accesses per second by cmdagent.exe.

Please, anyone got a clue, otherwise i have to dump Comodo, it’s not worth killing your HD’s.

cmdagent is the service so you would need press on the start buttom and then write service.msc, here you click on cmdagent and right click and select properties and then select manual or disable.

Keep in mind that this will disable the complete CIS in worst scenario; as far as I know cmdagent.exe responsible for all the components.

Thanks Valentin, but how do i have to address this so called instructions ? There’s obviously something awfully wrong with the way comodo handles disk storage.

The answer you gave me is like asking the instructions how i can travel to Jupiter and getting an answer back on how to get to the toilet instead.

This video might help to understand the instruction above.

I don’t know how cmdagent.exe works but disabling d+ or the firewall wont’t disable cmdagent.exe from running.

So, the only way to get rid of the continious disk activity by cmdagent.exe is to turn of the Comodo Internet Security Helper Service, meaning switching OFF comodo completely. Thanks, i better just uninstall it then.
Might be a cleaner way of getting rid of it.
Thanks anyway.

This is definately not default behavior, does this end if you switch AV to disabled?
What other security software(s) do you have installed? no matter real-time or on-demand.

Can you provide me with a procmon log for about a few minutes with all processes in it so see if that tells what’s causing this?

Hi Ronny,

I don’t have Comodo’s AV installed, i only have the firewall & defence+ modules active, all comodo sandbox is off.
The only other security tool i use is Panda Cloud Antivirus Free. Disabling Panda doesn’t change anything to the disk io caused by cmdagent.exe.

I send you the procmon log file via PM.

Thanks for all help so far Ronny & Valentin. :slight_smile:

Please send me a PM with a download link, maybe I can find a clue in there.



same problem here. WinXP pro machine, 1+Gb RAM.
Firewall running, antivirus not running.
I have the impression this started after one of MS security updates. Anyway, cmdagent.exe can use up to 100% of CPU, with continous disk access for a very long time, even when there is no other activity. And it also uses half or more of available RAM which apparently cannot be released/reallocated later. Result: the machine slooooooows down, freezes, sometimes picks up by itself, most of the times turns off randomly.

I will have to uninstall soon if I don’t find a solution.

Thanks, bye


Hi Max-1,

Welcome to the forums!
Can you check if setting Defense+, Settings, Disable Defense+ permanently and then reboot solves this issue?
Even if you install only firewall with leak-detection it will monitor executions and verify them in the cloud to see if they are malicious or not this might cause the explained issues.


Same problem on my Xp. Running AV + Defence+ , no FW.
Cmdagent.exe takes up to 100%CPU and lota RAM, stops randomly, apparently.

Issue started after I’ve clone my SYS HDD.

Can you go to ‘More’ and Run ‘Diagnostics’ to see if it finds anything?

The diagnostic didn’t find any problems.

Checking Computer Management/Event View/Application log I discovered som errors, avrg. 3 by a boot, mainly concerning COM+, errors that wasn’t there until the day I made clon of my sys HD to a new HD device.

There was no HD r/w and cpu overload from Comodo before this date, so I don’t know what came first.
My “old” sys HD is still connected, I can hear its activity during the booting, but after win is started and running there is only the sound of the new HD operation.

I plan to disconnect the old HD, but I don’t think sys drive swap is the reason. It can be coincidental.

Would it be still possible to boot from the old drive and see if the problem is still there?