Fix 0X0000088C: Bad service program name error

Quick fix (30 seconds) — check the config file

I've seen this error on Windows Server 2016 and 2019 mostly. It pops up when a service can't find the program it's supposed to run. The fastest thing to try is opening the config file that's causing trouble.

Look for any file named *.conf or *.ini in these folders:

C:\Windows\System32\
C:\ProgramData\
C:\Program Files\ (your app's folder)

Open it in Notepad. Find the line that says ServiceName= or ProgramName=. Make sure the name matches exactly what's in Services.msc. Had a client last month whose print queue died because someone renamed a service but not the config file — took me 30 seconds to spot.

If you don't see a config file, move on.

Moderate fix (5 minutes) — check the registry

The real fix is often in the registry. The error code 0X0000088C maps to NERR_BadServiceProgName, which means the ImagePath value under a service key is wrong.

Open regedit.exe as Administrator. Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Find the service that's failing. You can identify it by looking in Event Viewer under System logs — look for event ID 7000 or 7023 with this error code. Once you find it, right-click the service key and export it (just in case). Then double-click ImagePath on the right.

Check two things:

Is the path valid? Does the .exe or .dll actually exist at that location?
Is the service name correct? Some apps use a display name, not the internal service name. For example, if you see \"My Custom App\" but the internal name is MyCustomApp, that's your bug.

Fix the path, close regedit, and restart the service with net start [servicename] in an admin command prompt. If it starts clean, you're done. If not, proceed to the next step.

Advanced fix (15+ minutes) — rebuild the service entry

Sometimes the registry key itself got corrupted. I've seen this after a bad Windows update or a failed uninstall. Here's what I do:

Open an admin command prompt.
Run sc query [servicename] to check if the service is listed. If it says "FAILED 1060", the service doesn't exist — you need to recreate it.
To recreate, run:

sc create [servicename] binPath= "C:\Path\To\YourApp.exe" start= auto DisplayName= "Good Display Name"

Replace [servicename] with the internal name (no spaces usually). The binPath= must point to the actual executable. For a service that's a DLL, use %SystemRoot%\System32\svchost.exe -k [servicename].

After that, run sc start [servicename]. If it still fails, check the Event Viewer for more clues. Sometimes the fix is just deleting the old registry key entirely and letting the app re-register itself. I did that for a client who had an old antivirus leftover — error gone in 2 minutes.

If none of this works, you might have a damaged system file. Run sfc /scannow from an admin prompt. But honestly, 9 times out of 10, it's just a typo in the service name or path.

Pro tip: Before you mess with the registry, take a snapshot of the service settings. Export the whole key. Worst case, you can merge it back.