keepcalculator

06 Numbers and Powers

Dependency Service Failed to Start: Fixes

Card No. 06·79016 · Updated · Standard formula, shown below

If you see “The dependency service or group failed to start” when booting Windows or launching a program, it means a required background service did not load correctly, and the fix is usually to check the service’s dependencies, adjust its startup type, or repair corrupted system files. This error often appears with the event ID 7000 or 7023 in the Windows Event Log, and it can affect services like the Print Spooler, Windows Update, or third-party applications. Below is a practical guide to diagnosing and resolving the issue.

What Causes This Error

Windows services are designed to start in a specific order. When a service depends on another service or group, Windows tries to start the dependency first. If that dependency is disabled, crashed, or set to a startup type that prevents it from running, the dependent service fails with the “dependency service or group failed to start” message. Common triggers include:

  • A required service is set to Disabled in the Services console.
  • The dependency service is set to Manual but does not start automatically when called.
  • System files or the service registry entries are corrupted.
  • A recent Windows update changed service settings.
  • Third-party software altered the service configuration.

How to Find the Exact Service Name

Before making changes, identify the service that is failing. Open the Event Viewer (press Win + R, type eventvwr.msc, and press Enter). Go to Windows Logs > System and look for red error events with source Service Control Manager. The event will list the service name and often the error code. You can also open the Services app (services.msc), find the service that won’t start, and double-click it to see its Dependencies tab, which shows which services or groups it requires.

Step-by-Step Fixes

Try these fixes in order, checking after each one whether the problem is resolved.

  1. Restart the dependency service. In the Services app, locate the service listed under the failing service’s Dependencies tab. Right-click it and select Restart. If it is not running, right-click and choose Start.
  2. Set the dependency to Automatic. Double-click the dependency service, set Startup type to Automatic, click Apply, then Start the service if it is not running.
  3. Check the failing service itself. Set its startup type to Automatic (or Automatic (Delayed Start) if it is a non-essential service) and try to start it manually.
  4. Run System File Checker. Open Command Prompt as administrator and run sfc /scannow. This scans and repairs protected system files. After it finishes, restart your PC.
  5. Use DISM to repair the system image. In the same Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth. This fixes corruption that SFC cannot handle. Then run SFC again.
  6. Check for pending Windows updates. Go to Settings > Update & Security > Windows Update and install any pending updates, then restart.

Common Problem: The Print Spooler Service

One frequent example is the Print Spooler service. It depends on the HTTP Service and the Remote Procedure Call (RPC) service. If the HTTP Service is set to Manual and fails to start, the Print Spooler will not start. To fix it, open Services, find HTTP Service, set it to Automatic, and start it. Then start the Print Spooler. If the Print Spooler still fails, check that the RPC Endpoint Mapper and DCOM Server Process Launcher are running.

When to Use the Registry (Advanced)

If the service settings are correct but the error persists, the service’s registry entry may be corrupted. Each service has a key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ServiceName>. The DependOnService and DependOnGroup values list what the service requires. You can compare these entries with a known-good Windows installation or with the service’s default values from Microsoft documentation. Editing the registry incorrectly can break Windows, so this step is only for advanced users. Always export the key before making changes.

Comparing Startup Types

Understanding the difference between startup types helps prevent this error:

  • Automatic – The service starts when Windows boots.
  • Automatic (Delayed Start) – The service starts shortly after boot, reducing startup load.
  • Manual – The service starts only when another service or program needs it.
  • Disabled – The service cannot be started manually or automatically.

A dependency set to Manual usually works because Windows will start it on demand. However, if the dependency is set to Disabled, the dependent service will fail with this exact error. Always check that all dependencies are at least Manual, but for critical services, set them to Automatic.

Safety and Precautions

Do not disable services unless you are certain they are not needed. Many services are essential for Windows to function correctly. If you are troubleshooting a third-party service, check the vendor’s documentation for the correct startup type. Also, ensure you run Command Prompt and Registry Editor as administrator. Changes to service settings take effect immediately, but some require a restart.

Frequently Asked Questions

What does “dependency service or group failed to start” mean?

It means that a service Windows needs to run could not be started. The service that failed depends on another service or group that is either disabled, not running, or crashed. The error is logged in the Event Viewer with details about which service failed.

How do I find which dependency is failing?

Open the Services app, right-click the service that won’t start, and select Properties. Go to the Dependencies tab. It lists the services and groups required. Then check the status of each dependency in the Services list and start any that are not running.

Can I fix this without restarting my computer?

Yes, in many cases. If you manually start the dependency service and then start the failing service, the error may be resolved immediately. However, if the issue is due to corrupted system files, you will need to run SFC and DISM, which may require a restart to complete.

Why does this happen after a Windows update?

Windows updates can change service configurations, such as setting a service to Manual or Disabled, or altering dependencies. If an update changes a dependency to a state that prevents it from starting, the dependent service fails. Checking the service settings and resetting them to the default often fixes this.

Is it safe to set all services to Automatic?

No. Many services are designed to run on demand, and forcing them to start automatically can slow down boot time or cause conflicts. Only set a service to Automatic if it is required for your system or a specific application. For most dependencies, leaving them at their default (usually Manual) is correct.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →