A lot of things haven’t been updated in years though projects like Comodo Dragon has been consistently updated. CIS/CF .8012 still works flawlessly against even the latest ransomeware and viruses, particularly when tweaked and I don’t have issues with it in WIn11.
You have the option to install either Firewall or Antivirus or both in the Beta installer. Current beta does leave behind some remnants which the devs are looking into.
I’ve seen it mentioned numerous times but everyone’s setup is different. If your using Windows 11 CF isn’t officially supported for it, if your using Win 7 you need to have the SP1 & 2 installed, system hardening applications can conflict with CF.
We all hope for some improvements and I’m glad to see we’ve had a couple of Betas but if your that frustrated, try out other products, there are plenty out there but unless people continue to provide information the better @C.O.M.O.D.O_RT@ilgaz and devs can identify it. They fixed a handful of things in the betas so far so it could be something that is in the beta roadmap.
There’s probably something triggering the high CPU but only by looking at CF and windows logs can it be narrowed down to what the cause is.
(points are important, because I want answer to every thing I mention in my post, not skip some important informations) - why for so many years people complain about the same problem again and again? If it depends on some specific Windows settings, then Comodo should fix it years ago. Still people reports high cpu usage of cmdagent.exe and you’re trying to find problem on my computer, like it was some single case, not seen or reported before. Wrong.
For all that years - are people sending their Windows logs and sharing lot of data? I think yes. So why problem is still not solved for over 10 years? I want to know WHAT CAUSES the problem (from programmer) and when it was fixed. It’s not user’s task to fix Comodo code.
Where is that beta installer? And if I choose to install just firewall, I will have ONLY firewall installed, or whole Internet Security but with disabled/not installed AV? I don’t want to be constantly nagging about “you’re in risk” mark because I have no AV installed. I want ONLY firewall.
Again, I can repeat this again and again - WHAT HAPPENS with all other reports about cmdagent.exe CPU usage? Why I should provide any data if problem is not new? I just asking about final solution after MANY YEARS (which I proved by searching for this problem on internet and check dates).
Fine. There have been lots of posts about High CPU usage all varying in which components users have enabled. Some provided detailed information and others haven’t.
As @Melih Melih has indicated, Windows coding has changed all the time. CF/CIS whitelists Microsoft’s system files but has you aren’t using File Rating, it’s possible your firewall rules are to strict for system processes or something else. You haven’t provided any information to which OS your using.
The Devs assist where possible but 10 years ago 8.1 was released and the current beta doesn’t support it. I found no issues with CF/CIS when using Windows 10 but developers have tried to assist in the users in all this time and CIS/CF has come a long way since 8.2. What version are you using? Did version 12.2.7062 resolve your issue when you initially posted about high cpu in 2020?
We await either further information from you. If the Beta doesn’t resolve the issue, please post in the Beta topic so the Devs can pick it up.
My version is 12.2.2.7036 - I reverted to that version since update (using Comodo update) causes much more frequent freezes.
I was not asking about “do I must install AV module”. I was asking if I install ONLY firewall, it will be only firewall or Comodo Internet Security without installed AV? It’s big difference.
For now my window looks like that (I like this classic skin). As you see - no “AV missing”, no" At Risk" etc. No space for installing AV module. On the left you can see only Auto-Containment, HIPS and VirusScope, no AV section (even not installed).
I know that there was two type of Comodo Installers - one with name “cmd_fw_installer…” and one with name “cis…” as prefix.
I installed once that Security without Firewall and it was not what I wanted. It contains showing me info that I am not fully protected and that AV module is not installed. Firewall (only) do not do that.
So - again - since you don’t use only firewall - are you absolutely sure that this beta, when I do not select AV module, will install me ONLY firewall WITHOUT option to install AV later etc?
Thank you for the additional information. I’m in between testing installs so I will install it at my end as firewall only when I get a minute.
High CPU is no 40 on the 2021 Current Bugs list: https://forums.comodo.com/t/list-of-current-bugs/320077 but they are checking and working through these as they release the Betas. High CPU hasn’t so far been mentioned in the Beta Release topics.
But is again and again repeating bug reported so many times. That means nobody yet find real cause what is wrong with cmdagent.exe and high CPU usage. All workarounds may work from time to time, but it’s like in case all bad coding - it will work sometimes, but sooner or later bug will reveal itself. Testing in short period of time in perfect conditions (few programs installed, default system settings) is never good.
I’m not a Dev or Comodo Staff, I’m just a volunteer moderator and long time Comodo user, here to help out where I can. It’s late here but off work this week so should have time to install CF Beta.
The Beta Installs the whole CIS but only the CF activated. You have to manually disable everything else including miscellaneous and web filtering, hips etc
Ok, today I had over 90% of CPU after whole day of working.
By “working” I mean A LOT - lot of programs running, lot of internet connection, heavy stuff whole day.
And I decided to kill everything that may cause this problem.
NOTHING - I kill basically everything includin explorer (so my desktop disappear) - still cmdagent.exe was at 90% and higher and only PC restart helps. What a $#!#^!
Believe me if I tell you that it’s programmer’s fault. Too many THE SAME or similar reports over YEARS. Comodo just doesn’t care so much - and because most of people do not complain (or knows that it’s pointless because they may end in endless forum discussion about “everything works fine, please try…”) this problem probably will stay as long as someone find big leak/bug in code and write article that CIS is dangerous. That may wake up some cprogrammer.
And I know how CIS installation works - I prefer just Firewall, not whole CIS. Without AV module installed it constantly show that computer is not protected etc. With only firewall it shows that all is ok.
And more important - it’s also matter of speed - CIS is handling every file (no matter if AV is enabled or not). Firewall just monitors internet connection since it has no AV module.
Oh, nevermind, It will be endless discussion. I know that when I’m doing almost nothing on my computer, it can runs for days without that problem. But usually my computer is heavily used. And then cmdagent.exe becomes crazy.
If you read what I wrote, you would know that I installed this new version (I compared my files to yours - I keep my downloaded files just in case) and THEN I REVERT to my older one, because this new one causes MUCH MORE FREQUENT problem with cmdagent.exe and I must restart my computer twice a day.
Also - you can’t just paste links to new version and have hope that version number changes anything unless you’re sure that this particular problem was adressed in this version. And apparently not.
No, I could not. I do not want to install again worse version.
Read whole topic and lot of other topics - as I said, lot of people had this problem for years, so probably you already have dozens of screenshots.
Or just imagine - task manager with 90% CPU on cmdagent.exe. All task managers looks similar, so…
I described everything very clear, you don’t need to look at pictures to undersand (I hope) even if my english isn’t as good as I want it to be (not my native language)…
Please, just once, focus on fixing bug in code, not on looking what may be wrong on user’s side. Unless you think Comodo code is 100% bug free and people who complain about freezing cmdagent for years are just joking.
I provided links, lot of informations, but still don’t get any serious answers - is any programmer ever trying to find cause of this? If yes - what he discovers? What he fixed? When?
You see - I also have lot of questions. I just want to be sure that someone actually works on this, not waiting until someone provide ready solution with 500% proof and slideshow.
For now my cmdagent.exe is working ok and it’s most of the time, so it’s not really easy to reproduce this bug on user’s side. I can’t. But clever programmer should be able to find a bug.
EDIT: You know, acutally I could install this version, because I am not 100% sure that my Comodo updated itself to 12.2.2.8012. I uninstall my old first and try to install this new one. I just want to be sure if it wouldn’t be waste of my time - do you have any info that between 12.2.2.7036 and 12.2.2.8012 this issue was fixed. Any changelog like “fixing problem with cmdagent.exe high CPU usage”? Because changing number version itself is not magical solution for all problems.
Release notes page: Release Notes though more things were fixed that weren’t listed. 8012 is the current stable version has has been for some time and resolved a number of issues. It’s worth trying that version so @C.O.M.O.D.O_RT can assist.
Last info about cmdagent is “Defect where ‘Cmdagent.exe’ consumes 40-50 % CPU constantly in some cases.” from version 12.0.0.6810.
Well, not fixed enough I guess.
I’ll try later that great new version. Preferred after I get info that the proble was fixed.
Nothing is downloading or uploading right now, no tool can show anything, procmon do not show any activity and yet - it uses data in his internal loop.
EDIT 2: I installed 12.2.2.8012 version after completely uninstall old version, removing leftovers and all Comodo registry keys and basically everything. So it’s firewall “clean” install. We will see how long until cmdagent.exe jumps over xx%.
Thanks for sharing the information.
Kindly check with CFW v12.2.2.8012 and let us know your cmdagent.exe consumes cpu status .
However we will check this issue with the latest CIS beta and update you.
