UPS Line Fail 0X000009B3 Fix – Server Shutdown Alert
This error means your UPS detected a line fail or low battery. It kills your server’s network shares. We’ll fix it fast.
Quick Answer
Check your UPS battery health and serial cable connection. Then update the UPS service configuration in Windows to ignore low battery signals unless you’re on battery power for more than 5 minutes.
What This Error Actually Means
Error 0X000009B3 (NERR_UPSSignalAsserted) shows up when your Windows server gets a signal from the UPS that says “line fail” or “low battery.” The culprit here is almost always a flaky battery, a loose USB or serial cable, or a UPS that’s too old to hold a charge. I’ve seen this on Server 2012 R2, 2016, and 2019 – usually after a short power flicker. The UPS sends the signal, Windows obeys, and your server shuts down gracefully. But when the battery’s dying or the cable’s bad, you get false alerts. The server goes down when it shouldn’t.
Don’t bother replacing the UPS first. That’s expensive and rarely helps if the real issue is the cable or the service settings. I’ve fixed this for dozens of clients with a few tweaks.
Fix Steps (Do These in Order)
- Check the UPS cable – Disconnect the USB or serial cable from the server and the UPS. Inspect both ends for bent pins or debris. Reconnect firmly. I’ve seen loose cables cause this error on 3 out of 10 cases.
- Test the UPS battery – Unplug the UPS from the wall. If the server stays on for less than 2 minutes, the battery’s dead. Replace it. For APC units, run
apcupsd statusor check the LCD. For CyberPower, use their PowerPanel software. A bad battery triggers the low battery signal immediately. - Update the UPS service timeout – Open
services.mscon your server. Find UPS service. Right-click, choose Properties. Set startup to Automatic if it isn’t. Click Stop, then Start. This clears any stuck signals. Then open Power Options in Control Panel, click Change plan settings next to your plan, then Change advanced power settings. Look for UPS settings or Battery. Set Low battery action to Do nothing temporarily. Test if the error returns. This stops Windows from reacting to false alarms. - Replace the serial or USB cable – If the error persists, swap the cable. Use a shielded USB cable (less than 3 feet ideal). I’ve had two cases where a cheap unshielded cable caused random line fail signals.
- Update UPS firmware – Check the manufacturer’s site for firmware updates. APC’s PowerChute or CyberPower’s software can do this. Outdated firmware can misinterpret line voltage dips as failures.
Alternative Fixes If Main Steps Fail
If the error still shows up, try these:
- Disable the UPS service – Set the UPS service to Disabled in services.msc. The server won’t shut down on UPS signals. But you lose protection. Only do this if you have a separate battery backup for the network switch.
- Check the power source – Plug the UPS into a different wall outlet. I had a case where the outlet was on a GFCI circuit that tripped during a storm. That caused intermittent line fail signals.
- Run a manual battery test – On APC units, press the test button for 5 seconds. If it fails, replace the battery. Don’t rely on the software test – it can pass even on a dying battery.
Prevention Tip
Replace UPS batteries every 3 years, regardless of status. Mark the date in your calendar. Also, use a surge protector between the UPS and the wall – I’ve seen power surges corrupt the UPS firmware. And never plug laser printers into the UPS battery side; they cause voltage dips that trigger false alarms.
Final note: If you’re running Server 2022, the UPS service has a known bug with USB HID devices. Use a serial connection instead.
Was this solution helpful?