Fix SPAPI_E_NO_SUCH_DEVINST (0x800F020B) Error

I've seen this error more times than I can count. You swap out a graphics card, unplug a USB hub, or move an internal drive to a different SATA port, and then—bam—you try to install a driver or update a device and get SPAPI_E_NO_SUCH_DEVINST (0x800F020B). It's Windows telling you the device it expects isn't where it used to be.

Don't freak out. This isn't hardware failure. It's a record-keeping glitch in the driver store. The device instance ID Windows cached doesn't match anything in the hardware tree. Here's how to clear that mismatch.

Cause 1: Stale Device Entry in Device Manager

Most common trigger: you physically removed or replaced a device, but Windows still holds onto its old instance. This happens a lot with internal components (SSDs, GPUs) and USB devices that were swapped while the system was on.

Here's the fix.

Open Device Manager. Hit Win + X and select Device Manager.
Click View > Show hidden devices. You'll see grayed-out entries for devices that aren't physically present.
Look for the device that's giving you the error. It might be under Other devices (with a yellow exclamation) or under its normal category (still grayed out).
Right-click the ghost device and select Uninstall device. Check Delete the driver software for this device if prompted.
Restart your PC.

After the restart, Windows will rebuild the hardware tree. Plug your device back in (if it's external) and let Windows detect it fresh. The error should be gone.

When this fails: sometimes the ghost device won't show even with hidden devices enabled. That's when you need the command-line version.

Command-Line Cleanup

Open Command Prompt as admin. Then run:

set devmgr_show_nonpresent_devices=1
devmgmt.msc

This forces Device Manager to show ALL non-present devices. Then repeat the uninstall steps above. I've seen this trick work on Windows 10 22H2 and Windows 11 23H2.

Cause 2: Corrupted Driver Package in the Store

Second most common cause: the driver package itself is corrupted or its INF file references a device instance that doesn't exist anymore. This happened to me once after a Windows Update that botched a display driver.

You'll know this is the case if the device still shows up in Device Manager (not ghosted) but any driver update or reinstall throws the 0x800F020B error.

Fix: purge the offending driver package from the store using pnputil.

Steps:

Open Device Manager, find the problematic device, go to Properties > Details tab, and select Hardware Ids from the dropdown. Copy the string that looks like PCI\VEN_... or USB\VID_....
Open Command Prompt as admin.
Run:
```
pnputil /enum-drivers
```
This lists all driver packages. Look for ones that match your device's hardware ID. Note the Published Name (something like oemXX.inf).
Delete the driver package:
```
pnputil /delete-driver oemXX.inf /force
```
Replace oemXX.inf with the actual name.
Restart your PC, then reinstall the driver from the manufacturer's website.

Heads up: /force will delete the driver even if it's in use. Only use this if you're sure the driver isn't needed by another device. When in doubt, just uninstall the device first, then run the delete.

Cause 3: Registry Leftover from a Deleted Device

This one's rare but nasty. A registry key under HKLM\SYSTEM\CurrentControlSet\Enum still references a device instance that no longer exists. This usually happens after a failed driver uninstall or a forced removal of a device in safe mode.

You need to manually delete the registry key—but only if you're comfortable editing the registry. Make a backup first.

Steps:

Open Registry Editor (regedit) as admin.
Navigate to:
```
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI
```
(or the appropriate bus for your device, like USB, ACPI, etc.)
Look for a subkey matching the device's instance ID. The instance ID is the long alphanumeric string after the hardware ID in Device Manager's details pane. Example: VEN_10DE&DEV_1C82&SUBSYS_....
Right-click the key and delete it. Confirm.
Close regedit and restart your PC.

After the restart, Windows should rebuild the hardware tree fresh. Plug your device back in, and the error should be gone.

Important: Deleting the wrong key can break your system. Only delete keys you're certain belong to the error-causing device. If you're unsure, skip this fix and try the first two.

Quick-Reference Summary Table

Cause	Symptom	Fix	Difficulty
Stale device entry	Device shows grayed-out in Device Manager after hardware swap	Uninstall ghost device (show hidden first)	Beginner
Corrupted driver package	Error on driver update; device visible but can't install	Delete driver package with pnputil /delete-driver	Intermediate
Registry leftover	Device not visible at all; error during install of new driver	Delete orphaned registry key under HKLM\Enum	Advanced

This error is frustrating, but it's almost always a Windows records problem, not a hardware problem. Try the fixes in order: start with the ghost device, move to the driver store, and only touch the registry as a last resort. You'll be back up and running in 15 minutes.