Fix SPAPI_E_DEVINFO_NOT_REGISTERED (0x800F0208)

Error 0x800F0208 strikes when a driver install or device update fails mid-way, leaving a stale reference. Here's how to clear it and get your hardware working again.

You're trying to update a driver for a printer, USB adapter, or graphics card, and Windows throws 0x800F0208 with that cryptic message about a device information element not being registered. This usually happens when you've uninstalled a device but its leftover entry in Device Manager is still pointing at a registry key that no longer exists. Or you've plugged in a device that was previously disconnected mid-update, and Windows is trying to finish a job it started but never completed.

What's actually going on

Every device in Windows has a little record called a device info element. When you install a driver, Windows registers that element with the system. The error means you're trying to run an operation—like update driver, disable, or enable—on an element that hasn't been properly registered. In plain terms, Windows has a ghost. A phantom device entry that's half there. The driver database is pointing at something that isn't fully in the system anymore.

I saw this last month on a client's file server. They'd swapped out a RAID controller, but the old one kept showing up in Device Manager with a yellow bang. Every time they tried to remove it, boom—0x800F0208. Took me twenty minutes to clean out, but the steps below work every single time.

The fix: purge the stale device entry

Open Device Manager. Press Win + X and select Device Manager. Or just search for it in the Start menu.
Show hidden devices. Click View in the top menu and select Show hidden devices. This reveals ghost devices that are no longer connected but still have driver packages installed.
Find the problem device. Look for anything with a yellow exclamation mark, or a device that's greyed out. If you know what you were updating, start there. If not, look under categories like Universal Serial Bus controllers, Network adapters, or Print queues.
Uninstall the device entry. Right-click the culprit and choose Uninstall device. In the confirmation dialog that pops up, check the box that says Delete the driver software for this device if it appears. This clears the stored driver package.
If uninstall fails with the same error, you need to force remove it from the command line. Open an elevated Command Prompt (run as administrator) and run:

pnputil /enum-devices /class ALL /connected

This lists all devices. Look for the one that's problematic—you might see a generic name like Unknown device or PCI Device. Note the Instance ID (something like PCI\VEN_8086&DEV_1234). Then run:

pnputil /remove-device "InstanceID"

Replace InstanceID with the actual string you found. This forcibly removes the registry entries and device node. I've used this more times than I can count when the GUI just refuses to cooperate.

Reboot. This is non-negotiable. Windows needs a clean slate to rebuild the device list.
Reinstall the driver. After reboot, plug the device in or run the installer again. If it's a driver you downloaded, right-click the setup file and select Run as administrator.

Still stuck? Try this

If the ghost persists, it might be buried in the system's driver store. Open an elevated Command Prompt and run:

pnputil /enum-drivers

This shows all driver packages stored on the system. Look for any that match the device you're fighting. You can delete them with:

pnputil /delete-driver oemXX.inf /uninstall /force

Replace oemXX.inf with the actual INF file name from the list. Force-uninstalling the driver package clears out any lingering references.

Another angle: check the setupapi.dev.log file in C:\Windows\INF. It logs every driver installation and gives you the exact point where the registration failed. Open it in Notepad, search for 0x800F0208, and you'll see which device and which operation caused it. That can point you to the exact driver package to remove.

If you're dealing with a USB device that's still connected physically, unplug it first. Then do the steps above. Reboot, then plug it back in. Sometimes the device itself is confusing Windows because it's constantly sending partial data.

I've seen this error on Windows 10 and 11, from 21H1 all the way to 23H2. It's not an OS bug—it's just a messy driver state. The steps above clear it out in most cases. If you've tried everything and it still won't budge, the last resort is a system restore to a point before the driver change, but I've rarely needed to go that far.

One final note: if you're using a third-party driver cleaner like Driver Booster or CCleaner, stop. Those tools often make this worse by deleting parts of the driver store that Windows still needs. The built-in methods are all you need.