Windows Service Error 1068, "The dependency service or group failed to start"

Error 1068 means the service you tried to start needs another service to run first, and that dependency failed to start. The fix is almost always in the dependency, not in the service that reported the error.

The fix, in order

  1. In Services, double-click the service and open the Dependencies tab. Note every service listed under "This service depends on the following system components."
  2. Try starting each dependency by hand. The one that fails is the real problem, and its own error message tells you what to fix next.
  3. Check each dependency's Startup type. A dependency set to Disabled cannot start, so change it to Automatic or Manual.
  4. Check the Event Viewer System log for errors from the dependency service around the time you tried to start it.
  5. If a dependency belongs to a program, repair or reinstall that program. A missing or damaged dependency is common after a partial uninstall.
  6. Run sfc /scannow in an admin Command Prompt if a Windows component is the failing dependency.

If it still happens

If all dependencies start by hand but the service still reports 1068, restart the PC and try again, since a dependency can be stuck in a stopping state. If the dependency list includes a service that no longer exists, see the fix for error 1075.

Common questions

How do I see what a service depends on? In the Services console, double-click the service and open the Dependencies tab. It lists every service and driver group the service needs before it can start.

Should I set all dependencies to Automatic? No. Set a dependency to Automatic only if the service that needs it is also Automatic. Manual is fine for a dependency that is started on demand by the service that needs it.

Related errors

Windows Service Error 1075 · Windows Service Error 1053 · Print Spooler service not running

Was this helpful?