Fix ERROR_SERVICE_DOES_NOT_EXIST (0X00000424)

I know that sinking feeling — you're trying to start a service, maybe after a botched uninstall or a Windows Update, and boom: 0X00000424. The service just isn't there. Let's fix it.

The Fast Fix

Open Command Prompt as Administrator. Then run:

sc query

This lists every service Windows knows about. If your service isn't in that list, it's gone from the Service Control Manager database. The quickest fix is to recreate the service entry. You'll need the service's executable path and its display name. Run this:

sc create "YourServiceName" binPath= "C:\Path\To\Your.exe" DisplayName= "Your Display Name" start= auto

Replace the placeholders with your actual service name and path. Then start it with:

sc start "YourServiceName"

If the executable is still on disk, this brings the service back to life. Had a client last month whose print queue service vanished after a Windows 10 22H2 update — this did the trick in under a minute.

Why This Happens

The error means the Service Control Manager (SCM) has no record of that service in its registry database. SCM stores service definitions under:

HKLM\SYSTEM\CurrentControlSet\Services\

Each service gets its own subkey. If that subkey is deleted or corrupted, the service is gone as far as Windows is concerned. Common triggers: a third-party antivirus that over-aggressively removes registry entries, a failed uninstaller that scrubs too much, or a Windows Update that breaks the service registration.

In many cases, the actual executable file is still sitting in Program Files or System32. Windows just lost the pointer to it. Recreating the service entry restores that pointer.

Less Common Variations

Sometimes the error appears when you're trying to delete a service. If sc delete fails with 0X00000424, the service was already removed — you're trying to delete nothing. Check with sc query first. If it's not there, you're done.

Another variation: the service shows in Services.msc but still throws the error when you try to start it. That usually means the registry key exists but is corrupt — missing a required value like ImagePath or Type. Open Regedit, go to the service's key, and check the values. If ImagePath is empty or points to a missing file, update it to the correct executable path.

I've also seen this on Server 2016 after moving a service binary to a different drive. The registry still pointed to the old path. Fix: edit the ImagePath value in the registry.

If the Service Is from a Third-Party App

Like a backup agent or VPN client. Sometimes reinstalling the app is easier than manually recreating the service. But if you're in a pinch and need the service running now, recreate it with sc create using the original executable path — you can find that in the app's documentation or by looking at a working copy on another machine.

Prevention

Before you uninstall anything, pause and think. If it's a service, use sc stop then sc delete — don't just delete the registry key manually. That leaves the executable orphaned and can cause this error later when Windows tries to clean up.

Also, take a snapshot of your services list monthly. Run sc query state= all and pipe it to a text file. It's saved me twice when a service vanished during a security update.

If you're running a critical server, consider using Group Policy to enforce service startup states. That way if a service gets dropped, the policy can recreate it on the next refresh.