STATUS_FLT_CBDQ_DISABLED Error Fix (0XC01C000E)

You're staring at an error that makes no sense—0XC01C000E, STATUS_FLT_CBDQ_DISABLED. I get it. It's cryptic and annoying. Let's fix it right now.

The Quick Fix: Re-enable the Queue via Registry

This error means the filter manager (FltMgr) has turned off the callback data queue for a particular minifilter driver. That queue is what lets the driver talk to the system when files change. When it's off, the driver throws this status code.

The fastest fix is to delete the registry key that disables the queue. Here's how:

Press Win + R, type regedit, and hit Enter.
Go to this path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FltMgr\

Look for a subkey named CallbackDataQueueEnabled or DisableCallbackDataQueue. If you find it, right-click and delete it.
If you don't see it, don't panic. That's actually good—it means the queue isn't disabled at the global level. The problem might be in a specific driver's key.

After deleting, restart your computer. When you log back in, run the operation that caused the error. You should see it working now.

If you'd rather use a command prompt instead of digging through the registry, here's the one-liner:

reg delete "HKLM\SYSTEM\CurrentControlSet\Services\FltMgr" /v CallbackDataQueueEnabled /f

Why This Works

The filter manager has a safety mechanism. When a minifilter misbehaves—say, it doesn't respond quickly enough to I/O requests—FltMgr disables that filter's callback data queue. This stops the system from hanging, but it also breaks the filter's functionality. The error code you see is the driver's way of saying, "I can't do my job because my queue is off."

Deleting the registry value tells FltMgr to re-enable the queue on the next boot. It's like flipping a switch back on. The driver loads fresh, and the queue is active again.

One thing to know: this isn't a permanent fix if the driver keeps crashing. If the error comes back, the driver itself is the problem. We'll get to that.

Less Common Variations

Sometimes the queue is disabled per-driver, not globally. You'll see the same error code, but the registry key is under the driver's service entry. For example, if the error comes from a third-party backup tool like Acronis or Veeam, look here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\[DriverName]\

Replace [DriverName] with the actual service name. You can find that in the error details or by running fltmc filters in an elevated command prompt. That command lists all loaded minifilters and their altitudes.

Once you find the driver, look for a value named CallbackDataQueueDisabled or QueueDisabled. Delete it and restart.

Another variation shows up in event viewer, not as a pop-up. The system logs an event with source FltMgr and event ID 5343 or similar. The message says the same thing—callback data queue disabled. The fix is identical.

If the registry key isn't there, the queue might be disabled by a policy. Check Group Policy for filter manager settings. Run gpedit.msc and look under Computer Configuration → Administrative Templates → System → Filesystem. There's no standard policy for this, but some security software adds one. If you see something like "Disable filter manager callback queues," set it to Not Configured.

Prevention: Keep the Driver Healthy

The real fix is making sure the minifilter doesn't hang in the first place. That means keeping your storage and security drivers up to date. A driver that's outdated or buggy will trigger this error again.

Here's what I do in my shop:

Update the driver that's throwing the error. Check the manufacturer's site, not just Windows Update.
Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to fix any corruption that might destabilize drivers.
If the error appears right after a Windows update, roll back the driver or the update itself. That's a common trigger.
Check if the driver supports Windows 10/11 properly. Some legacy drivers don't and cause exactly this issue.

If you're using a security product like antivirus or encryption software, make sure it's compatible with your Windows build. These products often register minifilters, and they're the usual suspects for this error.

Last tip: if the error keeps returning after you've deleted the registry key and updated the driver, consider disabling the specific minifilter temporarily. Use fltmc unload [FilterName] in an elevated command prompt. That's a test, not a permanent solution. If the error goes away, you've confirmed the driver is the culprit. Then you can decide to replace it or live without it.

That's the whole deal. You've got the fix, the reasoning, and the backup plans. Go ahead and try the registry deletion first—it takes two minutes and solves most cases.