Fix ERROR_SERVICE_NOT_FOUND 0X000004DB in Windows Server

When does this error show up?

You'll see error 0X000004DB (which means ERROR_SERVICE_NOT_FOUND) when you run a command like sc start or net start in a command prompt. Or when a program tries to start a service using the Windows Service Control Manager (SCM). It happens a lot after you uninstall an application or driver — the service entry stays somewhere but Windows can't find the actual binary. Another case: on Windows Server 2019, after you remove a third-party firewall driver, the service entry is still in the registry but the driver files are gone.

Root cause: What's actually happening

The SCM keeps a list of all installed services in the registry under HKLM\SYSTEM\CurrentControlSet\Services. Each service has a key with values like ImagePath (points to the exe or driver file) and Start (how it starts). Error 0X000004DB means the SCM looked up the service name you gave it but couldn't find the key in that registry location. Or it found the key but the ImagePath value points to a file that doesn't exist. The SCM then says "service not found" — even though the service name looks right. It's a registry corruption or orphaned entry.

Fix: Step-by-step

These steps assume you know the service name (like MyBrokenService). If you don't, use sc query to list all services and find the one that fails.

Open an elevated command prompt
Right-click Command Prompt and select Run as administrator. This is needed to access the service control manager and registry hives.
Check if the service key exists
Run this command (replace ServiceName with your actual service name):
```
reg query HKLM\SYSTEM\CurrentControlSet\Services\ServiceName
```
If you get an error like "The system was unable to find the specified registry key or value", the service entry is completely missing. That's your root cause. If the key exists but has no ImagePath value, same problem.
If the key is missing — reinstall the software
The best fix is to reinstall the application or driver that owns the service. Uninstall it first (use Programs and Features), then reinstall. This recreates the registry entry. If you can't reinstall (maybe the software is custom), you can create the key manually — but that's tricky. See step 4.
If the key exists but ImagePath is wrong or missing — fix it
Run reg add to set the correct ImagePath. You need to know where the service binary lives. Example:
```
reg add HKLM\SYSTEM\CurrentControlSet\Services\ServiceName /v ImagePath /t REG_EXPAND_SZ /d "C:\Program Files\MyApp\service.exe" /f
```
The /f flag forces overwrite. If the service is a driver (like a filter driver), the path is usually system32\drivers\driver.sys.
After that, run sc start ServiceName to test.
If the service is a driver — check the driver store
Some drivers (especially network or storage ones) have entries under HKLM\SYSTEM\CurrentControlSet\Services but the actual driver file is in C:\Windows\System32\drivers. If that file is missing, you'll get 0X000004DB. To check, run:
```
dir C:\Windows\System32\drivers\driver_name.sys
```
If the file is gone, reinstall the driver package (usually from the manufacturer's setup). Don't just copy the file — drivers have signed catalogs and version info.
Use sc delete to remove orphaned services
If you don't need the service anymore (like a leftover from uninstalled software), just delete it:
```
sc delete ServiceName
```
This removes the registry key and the service won't show up in services.msc. Then the error won't appear because the service isn't referenced anymore.

What to check if it still fails

If you followed the steps and the error persists, here are a few things to look at:

Check for a typo in the service name. Service names are case-insensitive but must be exact. Use sc query to list all services and match the name exactly.
Check if the service is a kernel driver. Some drivers need a reboot after installation. The SCM won't find them until after a restart. Reboot and try again.
Check if the service is disabled. Run sc qc ServiceName and look at the START_TYPE. If it's 4 (disabled), change it with sc config ServiceName start= auto (note the space after =).
Check for malware. Some malware removes service entries to hide itself. Run a full antivirus scan (Windows Defender offline scan works well). If malware is the cause, the fix is to remove it and reinstall the affected software.
Check permissions on the registry key. If your account doesn't have read access to the service's registry key, SCM might show "not found" even though the key exists. Use regedit to check the key's permissions. Right-click the key, select Permissions, and make sure SYSTEM and Administrators have Read access.

One more thing: If you're on Windows Server 2022 with Secure Boot enabled, some third-party drivers might be blocked from loading. Check the Event Viewer under System logs for a warning like "Code integrity determined that a driver has an invalid signature." In that case, you need to update the driver to a signed version or disable Secure Boot temporarily (not recommended for production).