Disable Comodo Firewall on Windows Startup

Hi everyone,
I am new to the Comodo Firewall, and up till now, I managed to do what I needed.

Now, I would like to start the firewall only when I am about to connect to the net, and not at windows startup.
I couldn’t find where/how to do this.

Can you help me?

Thanks, Scarlet

Welcome to the forum.
You can turn it off by going to start/run/msconfig/autostart and uncheck CPF.
Save and exit without a restart.
Then you should go to control panel/administrator tools/services and double click on Comodo Application Agent and set it to manual start instead of autostart.
Save and reboot.

One problem is that it probably wont start or work as it should when you try to put it on. I have tried it, but at least I have to do a reboot to get it to work.
Why do you wanna have it off? To much resources? It’s better to turn other unnecessary autostart objects off in msconfig and services.
Good luck.


Thanks for the answer.
I want to be able to control what is starting on, and when, that’s a first reason.
Second, when I am not connected to the net, I don’t see a reason to have the firewall on.
Third, it is something that I would expect from a good software.

I’ll try to post this as a request, or mail Comodo.
I think this is an important feature.

If I missed it somehow, can anyone let me know?

Thanks again,

I also think that a “Start with windows” option could be a good implementation for CPF…

I only use internet on WinXP from time to time, and for me its unnecessary to have a Resident Service totally useless

well, it’s my opinion! :wink:

I would agree with you if CPF would use a lot of resources, but as it is not noticeable, why go through the hassle… ???



You may find it rather difficult to do with CPF what you’re wanting to accomplish. Here’s the reason: CPF is designed and built to resist Termination Attempts (ie, a malware’s ability to kill the program). As such, even if you disable the autostart service (Comodo Application Engine) that AOwl mentioned, and the CMDMon driver (that he didn’t), and disable the startup entry for CPF, there are still some more secure drivers that are active deep within the system. Thus, the firewall is still running, albeit in a reduced state, to protect your computer. When you manually start it, you will have troubles as it considers the termination (however legit it may be) as an attack and limits your connectivity for security purposes.

I understand, however, that you don’t want it running all the time, and want a greater control over when it does start. A possible solution for you is to try a startup manager program (such as Startup Delayer from r2 Studios); these types of programs (many are free) allow you to set delay times for programs loading (following Windows boot/login); thus providing some measure of control over what starts and when…

I would propose that having CPF running even when you’re not connected is a benefit… It’s CPU footprint is minimal if there’s no net activity. And if do get malware on your computer (which is possible, even with Antivirus and Antispyware programs; infections DO occur), you have the potential of finding out before getting online, when the malware tries to connect to the internet… (as a note on this, CPF has been shown to catch malware on at least one documented occasion; malware that was identifiable by the user’s AV, but the AV did not identify or stop it).

I have had firewalls that were easily terminated/turned off, and at the time I thought (like you) that this was a good thing. I am no longer of that opinion, as I have found that the easier it is for me to turn the firewall off, the easier it is for malware as well…

Hope that helps you some,