SPAPI_E_NO_BACKUP (0x800F0103): Driver install fails — files not backed up

What's actually happening here

The error SPAPI_E_NO_BACKUP (0x800F0103) appears when you try to install a driver and Windows can't find or create the backup files it needs to uninstall the previous driver. The operating system wants to keep a rollback snapshot of the old driver files in the driver store (C:\Windows\System32\DriverStore\FileRepository). Something has gone wrong with that process.

I've seen this most often after a failed driver update, a corrupted system restore point, or when someone has manually deleted files from the DriverStore folder to free up space. Windows 10 and 11 both throw this error, and it's especially common with graphics and network drivers.

1. Corrupted driver store or system files

This is the number one cause. The driver store itself has gotten into a bad state — maybe a partial install left the queue in an inconsistent state, or system files that handle backup creation are damaged. The fix is to repair those system files first.

Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or Terminal (Admin)). Run these in order:

DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW

DISM checks the component store for corruption and fixes it using Windows Update as the source. SFC then checks all protected system files against that cleaned-up store. The reason step 3 works is because DISM repairs the underlying component store that SFC pulls from. If you skip DISM and run SFC first, SFC might report it found corrupt files but couldn't fix them.

After both complete — and they can take 10-20 minutes on older hardware — reboot. Then try your driver install again. If the error persists, move to the next cause.

2. Pending driver operations blocking the queue

Sometimes a previous driver install or uninstall didn't finish cleanly. The driver queue has a stuck operation that prevents Windows from creating a new backup. You can see this by checking the PnP device installation status.

Open Device Manager (devmgmt.msc), go to View > Show hidden devices. Look for any device with a yellow exclamation mark or one that says "This device is not working properly." Right-click and uninstall it. If you see "Unknown devices," uninstall those too — they're often remnants of incomplete driver operations.

For a more thorough cleanup, open an elevated Command Prompt and run:

pnputil /enum-devices /problem

This lists devices with problems. Note the instance ID. Then clean them:

pnputil /remove-device /deviceid "<instance-ID>"

The reason this works is that pnputil interacts directly with the PnP manager's device tree and driver store, bypassing higher-level caches. If a driver package is still referenced but the files are missing or corrupted, this command removes the reference cleanly.

After removal, reboot and install your driver fresh.

3. Insufficient disk space or permissions on the DriverStore

This one's less common but easy to miss. The driver store needs room to store backup files — typically 200-500 MB per driver package. If your system drive is nearly full, Windows may refuse to create the backup and throw SPAPI_E_NO_BACKUP.

Check free space on C:\. If it's below 5 GB, you're in the danger zone. Run Disk Cleanup (cleanmgr.exe) and select "Clean up system files." Check "Driver packages" and "Device driver packages" — these can free up gigabytes.

Also check permissions on C:\Windows\System32\DriverStore\FileRepository. Right-click the folder > Properties > Security. Make sure SYSTEM and Administrators have Full Control. I've seen third-party security software lock this folder down.

If permissions are wrong, take ownership:

takeown /f C:\Windows\System32\DriverStore\FileRepository /r /d y
icacls C:\Windows\System32\DriverStore\FileRepository /grant Administrators:(OI)(CI)F /T

Then reboot and retry the install.

Quick-reference summary

Start with the system file repair — it fixes about 70% of cases. If that doesn't do it, check for stuck devices. Disk space is the last thing I'd check, but it's the easiest to rule out.