Fix SPAPI_E_ERROR_NOT_INSTALLED 0x800F1000 Windows

SPAPI_E_ERROR_NOT_INSTALLED (0x800F1000) means Windows can't find the driver package or component it's trying to install. Here's how to clear it fast.

Quick answer: 0x800F1000 means the driver package or INF file you're pointing at isn't actually present in the DriverStore — either it was never staged, it was removed by cleanup, or you're running the install from the wrong folder.

I hit this one a lot with old print drivers and OEM chipset packages. Last month a client's HP LaserJet install kept throwing 0x800F1000 from a batch script their previous MSP left behind. The script referenced an INF path that had been cleaned out by Storage Sense months earlier. Real fix took four minutes once I stopped trusting the script.

What's actually happening: SetupAPI is being asked to install a component, it queries the DriverStore, and gets nothing back. Windows doesn't ship missing drivers in a hidden folder somewhere. If the package isn't staged or the INF isn't where you say it is, you get this error. It's not a corruption error, it's a "you gave me nothing to install" error.

Fix 1: Verify the INF path actually exists

Before anything else, open an elevated Command Prompt and check the file is really there. I've seen this fail because someone typed C:\Drivers\HP when the folder was C:\Driver\HP.

dir "C:\Path\To\Your\Driver\*.inf"

If that returns nothing, you've got your answer. Grab the correct package from the vendor and start over.

Fix 2: Run install with pnputil instead of Device Manager

Device Manager hides the real error. pnputil tells you what's wrong. Open an admin Command Prompt:

pnputil /add-driver "C:\Path\To\Driver.inf" /install

If it still throws 0x800F1000, the INF is malformed or the referenced files (SYS, CAT, DLL) aren't in the same folder. A missing CAT file alone will trigger this on Windows 10 22H2 and Windows 11 23H2+. Check the INF with a text editor — look for CopyFiles= directives and confirm every file it names is sitting next to it.

Fix 3: Check for an existing (broken) driver entry

Sometimes the driver is half-installed and Windows won't overwrite it. List what's staged:

pnputil /enum-drivers

Find the OEM number (like oem42.inf) matching the device, then delete it:

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

Reboot, then run Fix 2 again. This one clears the error about 60% of the time in my experience, especially on print and audio drivers.

Fix 4: Repair the component store

If pnputil keeps failing, the component store itself might be damaged. This is more common after a botched Windows Update or a system restore that rolled back partially. Run these in order:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

RestoreHealth pulls clean files from Windows Update. If the machine has no internet or WU is broken, mount a matching ISO and point DISM at it with /Source:wim:D:\sources\install.wim:1 /LimitAccess.

Fix 5: Rebuild the DriverStore index

Rare but real — I saw this on a machine that had been through three in-place upgrades. The DriverStore\FileRepository index was out of sync. Fix from an admin prompt:

takeown /f C:\Windows\System32\DriverStore\FileRepository /r /d y
icacls C:\Windows\System32\DriverStore\FileRepository /grant Administrators:F /t

Then re-run pnputil. Don't delete anything in FileRepository by hand. I've watched people do that and end up with a desktop that boots to a black screen.

Alternative: install via Windows Update or the vendor's setup

If the manual INF route keeps failing, stop fighting it. Download the full vendor installer — Dell Command Update, Lenovo Vantage, HP Support Assistant, whatever matches the box. Those packages bundle the right INF and handle the DriverStore staging properly. For printers, grab the full driver package from the manufacturer's site, not the "basic driver" Windows Update offers.

Running an OEM's universal package is faster than debugging a hand-rolled INF 9 times out of 10.

Prevention

Don't let third-party cleaners wipe the DriverStore. Tools like older CCleaner versions and some "PC optimizers" flag DriverStore entries as junk. They're not. Also, when you script driver installs, check the INF path exists before calling pnputil, and log the output. And keep vendor driver packages on a share you control instead of pulling them fresh every time — that's how half the 0x800F1000 errors I see get started in the first place.