none
Can't Disable Windows Firewall Service? RRS feed

  • Question

  • Hi All,

    My company is using Sunbelt Software's VIPRE Enterprise Premium as out endpoint anti-malware solution.  Along with the anti-malware engine/scanner, the software includes a software firewall (hence the "Premium" version). 

    Having installed/configured the firewall included in VIPRE (and having it "Integrate" with the Windows Action Center) I disabled the Windows Firewall service.  As is my understanding, Windows Vista/7 must have a firewall installed, whether it be the Windows one (and even setting the profiles to "Off") or a third-party one, otherwise it will not send/recieve network traffic. 

    Now, keeping in mind I have a separate software firewall, I received a message this morning stating the following:

    The Windows Firewall service is not running. 
    Windows cannot automatically enable or disable Remote Desktop because the Windows Firewall service is not running. 
    To fix this problem, open Control Panel, click Administrative Tools, click Services, double-click Windows Firewall, and then click Start.  Then, on the Remote tab in System Properties, enable or disable Remote Desktop.
     

    Okay, so what gives here?  I have a separate firewall installed; I should not be forced in to keeping the Windows Firewall enabled ("anti-competitive practices", anyone?) to make system changes.  Yes, I know I can have it set to "Off" for all of the profiles, but why tie-up system resources if the service isn't being used?! 
    What other "Surprises" are in store for me because I have the Windows Firewall disabled? 

    Thanks in advance!

    Thursday, September 30, 2010 1:56 PM

Answers

  • ...really is a pain that you have to keep it running and turn the profiles off rather than just issue a simple "stop and do not auto start" command.

    Exactly.  You could do it in Windows XP if you were so inclined, but not on any of the NT6 or higher systems. 

    I understand the need for a firewall; I understand the inclusion of the firewall in to Windows.  I just find this whole "You're gonna leave it running whether you like it or not" mentality to be deplorable.  I have a separate software firewall, why utilize more resources for something I'm not using? 

    This just reeks of the same stink that got Microsoft in to anti-trust/monopolistic hot water in the first place, and it disappoints me. 

    Friday, October 1, 2010 2:55 PM

All replies

  • From my experience, Windows 7 and Server 2008 (R1/2) really do not like this service turned off. I even had a server go so far as to refuse to share any printer without this service running...really is a pain that you have to keep it running and turn the profiles off rather than just issue a simple "stop and do not auto start" command.
    Thursday, September 30, 2010 10:32 PM
  • ...really is a pain that you have to keep it running and turn the profiles off rather than just issue a simple "stop and do not auto start" command.

    Exactly.  You could do it in Windows XP if you were so inclined, but not on any of the NT6 or higher systems. 

    I understand the need for a firewall; I understand the inclusion of the firewall in to Windows.  I just find this whole "You're gonna leave it running whether you like it or not" mentality to be deplorable.  I have a separate software firewall, why utilize more resources for something I'm not using? 

    This just reeks of the same stink that got Microsoft in to anti-trust/monopolistic hot water in the first place, and it disappoints me. 

    Friday, October 1, 2010 2:55 PM
  • I agree.

    I understand the technical reason why, but MS should have kept the ability to stop this service and not adversely effect other windows components.

    • Proposed as answer by RayRoussy Friday, October 11, 2013 6:19 PM
    • Unproposed as answer by RayRoussy Friday, October 11, 2013 6:21 PM
    Friday, October 1, 2010 4:30 PM
  • You can no longer stop the service. As simple as that.

    That doesnt mean you can't disable the firewall itself and use a 3rd party software.

    Simply refer to http://technet.microsoft.com/en-us/library/cc766337%28v=ws.10%29.aspx

    You start the service. Open the GUI Firewall interface and turn off the firewall. Then you use Vipre or whatever else you want.

    rgds

    • Proposed as answer by RayRoussy Friday, October 11, 2013 6:21 PM
    Friday, October 11, 2013 6:21 PM
  • Way to reply to a thread that is over three years old...  ;)  Thanks for the link though; it may be helpful to anyone else who may come across this thread. 

    Incidentally, I read up on the firewall since I started this thread and I know I can stop the service if I have another firewall installed, however I did encounter issues where certain things still wouldn't work properly if the service wasn't running, so instead of "Tuning" the situation, I just disabled the firewall but left the service running. 

    Friday, October 11, 2013 6:59 PM
  • (and 5 years later)

    Windows Server 2008 and on: The windows firewall API is required for other network services to properly function.  Simply disable all profiles:

    Make sure the firewall service is set to start automatically in services control panel and then run (at an elevated command prompt)

    NETSH advfirewall set allprofiles state off

    This disables the firewall policies for the service, while leaving the service intact and running, allowing other services that are dependent upon it functioning.


    • Edited by Mac MacAnanny Wednesday, October 31, 2018 4:40 PM comical
    Wednesday, October 31, 2018 4:40 PM