I’ve installed CIS (only the firewall paket) for a long time on my windows 10 pc without problems. Suddenly it won’t start and exits with a message that it could not be startet on windows startup. I didn’t change anything on my pc or installed something new.
I’ve run the analyse tool as suggested and saved the report and attached it.
Can you next time when it happens check first if cmdagent.exe is running before running the analysis tool? Did the problem happen on other boots as well or was this a one of a kind event?
This looks like the timing problem where the client program cis.exe started earlier than cmdagent.exe. Once the desktop was started and the client could show the error message cmdagent.exe had already started. It was a problem that happened with a test build of one of the previous versions. I have seen it very very incidentally happen with stable releases.
If cmdagent.exe is running then diagnostics doesn’t need to run to try to fix it.
The problem happens on every boot since last week on this machine. Before this I use Comodo Firewall for a long time without problems on this machine.
The cmdagent.exe ist not listed in the taskmanager when the comodo message with the suggestion to run the analysis tool is shown. Comodo Firewall is shown in the systray without an icon. I made a screenshot which is attached.
Is it recommended to use the official uninstaller tool Comodo Forum to remove and reinstall CIS in this case?
To see if cmdagent.exe is running you need to run Task Manager for all users (Prozessen aller Benutzer anzeigen).
Could you check with the all users setting enabled and post a screenshot again.
Is it recommended to use the official uninstaller tool https://forums.comodo.com/news-announcements-feedback-cis/official-comodo-uninstaller-v2003-released-t121091.0.html to remove and reinstall CIS in this case?
You could try a clean installation of the latest RC using this tool. Don’t forget to export your configuration in case you want to keep it. Save it to a location that is not part of the CIS installation folder.
Could you first try to run with the default config to sere if the problem is fixed or not and then with your config?
I used the uninstall tool and then installed the latest 10.2.0.6514 RC. After this now CIS worked without problems. Because of this I can’t look for the cmdagent.exe with old installation no more sorry…
Can I updated the 6514 RC to further normal product version if it will be relaesed? How can I do this? Just remove the two given entries in the hosts and use the normal build in update function?