Fix SPAPI_E_DI_POSTPROCESSING_REQUIRED (0x800F0226) in Windows
This error means a device's co-installer needs more work after install. The fix is to restart the driver installation or use a specific workaround in Device Manager.
Yeah, that error is annoying. It pops up right when you think the driver's done installing, and then nothing works. Here's the direct fix.
What Actually Causes This
Windows uses co-installers—small helper programs—to finish driver setup. The error 0x800F0226 means a co-installer flagged that it still has work to do, but Windows didn't let it finish. This often happens with USB devices (like 3G modems or serial adapters) or graphics drivers from vendors like NVIDIA or AMD on Windows 10 22H2 or Windows 11.
The Fix: Re-trigger the Co-Installer
- Open Device Manager (right-click Start, select Device Manager).
- Find the device with the yellow exclamation mark. It's usually under "Other devices" or "Universal Serial Bus controllers."
- Right-click the device and select Properties.
- Go to the Driver tab, click Update Driver, then Browse my computer for drivers.
- Pick Let me pick from a list of available drivers on my computer.
- If a driver shows up, select it and click Next. If nothing shows, check Show compatible hardware.
- Windows will re-run the co-installer. This time it should complete.
If that fails, uninstall the device completely (right-click, Uninstall device, check "Delete driver software for this device"), then reboot and let Windows re-detect the hardware.
Why Step 6 Works
The co-installer requires a specific driver INF file to be present and loaded into memory. When you pick from a list, Windows reloads the driver stack from scratch, which resets the co-installer's state. The first install might have left the co-installer in a partial state—probably a timing issue or a missing registry key. Reloading it gives it a clean slate.
Less Common Variations
- Driver Signature Enforcement: If you're on a 64-bit Windows 11 system and installed an unsigned driver, the co-installer might fail silently. Temporarily disable driver signature enforcement via Advanced Startup (hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings > Disable driver signature enforcement).
- Old USB Driver Cache: For USB Serial or CDC devices, the cached driver in
C:\Windows\System32\DriverStore\FileRepositorymight be corrupted. Delete the relevant folder (match by INF name) and reinstall. - Group Policy Blocks: In enterprise environments, Group Policy can prevent co-installers from running. Check
gpedit.mscunder Computer Configuration > Administrative Templates > System > Device Installation > "Specify the search server for device driver updates"—set it to "Not configured." - Legacy Hardware: Some older PCI or ISA devices need a manual co-installer executable (like
setup.exe) run after the driver install. Check the manufacturer's website for a separate installer.
Prevention
Most of this is caused by rushing the install. Let Windows finish its thing—don't reboot early or unplug the device mid-install. Always run the installer as Administrator. If you're dealing with a modem or serial device, install the driver package before plugging in the hardware. That gives Windows a chance to cache all the INF files and co-installer DLLs in the DriverStore before the device triggers Plug and Play.
For developers writing co-installers: never return ERROR_NO_WORK from CoInstaller without checking if you actually completed all required steps. Windows 10 and 11 are stricter about co-installer return codes since the 21H2 update.
Was this solution helpful?