Quite often, when I start my laptep the comodo firewall starts up with protection disabled.
The protection will not enable unless I exit and restart the firewall.
Can anybody shed any light on this, it hasn’t happened on my PC.
Welcome to the forums!
What version of the firewall do you have?
Did you have any version prior to this one?
Is it the same on both machines?
When did this start?
LM
Thanks for the welcome.
The version is 2.4.16.174.
I had the previous version and had trouble updating on the laptop.
In the end I had to download manually.
It has never happened on my PC.
One thing I might have noticed is that it may occur when I boot the laptop and the firewall starts before the Netgear routre has connected.
Maybe the firewall sees no network and goes into disabed mode?
Unfortunately, when it goes into this state it won’t let me enable anything.
Does it have to be enabled in a specific order?
It has only happened in the last couple of days, some time after the upgrade.
ASB
There were some problems with the automatic update, due to loads on Comodo’s server(s); a manual download was required by many.
If you have the downloaded install package still, great; if not, get a new one.
My recommendation is that you completely uninstall CFP, reboot, run a registry cleaner (like RegSeeker) to clean out obsolete/orphaned entries, reboot, and then reinstall it fresh.
My thought is that (based on what I’ve seen from other users that had auto-update issues) by partially updating, something may have gotten messed up, and is lingering to cause problems, after the uninstall of the previous version.
Before uninstalling the firewall, do the following things (Note: I corrected the order here, on 2/7/07):
-
Go to Start/Run, type “msconfig”, go to the Startup tab. Make sure if there’s any entry for CPF checked, that you uncheck it, click Apply, OK. You don’t have to reboot yet.
-
Then, in CPF, go to Security/Advanced/Miscellaneous, and uncheck the box to Protect Own Registry Keys. OK. Go to the Summary page, and move the Security level to Allow All.
-
Go to Start/Run, type “services.msc”; find the entry for Comodo Application Agent. Double-click, and set the start type to disabled. OK.
Now run the uninstaller on it, and reboot when finished.
Then run the registry cleaner and reboot.
Turn off/deactivate ALL other security software (Antivirus, Antispyware, HIPS, Windows Firewall, etc) then reinstall CPF.
I know that’s a number of steps to go through, but it should go pretty quickly, and we want to make sure that we eliminate the possibility of something having been messed up previously. In fact, I’d almost recommend getting a new download package entirely, just to eliminate that as well.
Hopefully that will fix the issue.
LM
Thanks, I’ll try that.
Please let us know how this works. Perhaps it will help with the issues I’m having (monitors won’t enable).
I had this problem and I followed “Little Mac’s” advise in Reply #3. And it’s working for me now. I made sure that I started with a new download. The only thing I had to do was the reverse the order of “services.msc” and go into CPF Security/Advance/Miscellaneous. For some reason I couldn’t disable the Comodo Application Agent without changing Protect Own Registry Keys and Allow All first in CPF.
Pat
I’m glad that’s working for you. Thanks for the comment; yeah I should have had the order different. I will edit that now… ;D
LM
I finally got round to trying the uninstall/reinstall.
It didn’t change anything.
It all seems to stem from booting while my wireless router is switched off.
If it is on, everything is OK.
If it is off, comodo start disabled and will not enable unless exited and restarted.
It restarts OK even if the router is off.
I will have to make sure the router is on when I boot I guess.
Thanks for all the help.
Does this issue still persist with the latest 2.4.17.183?
Yes, I am running 2.4.17.183.
I am getting used to it now, I have checked the show the application window on system startup so now I can see if it has started disabled. If it has, I just stop it and re-start it and everything is fine.
Of course, if I start the router first there is no problem.
That’s an odd one. Will you file a ticket with Support, so we know they’ll be looking into a fix for that?
It’s good you’ve got a way around it, but it’d be better not to have to…
LM
I am logging it with support.
It has started happening even when the router is on now.
it comes up dead when there is no IP address.
Maybe the firewall should start after the network is up but that would seem to leave a window of inopportunity.
Please keep us posted on the progress, asabarker…
LM