Troubleshoot: Windows Services will not start

Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of, a 10-year Microsoft MVP Awardee in Windows (2006-16) & a Windows Insider MVP. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.


  1. Noremacam

    I found a Windows 10 specific issue where most .Net based services
    would fail on startup, but could be started later manually just fine.
    For some reason, services that are written in .NET take longer to start
    in Windows 10. By default, if a service takes longer than 30 seconds to
    start without responding, the service is terminated by Windows.

    I was able to change that behavior to 60 seconds in the registry. Go to:


    If it doesn’t already exist, create a DWORD (32-bit) key called
    “ServicesPipeTimeout”(minus quotes). Set its value to 60000(in decimal).
    This correlates to 60 seconds in milliseconds.

    This fixed the issue for us on multiple machines. Let me know if this
    helps. Unfortunately, I still do not know why .NET services take so
    long to start that they get terminated. However, I feel this is a
    Microsoft bug, and not necessarily anything us users are doing wrong…

  2. Jessica Harper

    I know how to access windows services to enable or disable. I can’t get onto my administrator account in order to do so. It also doesn’t work in safe mode. I don’t know what to do. Please help!

  3. David Stroud

    I get the message saying the same thing trying to run the service.msc as well. It started last night, and I just logon to my computer, and waiting did not fixed the issue.

Leave a Reply

Your email address will not be published. Required fields are marked *

1 + 2 =