I had this problem also.
After I uninstalled comodo and restarted everything went fine.
I think this has something to do with the logs from firefox.exe…
If someone can figure out how to stop comodo from logging the whole profile for firefox then it’ll run just fine.
cmdagent.exe is a Comodo Agent Service from Comodo belonging to Comodo Firewall cmdagent.exe is located in a subfolder of “C:\Program Files” or sometimes in a subfolder of C:. Known file sizes on Windows XP are 361040 bytes (75% of all occurrence), 495360 bytes, 565840 bytes, 536576 bytes, 544512 bytes, 569936 bytes, 356944 bytes.
The program has no visible window. The file is not a Windows core file. The file is digitally signed. cmdagent.exe is able to record inputs, monitor applications, manipulate other programs. Therefore the technical security rating is 39% dangerous, however also read the users reviews.
which version of CIS did you use? For me the version 3.5.53896.424 of CIS caused that cmdagent.exe was running 100% CPU. But I downloaded next version 3.5.54375.427 of CIS and the problem is resloved for me (so far :)) But as I have read above, this did not help some people. Give it a try.
I hope Comodo team will fix this problem soon, because this is a great firewall and I like it very much! (R)
Hi guys,
I just would like to share my experiments about the same issue. The story is the usual: I realized that cmdagent eats 100% CPU time, and system became extremly slow.
After a half day torture I found out that it was caused by a freeware application called ‘process lasso’, removing it solved my problem. If you have the same issue, maybe you also should check if you are running any process monitoring tools.
Good luck!
ps. Maybe the developers also should check how Process lasso effects cmdagent.
Actually I’m not sure about the version but I believe it was automatically updated to the latest version as of nov 14.
I ended up removing that copy and installing the very latest off the comodo website. Initially the cmdagent.exe took up my cpu time again - even though the winxp automatic update shield was not visible - but after disabling cmdagent from the comodo config (as detailed in this thread) the cpu use went down and did not start again when the winxp automatic update shield showed up again.
SO right now everything is fine. Automatic update worked fine. No cpu hogging. Does not seem to be related to automatic update, at least superficially.
HOWEVER - When I uninstalled comodo firewall, what happened to the quarantined malware I had in comodo’s care???
Do the quarantined files become loose on my hard drive???
I am not going to close this thread & mark it as resolved. Anyone that has not installed the .432 build please do so. Jeremy if it does get major please post a separate bug report.
Thanks for unlocking the topic. I had actually had this problem resolved for 3-weeks now. Windows Updates and Windows Firewall was turned off, and it seemed to be working fine. Then just out of the blue, 99% CPU all over again. I reinstalled Comodo and it did the same thing.
Basically the fix was temporary since whatever is causing it has started up all over again, even with both Windows Updates and Windows Firewall off… :???:
I have downgraded to 3.0.24.368 now and the problem has ceased for the time being. I do hope you guys manage to figure this one out though. I have wondered if this is a form of attack against Comodo, perhaps remote buffer overflow or something that would make the cmdagent.exe act like a CPU hog?
I’ve been using Comodo for some weeks now without any problem. Today, I had the unpleasant surprise of watching cmdagent.exe take control of my computer. I don’t know why. After almost uninstalling it for good, so angry I got, I decided to disable the Defense+ feature and it seems it did the trick. So far, no more misbehavioring comodo agent. I don’t care not having the Defense+ feature, it is confusing anyway imo, I do like the firewall though.
I’m using the latest version, 3.5.xxxxxx.432 so I guess the bug is not fixed. At first, I thought the cause could be because I had around 18k files “waiting for my review” and then I cleaned the list, but the bug didn’t go away. It would not use 100% of my CPU (a Pentium 4 3.2GHz), it would use around 50%, the computer was still responsive but much slower than usual. Trying to open Comodo was impossible, right-clicking on the tray icon was no good, no context menu would popup, Comodo was the one actually frozen. I tried to end the process using Task Bar but it’s impossible, which made me much angrier because I hate apps that don’t allow being terminated. I am the one in command, I should know when I want a program terminated or not. After a while, it could be 5 minutes or 30 minutes, the cmd agent would return to normal behavior automagically but soon to become crazy again.
So, without the Defense+ feature, it seems there is no bug. With it, it is still there.
I have version .439 and it was working fine until I installed the Comodo update this morning. Then cmdagent.exe took over the machine. I finally had to use system restore thru msconfig to restore it to yesterday’s setting. The problem is resolved, but everytime I start the machine a Comodo pop up wants me to install the update. The update notes specifically stated that it resolved the cmdagent problem with Firefox which I use. It does not resolve the problem, it makes it worse. Any suggestions?
The latest version is .439, You need to reinstall CIS to solve the update issue… You can also export & save your settings via Miscellaneous>Manage My Configurations>Export & Import the same way when you reinstall.
