Fix UPS error 0X000009B1 fast: NERR_UPSInvalidConfig

Error 0X000009B1 – The UPS service isn't configured correctly

You're getting 0X000009B1 (NERR_UPSInvalidConfig) when trying to start the UPS service on Windows Server. I've seen this more times than I can count — usually after someone moved a UPS to a new server or reinstalled the OS but forgot to redo the config. The service exists, but it can't parse its settings file. Let's get it working.

Fix 1: Check your ups.conf file (30 seconds)

The UPS service reads from %SystemRoot%\System32\ups.conf. Nine times out of ten, that file is missing, corrupted, or has a typo. Here's what to do:

1. Open Notepad as Administrator.
2. Navigate to C:\Windows\System32\ups.conf. If it's not there, create a blank file.
3. Paste this exact content for a basic serial UPS (adjust the COM port if needed):

[ups]
Driver=ups10
Port=COM1
BaudRate=9600

Save and close. Then restart the UPS service:

net stop ups
net start ups

If you're using a USB UPS (like most modern APC units), change the driver to usbhidups and set Port to auto. Had a client last month whose entire print queue died because someone left the port as COM1 for a USB UPS. Don't be that guy.

Still failing? Move to Fix 2.

Fix 2: Registry and service permissions (5 minutes)

The UPS service reads its settings from the registry too. If the config file is fine but the service still barfs, the registry key might be wrong or permissions are messed up.

1. Open regedit as Administrator.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UPS.
3. Double-check the ImagePath value. It should be %SystemRoot%\System32\ups.exe -k. If it's missing or points to a different path, correct it.
4. Check the Start value. Should be 2 (automatic) or 3 (manual). If it's 4 (disabled), change it to 2 and reboot.
5. Right-click the UPS key, select Permissions, and make sure SYSTEM and Administrators have Full Control. I once spent an hour on a server where a GPO had locked down the service key. Check that.

After any registry change, restart the service or reboot. Still getting the error? Move to Fix 3.

Fix 3: Reinstall the UPS service manually (15+ minutes)

When the config and registry are clean but the service still won't start, the service itself is hosed. I've seen this after a botched Windows Update or a rollback that didn't restore the UPS service files properly.

1. Open an elevated command prompt.
2. Stop and remove the current service:

net stop ups
sc delete ups

3. Reinstall the service from the system files:

sc create ups binPath= "%SystemRoot%\System32\ups.exe -k" start= auto DisplayName= "Uninterruptible Power Supply"

4. Recreate ups.conf from scratch (use Fix 1 as a template). Then start the service:

net start ups

If that fails with an access denied, you probably have a corrupt ups.exe or missing DLLs. Run SFC:

sfc /scannow

Wait — it'll take 15 minutes. After SFC finishes, repeat the sc create and net start steps. If it still won't start, copy ups.exe from a known good machine (same OS version) to C:\Windows\System32\ and try again.

Still stuck?

Check the Windows Event Viewer under System logs for more details on the error. I've seen third-party UPS software (like APC PowerChute) take over the service and break it. Uninstall any third-party UPS tools, then redo Fix 3. If you're running Windows Server 2019 or 2022, also check that the UPS service isn't blocked by a firewall rule — yes, I've seen that.

One last thing: if the error persists, the UPS itself might be sending garbage data. Disconnect the UPS cable, start the service (it'll run but won't monitor), then reconnect the cable. That forced a re-initialization for a client last week. Good luck — you've got this.