Ever have a service fail to start with Local System, but will start with anything else?

[Alan Kamrowski II]

I've got a service that starts on my development box (win 10 home) under local system, but a particular Win 10 Pro box has this odd behavior: The service will fail immediately with erro 1053: The service did not respond to the start or control request in a timely fashion. This is an immediate error when I click start if it is configured for local system. Not a typical few second delay where the OS waits for a service to respond. If I change it to any named user for the logon such as administrator or a test user I created with regular user rights, it starts right up. If I change it to local service, it starts right up. I thought maybe some policy on the system was changed or something, but there are lots of other 3rd party services like an Adobe updater that are configured for local system and are started. I then made an empty service that essentially does nothing but respond to service requests thinking maybe there was some odd dependency, but even the empty service can't start using local system. Any ideas?

Continue reading...