Please see the following link to answer your question.
https://forums.comodo.com/install_setup_configuration_help/cfp_3554375427_not_recognized_by_windows_security_center-t29190.0.html
That should resolve your question.
I think that’s what happened. 3.5 got pushed out as an update for 3.0 and I let CFP update itself. If the recommended upgrade is to completely uninstall CFP and install CIS, then why was it pushed out as an update to begin with?
It is an update to CFP, but at the same time it is a new Program (Suite, if you prefer) since it includes the option of CAV, and future releases will include CMF and BoClean.
This is my point exactly. If this update should be applied through a re-install, we push it through the auto update? It goes back to QC… it wasn’t really thought through. I mean when I applied the auto update, it didn’t even put the new Antivirus tab in the app, so I didn’t even KNOW there was a new antivirus.
Mostly, my hope is just that this becomes a learning experience for the QA department.
I have the same problem, and after reading the posts in the link I have to say it doesn’t help much.
There is as is said no clue that the update to the firewall is not all you need to do!
It doesn’t seem right that you should have to uninstall then partially install CIS to get back where you were.
As far as I can tell Comodo 3.5 seems to be functioning OK apart from the windows monitoring thing.
In the meantime, I have told Windows I will monitor my own Firewall.
I’ve run into this issue as well. I was upgraded to CIS 3.5.54375.427 without warning.
In Windows XP SP3 x32 the upgrade was handled smoothly.
In Vista SP1 x32 the upgrade was incomplete, I had to go through Control Panel → Uninstall a program → Select Comodo Firewall Pro → Uninstall/Change → Add/Remove → Select Install COMODO Firewall (it is unselected by default in Vista but is selected in XP) then continue through the installation process.
At no point was a notice given about loosing settings or requiring an uninstall/reinstall to get things going. If such is required that is a bug and should be flagged as such.
Comodo developer now says that updating from CFP 3 to CF 3.5 should work fine. Currently I don’t know more than this.
LA
I won’t recommend exporting 3.0.x and importing this in CIS 3.5.x unless you know what you are doing…
See the FAQ for more details.
I have tested the upgrade on Virtual PC with Windows XP SP3 my Security Center reports COMODO firewall is active.
I just recently switched from a paid version of ZA Internet Security Suite - time ran out. I think this is a fantastic program, but I would have to agree with most of the other posters on this issue. I can’t believe this would happen from, what appears to be, an outstanding company.
My very first update after installing CFW came yesterday, and after restart VistaSP1 Home Premium tells me I don’t have a firewall. I had no problems with the update, except for the extremely long time it took, which seemed rather odd to me at the time it was happening. If I open the window everything seems to be just great, and working, I HOPE! The only notification I got was that there was an update waiting to be installed to my CFW. I clicked it and it started. Rebooted once it got through, and there is the no firewall message.
I would certainly think that some sort of fix should be forthcoming, rather than having to uninstall and reinstall, just to get the security center to recognize it!!! It doesn’t appear that the AV component, or anything else new was installed, but my tray icon now says “COMODO Internet Security”!
And yes, ZA was completely uninstalled using RevoUninstaller, which I also think is a very nice program.
Is there any possible way you can ask if there’s a solution for the people who have already updated, aside from a reinstall of the software?
Edit: Nevermind. I came across a solved help thread for installing the Anti-Virus component after the firewall had already been installed (Thread located here). I thought maybe their was a repair option, so I loaded up Vista’s rendition of Add/Remove Programs and ran the installer. No repair option, but you can pull off a repair by selecting Modify, which essentially lets you rerun the installation without having to uninstall and lose all your settings. The odd thing is that the installer doesn’t detect the components you already have installed and automatically tick the boxes for them, so if you’ve got the Anti-Virus installed and you only check the Firewall, you might risk the AV being uninstalled. I haven’t tried that though, and I don’t know how the installer behaves, so don’t quote me.
Anywho, and in short, if you load up the installer from Add/Remove Programs or Vista’s Programs and Features and go through the installer for the Firewall (With the reboot), you’ll repair the Security Center tie-in without having to uninstall and lose all your settings.
Just to mirror what I said in the CIS Setup/Install forum, if you go to Add/Remove Programs (XP) or Programs and Features (Vista), select Change/Uninstall to bring up the installer, select the Modify option, run through the installer and reboot at the end. That fixed the Security Center tie-in for me, although I still think the Comodo Diagnostic feature should be modified to repair it.
Thanks for your help, using the Add/Remove Programs to reinstall did fix the problem, and now Windows Security Center does recognize that I have CFP installed. It would be nice if the auto update did not cause this problem, but at least that was an easy fix to do.
Glad to help.
Merged Threads. (:m*) All XP/Vista Related WSC probs can be posted here. 
Josh
Hi.
After installing the most recent upgrade (done in nov/01/2008) my vista business report CFP is not ‘installed’: vista’s security center’s red shield remains on taskbar and requiring me to activate windows firewall. When using an internet ports probe (Shields UP!! — System Error) it says all my ports are ‘stealth’ but microsft’s firewall is not enabled. Because the comodo’s shield are being shown in the task bar i suppose the protection is being provided by it.
Pls, is there any problem in the most recent upgrade of cfp v3 regarding windows detection of a third party firewall? In other words, why is not windows detecting cfp v3 after we install the most recent upgrade?
Thanks, Tedesco.
Please, read this entire thread. It’s already answered here, incl. the way to fix broken WMI. People generally don’t like to waste their time repeating the same over and over again. :-La
Hi I’m new here so please forgive me if I’m using the wrong thread.
I have just had a Comodo update which was successful, but Windows doesn’t recognize it So have had to tell it I will monitor it myself.
Before the update Windows would say ‘Comodo firewall is currently on’ This by the way is using O/S Vista Basic.
However, on my XP3 O/S the new update is accepted by Windows.
Any comments would be appreciated.
Ron.
Please, read the entire thread. Already answered there.
Sorry there are threads all over the place relating to this and new ones being created recently so I merge them.
Josh