Fix 0x800F023F: SPAPI_E_NO_AUTHENTICODE_CATALOG Error

Driver install fails because Windows can't verify the .cat file. Usually a signing cert issue or a bad driver download. Fix it in under a minute with the first step.

What's Going On?

You're trying to install a driver — maybe for a USB device, a PCI card, or some obscure piece of hardware — and Windows throws up SPAPI_E_NO_AUTHENTICODE_CATALOG (0x800F023F). The short version: Windows can't find a signed catalog file (.cat) that matches the driver's hash. This usually happens with older hardware, cheap knockoff devices, or when you downloaded a driver from a shady site that stripped the signing.

I've seen this most often with budget USB-to-serial adapters, older network cards, and third-party printer drivers on Windows 10 22H2 and Windows 11. The culprit here is almost always a missing or corrupted .cat file — sometimes the driver package itself is the problem. Let's fix it.

The 30-Second Fix: Re-Download the Driver

Don't overthink this. Half the time, the driver you downloaded got mangled during the download or the vendor's site served a broken package. Go back to the manufacturer's official site, grab the latest signed driver for your exact Windows version, and reinstall. Skip third-party driver updaters — they're garbage for this error.

If the driver is from a known brand (Intel, Realtek, TP-Link), check that the file size matches what's listed on the site. Mismatch? You got a corrupted download. Delete it and start over.

The 5-Minute Fix: Temporarily Disable Driver Signature Enforcement

If a fresh download still fails, Windows is being picky about the signature. You can force the install by disabling driver signature enforcement temporarily. This is safe for most scenarios — just remember to turn it back on after the install.

On Windows 10 & 11

Open Settings > Update & Security > Recovery.
Under Advanced startup, click Restart now.
After reboot, go to Troubleshoot > Advanced options > Startup Settings > Restart.
Press 7 or F7 to select Disable driver signature enforcement.

Once the system boots, install your driver. It'll work even if the .cat file is missing or unsigned. After the install, reboot normally — enforcement comes back.

Don't leave enforcement off. It's a security risk. Malware can sneak in rootkits if you keep it disabled.

The 15+ Minute Fix: Manually Add the Catalog File or Re-Sign the Driver

If you're still stuck, the driver package itself lacks a proper .cat file, or the one it has is invalid. Here's how to dig into it.

Step 1: Check the Driver Package

Extract the driver's .inf and .cat files. Look for the .cat file inside the package. If it's missing entirely, you're probably using a beta or unsigned driver. Search for a WHQL-signed version on the vendor's site.

Step 2: Clear the Driver Store Cache

A corrupted cached copy can cause this. Run this in an admin Command Prompt:

pnputil /delete-category /force

Then reinstall. This clears stale driver packages from the store.

Step 3: Manually Sign the Driver (Advanced)

If you're desperate and the hardware works fine otherwise, you can create a self-signed catalog. This is a last resort — it won't pass WHQL but will shut Windows up.

Install the Windows Driver Kit (WDK) from Microsoft — it includes inf2cat.exe and signtool.exe.
Open an admin Developer Command Prompt for VS 2022 (or whatever version you have).
Navigate to the driver folder with the .inf file.
Run:
```
inf2cat /driver:. /os:10_x64
```
(Change 10_x64 to your OS — 10_x86, 6_3_x64 for Win 8.1, etc.). This creates a .cat file.

Now sign it with a test certificate:

signtool sign /fd SHA256 /a /n "YourTestCert" /t http://timestamp.comodoca.com/authenticode MyDriver.cat

Install the test certificate into the Trusted Root Certification Authorities store on your machine.
Install the driver normally.

This is overkill for most people. Only do it if you're comfortable with command-line tools and certificate management. For most users, the first two fixes solve it.

Why This Error Happens in the Real World

I've hit this error most often with:

Older USB-to-serial adapters (Prolific PL2303, FTDI clones) — the manufacturers stopped signing their .cat files, or you bought a counterfeit.
Budget PCIe Wi-Fi cards from no-name brands that reuse unsigned drivers.
Windows Insider builds — Microsoft sometimes changes signature requirements mid-flight, breaking catalogs for older hardware.

If none of these fixes work, the hardware is probably dead to modern Windows. Replace it with something WHQL-certified. It's not worth the headache.