none
Firewall service doesn't start after reboot RRS feed

  • Question

  • Every Sunday morning, our VDI's with W7 32 bit and VMware view 5.1 get a scheduled reboot. About 5% of them are not reachable after the reboot. It turns out the Firewall service hasn't started.

    When I look in the event log, it says after the reboot:

    The Windows Firewall service terminated with service-specific error This operation returned because the timeout period expired.

    I can also see that the VDI doesn't have the correct domain profile (none), but that seems to be the case for every VDI.

    The problem occasionally also happens during the week.

    Steps taken to remediate this: I created a GPO that restarts the FW service the first 2 times and restarts the computers after subsequent failures. The network adapter is a E1000. After consulting VMware, we changed it to VMXNET 3, but this didn't help and we could not image our VDI's any more.

    Monday, February 22, 2016 10:26 AM

Answers

  • Hi Dutch_Frank,

     

    Based on your description, I noticed the error message, I want to confirm that have you installed any third-party software recently? Have you scan the virus on your computer?

     

    I suggest that we may perform a Clean Boot to ensure whether is problem is caused by a third-party software.

    How to perform a clean boot in Windows:

    https://support.microsoft.com/en-us/kb/929135

    In addition, for more firewall start issue, please refer to the link:

    Windows Firewall service does not start in Windows 10 / 8 / 7: http://www.thewindowsclub.com/windows-firewall-service-does-not-start

    Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Best Regards,

    Tao


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, February 23, 2016 11:46 AM
    Moderator

All replies

  • Hi Dutch_Frank,

     

    Based on your description, I noticed the error message, I want to confirm that have you installed any third-party software recently? Have you scan the virus on your computer?

     

    I suggest that we may perform a Clean Boot to ensure whether is problem is caused by a third-party software.

    How to perform a clean boot in Windows:

    https://support.microsoft.com/en-us/kb/929135

    In addition, for more firewall start issue, please refer to the link:

    Windows Firewall service does not start in Windows 10 / 8 / 7: http://www.thewindowsclub.com/windows-firewall-service-does-not-start

    Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Best Regards,

    Tao


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, February 23, 2016 11:46 AM
    Moderator
  • Hi Tao,

    Thank you for your reply.

    We have not installed 3rd party software recently. We do have Endpoint protection with the latest definitions. I have checked some things and they seem ok. For the rest, we have to wait until next Monday to find a VDI with a faulty firewall service. I will keep you updated.

    Monday, February 29, 2016 12:50 PM
  • Hi Dutch_Frank,

    I think the firewall troubleshooting tools may be a good idea, let's try it.

    Tools and Procedures Used to Troubleshoot Windows Firewall: https://technet.microsoft.com/en-us/library/cc749386%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

    Best Regards,

    Tao


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, March 1, 2016 1:03 AM
    Moderator
  • Hi Dutch,

    Is there any update on your issue?


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, March 7, 2016 8:16 AM
    Owner
  • Hi Tao,

    I did have a look at the Troubleshooting tools, but they assume that the FW service is working. I did find out that each VDI gets the message

    The Windows Firewall service terminated with service-specific error This operation returned because the timeout period expired..

    But the VDI's that do work, get an extra message after 30 minutes:

    The Windows Firewall service entered the running state.

    Monday, March 7, 2016 2:22 PM
  • Hi Dutch,

    It seems like service timeout period expired, please refer to the link:

    A service does not start, and events 7000 and 7011 are logged in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2:

    https://support.microsoft.com/en-us/kb/922918


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, March 8, 2016 1:14 AM
    Moderator
  • Hi all, somehow the problem solved itself. I did change the GPO to modify the recovery options of the firewall service.
    Monday, April 4, 2016 7:05 AM