Problem:
An error message containing “Comodo security agent could not be started” shows up everytime you start up Windows, which renders the program unusable. Sometimes you are even disconected from the internet (because the firewall is installed, but the service is not running)
Affects: CIS Premium 6.0.264710.2708
Details:
It appears cmdagent.exe (the service) does not run. Starting it manually from service.msc produces no result, and even if it says “Started”, once you refresh the service.msc, it shows nothing (i.e. not started)
Tried reinstalling (Uninstall then install) - does not work.
I have tried reinstalling for about 8 times and still does not work.
I have even tried uninstalling the program and use another program from Auslogics to try to clean it up, but it does not work.
Finally, here is my final solution that works:
After uninstalling, delete any Comodo Folder from (assuming Windows on C:) C:\ProgramData and the Local, LocalLow, and Roaming. then reinstall.
That seems to be working.
Sorry that the text is not properly formatted. I am just posting it here in case anyone have the same problem, since I have found no lead on the web.
The topic may seem to report 2 separate bugs but it’s actually one and the same bug with two stages. Meaning that “Defense+” not working causes the tray agent to terminate itself.
Here’s a report in the standard format as asked for.
A. THE BUG
Summary: Pls give a clear summary in the topic subject, NOT here.
Can U reproduce the problem & if so how reliably? - I can't. I don't know what's causing it, so I can't reproduce it.
If U can, exact steps to reproduce. If not, exactly what U did & what happened:
a. I was notified to allow program update, so I allowed it.
b. About 2-3 minutes after the update was complete there was this exclamation mark in the system tray.
c. When I clicked on the excl. mark there was a message at top left corner of the program window which says "Defense+ is not working properly" and a button "run diagnostics".
d. Running diagnostics couldn't fix anything, so I saved a diagnostics report.
e. Moments after the diagnostics report is saved the tray agent terminates itself and/or is being replaced by the exclamation mark.
f. I noticed that when I restart my PC a few minutes after system boot Comodo works fine, then the excl. mark returns and "kills" Comodo tray agent.
If not obvious, what U expected to happen:
If a software compatibility problem have U tried the conflict FAQ?: Not a software compatibility. I'm running Avira Free along with Comodo but at the time when this bug occured there was only Comodo installed. Avira wasn't installed yet. Besides for the last year or so I've used both programs together and never had a single problem with both of them running.
Any software except CIS/OS involved? If so - name, & exact version:
Any other information, eg your guess at the cause, how U tried to fix it etc: My best guess of the cause is a bad code in the last program update because the bug occured a few moments after the last update which happened 1 day before I posted this topic.
Always attach: Diagnostics file: Apparently I can't attach the xml diagnostics report to the post, so I've uploaded it on mediafire: http://www.mediafire.com/?lq4v9ja6etegviq
B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
Exact CIS version & configuration: Comodo Firewall x64 v5.12.256249.2599
Modules enabled & level. "Defense+" is OFF; used Comodo DNS servers. Everything else is with default settings.
Have U made any other changes to the default config? (egs here.): No
Have U updated (without uninstall) from CIS 5: Yes.
if so, have U tried a a clean reinstall: Yes, I did. Didn't help at all.
Have U imported a config from a previous version of CIS: No.
if so, have U tried a standard config - if not please do.
OS version, SP, 32/64 bit, UAC setting, account type, & virtual machine used: Windows 7 Ultimate SP1 x64, UAC=off, admin, VM not used
Other security software: at the time the bug occured - no.
I did. In fact I had to reinstall Windows due to a virus problem and after Windows reinstallation I did a clean install of Comodo which changed nothing - Comodo keeps doing the things I described.
We would very much appreciate it if you would be kind enough to edit your report to put it in the standard format and add any additional information requested, as this will make it much easier for the developers to diagnose and fix the problem.
The reasons we need all the information in the format, though they may not seem directly relevant to the issue are explained here.
If you are able to do this we will forward this post to the format verified board, where it is more likely to get looked at by developers. You can find assistance using red links in the format and here. If you need further help please ask a mod. If you do not add the information after a day or two we will forward this post to the non-format board. If this happens we will tell you how to rectify this if you wish to.
In the current process we will normally leave it up to you whether you want to make a report in standard format or not. However we may remind you if we think a bug of particular importance.
Just Avira but for the more than a year with Avira and Comodo - Avira has never created any problems for Comodo or vice versa.
Besides, after Windows installation I installed Comodo first - as always and while I was navigating directories to Avira Setup Comodo began behaving the way I said, so you see - the reason can’t be Avira because at the time Comodo terminated itself Avira wasn’t installed yet.
OK the fact that CIS comp;ains is by design, but your second issue sound like it could a bug so:
Thank you very much for your issue report.
We would very much appreciate it if you would be kind enough to edit your report to put it in the standard format and add any additional information requested, as this will make it much easier for the developers to diagnose and fix the problem.
The reasons we need all the information in the format, though they may not seem directly relevant to the issue are explained here.
If you are able to do this we will forward this post to the format verified board, where it is more likely to get looked at by developers. You can find assistance using red links in the format and here. If you need further help please ask a mod. If you do not add the information after a day or two we will forward this post to the non-format board. If this happens we will tell you how to rectify this if you wish to.
In the current process we will normally leave it up to you whether you want to make a report in standard format or not. However we may remind you if we think a bug of particular importance.
For some reason, Comodo won’t open anymore since my last computer restart. Now, anytime I try to do so, the “CisTray.exe” will show up in task manager, but nothing else. Windows will even notify me that I don’t have any antivirus installed, and after a minute or so after attempting to open comodo, I’ll get the error message “COMODO Security Agent could not be started. Would you like to run the diagnostics tool to fix this error?” But when I run said tool, it says it hasn’t found anything wrong. I’ve tried re-installing, but it doesn’t help at all.
This issue appears to me to be the same as one already on file. Accordingly, I will merge them, if that’s OK. You can locate the merged report by following the link in the email notification.
If you don’t agree please PM any active mod with your reasons and, if appropriate, they will unmerge the issue.
This is a 5.x and a 6.x bug [edited], so once a report is complete, I will forward to format verified.
Rado84, could you please do the following to complete your formatted bug report
Embolden the prompts to make it easier to read
Add your ‘watch activity’ process list. Please follow red links in format for guidance. You can append zip and image files
There is a work-around in this trace developed by Charon. Alternatively using the forced uninstaller then re-installing (see Installation help stickies will probably work too)
Thanks very much for your issue report, which is much appreciated.
We have moved it to the non-format bugs board for the moment, because it is not in the standard format or too much of the information we normally need to replicate a problem and fix it is still missing.
We realize some people may not have the time to do an issue report in standard format, and therefore offer the option of a non-format report instead. But the problem is much more likely to be fixed promptly if you edit your first post to create an issue report which reflects the guidance in the Standard Format topic. (You can copy and paste the format from this topic). The reasons we ask for the information we do are given in this post.
You can get your report moved to the format verified issues board simply by ensuring that it reflects the guidance in the standard format topic, and PM’ing a mod who is active on the bug board.
Can you please check and see if this is fixed with the newest version (version 6.2.282872.2847)? Please let us know whether it is fixed or you are still experiencing the problem.
Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments, so I can forward this to the devs and get this problem fixed.
Can you please check and see if this is fixed with the newest version (version 6.3.294583.2937)? Please let us know whether it is fixed or you are still experiencing the problem.
Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are mainly not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments), so I can forward this to the devs and get this problem fixed.
The devs have been unable to replicate this. Thus, as there has also been no response, I will assume that this is fixed and move this report to Resolved. If you are still experiencing the issue let me know.