Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Maybe you could give some examples of such services that fail to start. It's hard to guess what the issue may be without any details.
    – dxiv
    Commented Jan 16, 2016 at 0:12
  • 5
    If it makes you feel any better, you are not the only one. I have the exact same issue. The services are 32 bit. Custom software installed quite some time ago. So the WOW64 setting is there, turned on. I can start the services manually, but ever since upgrading from Windows 7 to Windows 10, the OS makes NO attempt to start the services. Their trace files show nothing, and the Event Log shows no attempt to start them, nor any problem with them. It is very frustrating. The Automatic Delayed is a lousy option, but I guess that's it for now...
    – Brian B
    Commented Apr 5, 2016 at 22:26
  • See also here: stackoverflow.com/questions/33238665/…
    – RenniePet
    Commented Nov 25, 2017 at 2:43
  • 1
    For me when having this problem, changing "This account" in "Properties>Log On" for the service, to a network name in the form "MyDomain\MyUser" from "[email protected]", solved the issue, although I have no explanation why.
    – MBWise
    Commented Mar 14, 2018 at 13:07