ERROR_FLT_CBDQ_DISABLED 0x801F000E Quick Fix

What This Error Means

You're seeing ERROR_FLT_CBDQ_DISABLED (0x801F000E) because the Windows Filter Manager has shut down a callback data queue. This usually happens when a third-party minifilter driver (antivirus, backup software, or disk encryption tool) gets partially uninstalled or crashes during a driver update. The queue gets stuck in a disabled state and won't re-enable on its own.

I've seen this most often with older Symantec, McAfee, or Sophos installations that didn't clean up properly. Also happens when someone force-kills a disk backup process mid-scan.

Let's fix it. Start at step 1 and only move down if needed.

Step 1: Restart the Filter Manager (30 seconds)

This is the quickest fix and works more often than you'd think. Open Command Prompt as Administrator and run:

fltmc load fltmgr

That reloads the Filter Manager driver without a reboot. If you get "The service has not been started", run this instead:

net start fltmgr

Then check if the error clears. If it does, you're done. If not, move on.

Pro tip: If the fltmc command isn't recognized, you're missing the Filter Manager tools. Install them via dism /online /add-capability /CapabilityName:Tools.~~ – but that's a rabbit hole. Just reboot instead and retry.

Step 2: Unload and Reload Problem Filters (5 minutes)

Sometimes a specific filter driver is the culprit. List all active filters with:

fltmc filters

Look for anything with a status other than Running or anything that looks like an old AV driver (e.g., SymProtect, McPvDrv, Sophos). Unload it with:

fltmc unload <filter_name>

Replace <filter_name> with the actual name from the list. For example:

fltmc unload SymProtect

After unloading, try your original operation again. If the error disappears, that filter was the problem. You can leave it unloaded, but it'll reload on next boot unless you uninstall the software properly.

No luck? Let's go deeper.

Step 3: Check Registry for Corrupted Queue Settings (15+ minutes)

This is where things get manual. The callback data queue state is stored in the registry. A corrupt entry here can keep the queue disabled even after reloading fltmgr.

Back up your registry first. I'm serious. This is a sensitive area and a wrong delete can make filters stop working entirely.

Open Regedit as Administrator.

Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FltMgr\Instances

Look for a subkey named CallbackDataQueue or something similar (it might be named after your AV product).
If you see a DWORD value Enabled set to 0, change it to 1.
Delete any orphaned instance subkeys that don't match an actually installed filter driver. To check which filters are registered, run:
```
fltmc instances
```
Compare that list to what's in the registry under Instances. Delete any that don't appear in the command output.
Reboot – this is non-negotiable after registry changes here.

Most of the time, you'll find a leftover instance from a partial uninstall. That's your culprit.

Step 4: System File Checker and DISM (Last Resort)

If none of the above worked, the Filter Manager core files might be corrupted. Don't bother with SFC first – go straight to DISM:

dism /online /cleanup-image /restorehealth

After that finishes (it'll take 5-10 minutes), run:

sfc /scannow

Reboot after both complete. This fixes underlying corruption but won't touch the registry settings from step 3. If you skipped step 3, go back and do it.

When All Else Fails: In-Place Upgrade

If you're still seeing 0x801F000E after all that, the Windows image is probably hosed beyond simple repair. An in-place upgrade (keeping your files and apps) is the nuclear option. You'll need a Windows 10 or 11 installation ISO. Mount it, run setup.exe, and choose "Keep personal files and apps". This replaces all system files including fltmgr.sys without wiping your data.

I've only needed this once in 14 years. Steps 1-3 fix 98% of cases. Stick with those.