Device Manager Error Code 28 Fix

You're in the middle of a driver installation or OS reinstall, and at around 20% progress, Device Manager throws Code 28: drivers not installed. This usually happens when the Windows driver cache is missing entries or the Update Service refuses to serve the correct package. In some cases, the error appears right after connecting new hardware.

Quick attempt — Delete pending.xml (one method)

Instead of chasing multiple complex repairs, start here. Deleting Pending.xml resets the driver installation state and often clears Code 28 without touching anything else.

net stop wuauserv
net stop bits
del C:WindowsWinSxSPending.xml /f
net start wuauserv
net start bits

After that, reboot and let Windows try to install the driver again. Did it fix the error? Not always — but many IT admins reported that this single step resolved the missing driver message immediately.

If this didn’t fix it at first (branch logic): the next logical step is resetting CBS components. But for the sake of minimal interference, we won’t dive into that here. Just know that DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow become relevant if Pending.xml reappears.

What you should check after the command

• Open Device Manager → right-click the problem device → Update driver → Search automatically.
• If still Code 28, go to the vendor’s site and grab the exact driver (don’t rely on generic ones).
• Look into C:WindowsLogsCBSCBS.log for entries like “failed to install driver” around the 20% mark — that’s the unique signal (KB5147689 references this exact log pattern).

Sometimes you search for “how to fix code 28 drivers not installed” or “windows 11 code 28 solution” and end up with a ten‑step guide. But in real practice, cleaning the pending state solves it faster. Another common query — “install driver fix code 28” — leads to the same conclusion: the system is stuck because a previous installation attempt left a half‑baked XML entry.

How you’ll know it’s fixed

• Drivers installed successfully (no yellow bang in Device Manager).
• No Code 28 error when you reopen the properties page.
• The device is recognized correctly (correct name and model shown).

That’s it — a WORKING Driver Install Solution without overcomplicating things. If the issue persists, the real culprit might be a locked driver cache, but for many systems the Pending.xml deletion is the final FIX Code 28 approach you need.

Environment nuance: Windows 10 allows manual driver installs more easily, while Windows 11 restricts unsigned drivers, which can trigger Code 28 even after this fix. In that case, temporarily disable driver signature enforcement (Shift+Restart → Troubleshoot → Startup Settings) before repeating the steps above.