It’s kind of a joke. Certificate check is very important etc. But the main problem is I was trying to fix my Comodo Firewall today and I ended with uninstalling it. Apparently for no reason - all I need is just wait.
Come on! Security can’t be that paranoid. I understand that Windows wants to protect us at all cost, but if I trust downloaded file, I should be able to install it, no matter if have valid certificate or not. I need firewall and it’s apparently impossible to bypass that whole Windows protection %#@@ - even if I have everything disabled, it still wants to protect me.
Users have less and less control over their systems.
I am waiting for that updated installer and good luck Comodo!
EDIT: I downloaded offiial old firewall (it’s basically all I need) and we will see. So far is working.
The previous version of Comodo Firewall (12.2.2.8102) works fine as it always has. The certificate issue only affects any current 2025 version available for download- and this would affect only the installation of the new version. The protection afforded by any current versions (either 8102 or 80140) would not be affected.
Don’t know if “current versions (…) would not be affected” since tomorrow morning my Comodo Firewall (beta 2) stops working (cmdagent was unable to start or something like that) and that’s why I decided to upgrade firewall, update system etc. And when nothing works - I uninstalled everything and back to old version.
Hi all, we are communicating with our Certificate Authority to solve this problem within a couple of days. After that we will create new installers for CIS 2025 (both online and offline) and replace those fresh installers with the old ones that are currently available.
Problems are appearing…
Why are the CIS 2025 processes reporting that they are UNKNOWN?
And several other processes that cannot be shown completely in the image.
I did a quick scan with CIS 2025;
The information is not good, it is reporting that there are 2 threats, but these threats are the COMODO service itself.
It’s just detecting the certificate which has been revoked but it’s not an issue. They’ll push updated certificate when it’s been resolved. Your still protected as the devs and Melih have said.
When an antivirus certificate is revoked, the fix can usually be done through a software update or signature database update, depending on the type of revocation and the antivirus. Most modern antivirus solutions are equipped to automatically fix this type of problem via updates.
Because it will be necessary to create new installers for CIS 2025 to replace it, since a software update via update could solve the problem, avoiding people having to do a lot of work to remove it from each computer and install it from scratch.
This is my case, I have several clients, it would be unfeasible for me to have to manually update each person’s machine.
Same problem.
But contrary to what has been said, it’s for an old installation.
CIS Pro 2025 no longer works.
The certificates are broken.
The license is no longer recognized.
It’s dead.
I had to uninstall.
Impossible to reinstall.
There was a time when Comodo was the King of Certificates… (Sectigo now)
Is that the case, though?
My installation of CIS stopped working properly because the agent would no longer start due to the expired certificate.
Edit: I should probably say that it was an installation of CIS2024, so it was not the latest version. I relied on automatic updates but that seemingly does not/did not include updates to CIS2025.
What I want to know is why there were no preventative measures taken to issue a new cert and binaries before the revocation was set. This entire mess could have been easily avoided. Unless the Comodo servers/a developer was hacked and the cert was stolen I just don’t see the logic, the lack of transparency is a very bad look either way.
Run the Uninstaller tool to remove CIS and then use .8012 in the interim if you are having issues as described in my post here:
The Containment protection is the same in the old version and the new version of CIS/CF. The certificates will be updated in the next couple of days. What you decided to do between now an then is up to you. I run CFW .8012 just fine on Win 11 and waiting for the updated certificates before installing 2025 again.
I checked my system with several programs and cce detected a threat: UAC.
I had it repaired once and… the computer wouldn’t boot. But now I avoided repair.
Other than that, no software detected a threat.
