I have a services running in Windows Local Services which is set to Automatic Startup. Every so often this service doesn't start after a reboot and there are no errors in the event log.

The service uses a domain service account as its impersonation. I have a feeling that the machine is having difficulty communicating to the domain controller and verifiying the logon which could be preventing the service from starting.


Are service account credentials cached for service logons? What is the expected behaviour if the logon cannot be verified?


No, the account credentials are not cached in this situation.

  • Thanks - What is the expected behaviour if the service cannot login? Does it simply not start? Should there be an error thrown? – heymega Jun 9 '15 at 12:33
  • Well I'm not sure about that, that's why I didn't answer that one. What is the service? – Konrad Gajewski Jun 9 '15 at 12:39

Does your service have any dependencies? Perhaps it is starting too soon, before the key services that support networking (such as "Workstation" and "Network Connections") are fully initialized. Try setting your service to be dependent on these services and see if that solves the problem..

Another simpler alternative is to change your service's startup type to Automatic (Delayed Start). This will have your service started 1-2 minutes after boot, giving the critical services sufficient time to get on their feet beforehand.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.