Hi,
"then either your service has a dependency on another service that is not starting correctly"
I have tried adding dependency of NetLogon but this does not work, are there other services that you would recommend adding a dependency
on? This one was the most suggested as NetLogon also relies on Workstation.
"or
your service's own startup code is failing and ends up stopping the service."
I believe that if this was true the users would not be able to start the service manually, and they are able to do so. Also the service
was starting fine for about a year prior and has only stopped auto starting within the last 2 months.
"the current problem should be related to these users’ specific configurations on computers"
I believe this is due to a windows update, all of the users services were starting automatically and recently they have stopped auto starting. As time goes on and more people update, more and more services may stop automatically starting this could be a
big problem.
"super user link"
I have read this previously and found that doing a delayed start is a workaround but not an actual solution as we are creating a backup service that we need to be started right away. Delayed start starts 2 minutes after the last automatic service is started
which can take a very long time.
There are also many other people having the same problem and I believe it needs to be looked at closer. I found many threads both here and on stack overflow where services are no longer starting automatically.
Thanks,
Megan
