SPAPI_E_DI_BAD_PATH (0X800F0214): Fix Device INF Path Error

Wrong Folder or Missing INF Files (Most Common)

I know this error is infuriating—you've got the driver folder, you click install, and Windows just says "nope, not finding anything here." Nine times out of ten, the problem is you're pointing to the wrong folder or the INF files aren't where you think they are.

This happened to me back in 2019 when I was helping a user install a Dell printer driver. They'd downloaded the ZIP, extracted it to a temp folder, and then pointed Device Manager to that temp folder. Problem was, the actual INF files were buried in a subfolder called Drivers\Win10\x64. Windows only looks one level deep by default, so it gave the SPAPI_E_DI_BAD_PATH error.

How to fix it

1. Open File Explorer and go to the folder where you extracted the driver files.
2. Look for any subfolders named Drivers, INF, x64, Win10, or similar. Double-click into them.
3. If you see files ending in .inf, that's your real driver folder. Copy the full path from the address bar.
4. In Device Manager, right-click the device with the yellow exclamation mark, choose Update driver > Browse my computer for drivers.
5. Paste that path into the location box. Make sure Include subfolders is checked—this catches INFs in nested folders.
6. Click Next.

If you're using pnputil or DISM to add the driver, the same rule applies. For pnputil, you'd run:

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

That /subdirs flag is critical. Without it, pnputil only scans the top-level folder—just like Device Manager.

If the folder contains no .inf files at all, the driver download is probably corrupt or incomplete. Redownload from the manufacturer's site and try again.

Driver Package Not Signed or Corrupt (Second Most Common)

Sometimes the folder is correct, but the INF file itself is bad. Windows checks for digital signatures on driver packages. If the signature is missing, expired, or broken, you'll get SPAPI_E_DI_BAD_PATH even though the file is right there.

I've seen this most often with older hardware—say, a 2015 webcam on Windows 11. The driver was signed for Windows 8.1, and Windows 11 quietly refused it. The error text doesn't say "signature bad," so it's easy to chase the wrong fix.

How to check and fix

1. Right-click any .inf file in the driver folder and choose Properties.
2. Go to the Digital Signatures tab. If it's missing or says "This digital signature is not valid," that's your problem.
3. For testing, you can temporarily disable signature enforcement: reboot and press F8 before Windows loads (or hold Shift while clicking Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 7 to disable driver signature enforcement).
4. Once booted, try installing the driver again. If it works, you've confirmed the signature issue.

But don't run with signature enforcement off permanently—that's a security risk. The real fix is to download a signed driver from the manufacturer, use a compatibility version, or if you're on a corporate network, deploy the driver using a tool that signs it internally.

For Windows 10 and 11, you can also try installing the driver in Safe Mode with Networking. Sometimes the signature check is less aggressive there. Boot to Safe Mode, install the driver, then reboot normally.

Corrupt Driver Store or PnP Cache (Third Most Common)

If the first two fixes didn't work, the problem might be inside Windows itself. The Driver Store and the Plug and Play cache can get corrupted—especially after failed driver installs or incomplete updates.

I had a user whose HP printer driver kept failing with this error on Windows 10 20H2. The folder was fine, the INF was signed, but every install attempt hit SPAPI_E_DI_BAD_PATH. Turns out, the driver cache had a stale entry that conflicted with the new install.

How to fix it

1. Open an elevated Command Prompt (right-click Start, choose Command Prompt (Admin) or Windows Terminal (Admin)).
2. Run this command to reset the driver store:

pnputil /cleanup

This removes unused driver packages from the store. It won't delete drivers that are currently in use.

3. Then run DISM to repair the system image—this catches deeper corruption:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for it to finish (could take 10-20 minutes). Don't interrupt it.

4. After DISM completes, run SFC:

sfc /scannow

5. Reboot your PC and try installing the driver again.

If pnputil /cleanup gives an error itself, you may need to manually delete stale driver entries. Run:

pnputil /enum-drivers

Look for any driver listed as Published Name that matches the one you're trying to install. Note the oemXX.inf name, then remove it with:

pnputil /delete-driver oemXX.inf

Replace oemXX.inf with the actual name. Then try the install again.

If you're still stuck, the driver package might be incompatible with your OS version—check the manufacturer's support page for a Windows 10/11 specific driver. Some old drivers simply won't work, and no amount of path-fixing will change that.

Quick-Reference Summary

This error is almost always a path or signature problem. Start with the folder check—it's the quickest fix. Move to signature and cache issues only if the first one doesn't stick. You'll be up and running in minutes.