Fix 0X0000042C: Dependency Service or Group Failed to Start

Yeah, this error is annoying. You're staring at a service that won't start, and Event Viewer just gives you that vague 0X0000042C code. I've fixed this exact problem on hundreds of Windows servers and workstations. Let me save you time.

The Quick Fix

Open Services.msc. Find the service that's failing. Right-click it, go to Properties, then the Dependencies tab. You'll see a list of services this one depends on. Every single one of those must be running. If any are stopped—even if they're set to Automatic—start them manually, then start your original service.

For example: if you're getting this error on Windows Time service, check that WinHttpAutoProxySvc is running. It's a common dependency that gets disabled by some security tools.

If a dependent service won't start either, check its dependencies. You might be chasing a chain of failures.

Why This Happens

The error means Service Control Manager tried to start your target service but the dependency—another service or a service group—wasn't available. The dependency either failed to start, was disabled, or crashed after starting. Windows doesn't try to restart it; it just throws the error and moves on.

Root causes I've seen most often:

• Disabled dependency — someone disabled a required service via Group Policy or manually. This is the #1 culprit.
• Service group failure — service groups like "Tcpip" or "NetBIOSGroup" are virtual. If one service in the group fails, the whole group fails.
• Corrupted service state — the dependency's registry entry is damaged. You'll see this after failed updates.
• System file corruption — sfc /scannow sometimes fixes it, but don't bother unless the above steps fail.

Step-by-Step Fix

1. Open Services.msc as Administrator.
2. Find the failing service. Note its Display Name.
3. Right-click → Properties → Dependencies tab.
4. Under "This service depends on the following system components", you'll see either service names or group names. Groups start with + in some views.
5. For each dependency, check its status. If it's stopped, start it. If it's set to Disabled, change it to Automatic or Manual (depending on what the service needs).
6. Repeat for any nested dependencies.
7. Once all dependencies are running, start the original service.

Using the Command Line

If you prefer the terminal, use sc qc [ServiceName] to see dependencies. Example:

sc qc w32time

Look at the DEPENDENCIES line. It'll list service names (like WinHttpAutoProxySvc) or group names like Tcpip. Groups start with a forward slash: /Tcpip.

To check if a dependency is running:

sc query [ServiceName]

If it shows STATE: STOPPED, start it:

sc start [ServiceName]

When the Dependency Is a Service Group

Service groups are trickier. A group like "Tcpip" or "RPCSS" isn't a real service—it's a logical group of services. If the group fails, it's because something inside the group is broken. You need to check Event Viewer for other errors. Look under Windows Logs → System for events with IDs like 7000, 7001, or 7026. These point to the real culprit.

For example: if the group "RPCSS" fails, it's almost always because RpcSs or RpcEptMapper is disabled. I've seen people disable RPC services thinking they're safe—they aren't. Windows 10 and Server 2016+ require RPC. Don't touch it.

Less Common Variations

Service Won't Start After Reboot

If the service starts manually but fails on boot, a dependency is set to Manual but isn't starting fast enough. Change that dependency to Automatic (Delayed Start) to give it more time.

Third-Party Software Conflicts

Antivirus or security software sometimes disables services they think are unnecessary. I've seen McAfee and Symantec do this to the Windows Time service. Check your AV's startup protection logs.

Corrupted Service Registry Entry

Open Regedit, go to HKLM\SYSTEM\CurrentControlSet\Services\[ServiceName]\. Look at the DependOnService or DependOnGroup values. If they contain weird characters or blank entries, that's your problem. Export the key first, then fix it. Be careful here—one typo can break the service completely.

Prevention

• Never disable core Windows services. If you're not sure what it does, leave it as default.
• When deploying new software, test its service dependencies in a lab first.
• Use Group Policy to lock down service startup types—but apply it to a test OU before production.
• Monitor Event Viewer for service failure warnings. Catch this early before it cascades.

That's it. Nine times out of ten, it's a disabled dependency. Check that first and you'll be done in two minutes.