Sometimes, when a Windows server starts up, there are system services that can start up out-of-sequence — or perhaps just before they should — in the boot process.  Or, it might be that one service is dependent on the availability/functionality of another service on the same server in order to start successfully. 

Usually this service dependency is configured during installation; but if it becomes broken, it can be fixed by setting the original service to delay its start. 

Below is a very terse — but also very easy — way to set the original service to verify that the service upon which it depends is running, before attempting to start itself.

Warning: Before you make the changes described in this article, remember that you edit the registry at your own risk.  If you don’t know what you’re doing, just put down the mouse and step back…

First, you need to know the name of the service for which you are configuring a dependency.  The service name can be found by right-clicking on the specific service in the service console, and selecting Properties.  The service name will be under the General tab at the top.

 Now, to set it all up…

1. Click Start, click Run, and enter regedit.
2. Expand to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3. Right-click the service that you are trying to set a dependency for and select New -> Multi-string Value.
4. Rename the new value to DependOnService.
5. Double-click the DependOnService value and enter the dependent service name (from above) into the Value Data: field and click OK.
6. Close the registry editor.
7. Restart the server.
8. Enjoy.

For more information, see the Microsoft Article ID: 193888, “How to delay loading of specific services“.

Tags: dependency, Microsoft, system services, Windows