Fix SPAPI_E_INVALID_FILTER_DRIVER (0X800F022C) on Hard Drives

1. Corrupted or Wrong Filter Driver in the Registry (Most Common Fix)

I know this error is infuriating. You try to update a driver or plug in an external drive, and Windows throws SPAPI_E_INVALID_FILTER_DRIVER (0X800F022C). Nine times out of ten, the culprit is a bad entry under the UpperFilters or LowerFilters registry key for your hard drive controller.

This tripped me up the first time too. Antivirus software, old disk encryption tools, or even a failed Windows update can leave a garbage filter driver reference in the registry. Windows tries to load it, realizes it's bogus, and stops the device dead.

How to fix it

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
   (That's the GUID for hard drive controllers.)
3. Look for UpperFilters and LowerFilters on the right side. If they're there, right-click and delete them.
4. Close regedit and restart your PC.

This removes any invalid filter that Windows is choking on. After reboot, the drive should appear in Device Manager without the error. If you still see the problem, move to the next cause.

Pro tip: Before deleting, export the key just in case (right-click the folder → Export). I've never needed to restore it, but it's a good safety net.

2. Third-Party Filter Driver from Disk Tools (Antivirus, Encryption, or CD Emulators)

If the registry cleanup didn't work, the problem is likely a real, installed filter driver that's corrupted or incompatible with your current Windows version. Programs like Daemon Tools, Alcohol 120%, VeraCrypt, or even some antivirus suites install their own lower filters to intercept disk reads/writes. If that driver file gets corrupted or the app is partially uninstalled, Windows sees the invalid filter.

How to find and remove it

1. Open Device Manager (right-click Start → Device Manager).
2. Expand Disk drives. Look for any device with a yellow exclamation mark.
3. Right-click that device → Properties → Details tab.
4. In the Property dropdown, select Upper filters or Lower filters. If the value shows a driver name you recognize, that's your suspect.
5. Uninstall the offending program via Settings → Apps. If it's an antivirus, use the manufacturer's removal tool (they often leave leftovers).
6. Restart your PC and check if the error is gone.

If you don't recognize the driver name, Google it. Common offenders are partmgr.sys (legit, don't touch it) or sbp2port.sys (IEEE 1394, which is fine). But cdrom.sys or random vendor files are often the bad guys.

3. Windows Filter Driver Cache Corruption (Less Common but Stubborn)

Sometimes the registry and installed drivers are clean, but Windows's internal filter driver cache is scrambled. This can happen after a major Windows update (like 22H2 to 23H2) that doesn't flush the old cache properly. The result: Windows still tries to load a filter from an older driver store that's no longer valid.

How to clear the filter cache

1. Open an admin Command Prompt: right-click Start → Windows Terminal (Admin).
2. Run this command to reset the driver store:
   pnputil /delete-driver * /force
   (This removes all third-party drivers from the store. You'll need to reinstall your graphics and storage drivers after.)
3. Next, clear the filter manager cache:
   fltmc unload (will fail – ignore it)
   fltmc detach *
4. Restart your PC. Windows will rebuild the cache from scratch.

This is the nuclear option. I've used it on maybe 2% of cases, and it's always been the last resort. But when the first two fixes fail, this one works.

Quick-Reference Summary Table

That's it. Start with the registry fix, move to uninstalling suspect software, and only go nuclear if you have to. This error looks scary, but it's almost always just a stale reference that needs cleaning out.