0XC01C0005

Fix 0XC01C0005: Invalid Name Request in Windows

EP
Erropedia Team
📅 May 26, 2026 📅 Updated Aug 1, 2026 👁 9 views Windows Errors Intermediate
This error hits when a filter manager name request goes wrong, often after a driver update or app install. Here's how to kill it fast.

What Triggers This Error

You'll see 0XC01C0005 when Windows' filter manager—part of the file system—gets a name request it can't handle. This usually happens after installing or updating third-party software that hooks into file operations: antivirus tools, backup apps, or encryption drivers. I've seen it most often with McAfee Enterprise and certain Dell backup utilities on Windows 10 22H2 and Windows 11 23H2. The error pops up in Event Viewer under System logs or as a crash dialog. It's a pain, but fixable.

Quick Fix (30 Seconds): Roll Back Problematic Drivers

If this error just started, the fastest fix is to undo whatever caused it. Think back: did you install or update any software with file system hooks recently? Antivirus, backup agents, or disk encryption tools are the usual suspects.

  1. Press Win + R, type devmgmt.msc, hit Enter.
  2. Expand Storage controllers and System devices. Look for entries labeled with the vendor of the offending software (e.g., McAfee Minifilter, Dell Backup Agent).
  3. Right-click that device, choose Properties > Driver > Roll Back Driver. If the button's grayed out, skip to the next step.
  4. If rollback isn't an option, uninstall the driver entirely. Restart immediately.

That's it. If the error goes away, you know the driver was the culprit. Don't reinstall the same version—check the vendor's site for a newer one or a known fix.

Moderate Fix (5 Minutes): Wipe the Filter Driver from Registry

If the quick fix didn't work or you can't identify the driver, the filter manager stores a list of registered minifilters in the registry. Removing the bad one manually does the trick. Warning: back up your registry first—export the key you're about to edit.

  1. Press Win + R, type regedit, hit Enter.
  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FltMgr\Instances
  3. You'll see subkeys named after minifilter instances. Each has a Name value. Look for anything that matches the software you suspect (e.g., McAfeeMon, DellFlt).
  4. Right-click that subkey, choose Delete. Confirm.
  5. Restart your system.

This removes the filter from the manager's load list. If you're wrong about the guilty party, no harm—the filter just won't load until you reinstall the app. You can check Event Viewer afterward to see if the error stops.

Advanced Fix (15+ Minutes): Unhook the Filter from Boot Sequence

When the error happens during boot or you can't boot into Windows normally, you need to break the filter chain before it loads. This requires booting into Safe Mode or using Windows Recovery Environment (WinRE).

  1. Boot into Safe Mode with Networking: Restart your PC, press F8 or Shift + F8 during boot (Windows 10/11 sometimes requires recovery media). Alternatively, force the startup repair by interrupting the boot three times—hold the power button during the Windows logo to trigger automatic repair. Once in the recovery menu, go to Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 for Safe Mode.
  2. In Safe Mode, open an elevated Command Prompt (right-click Start > Terminal (Admin)).
  3. Run: fltmc instances. This lists all loaded minifilters. Look for the Altitude and Instance of the offending one.
  4. Unload it with: fltmc unload <instancename> (replace with the actual instance name from the list).
  5. To prevent it from reloading on next boot, you'll need to disable its associated service. Open Services.msc, find the filter's service (e.g., McAfee File Filter), set Startup type to Disabled.
  6. Reboot normally.

If you can't even reach Safe Mode, boot from a Windows installation USB, open Command Prompt (Shift + F10), and use bcdedit /set safeboot minimal to force Safe Mode on next boot. After fixing, run bcdedit /deletevalue safeboot to revert.

When to Call in the Vendor

If none of this works, the filter driver itself is buggy. Uninstall the entire application that introduced it—not just the driver. Then test. If the error vanishes, contact that vendor's support with the exact error code and a screenshot of the Event Viewer entry. Don't let them dodge—this error is their software's fault, not Windows'.

Prevention

Keep a system restore point before installing any software that hooks into file systems. When you see a prompt like "Install a file system filter driver" during setup, that's a red flag. Research the vendor's track record with that driver before clicking yes. It'll save you a headache later.

Related Errors in Windows Errors
0X000000CD Fix ERROR_NO_SIGNAL_SENT (0X000000CD) in Windows 10/11 0XC00000E2 Fix STATUS_OPLOCK_NOT_GRANTED (0XC00000E2) on Windows 0XC00D100A NS_E_WMP_INVALID_MIN_VAL (0XC00D100A) fix for slider errors 0XC0000242 STATUS_BAD_COMPRESSION_BUFFER (0xC0000242) Fix: Ill-Formed Data
0XC01C0005 STATUS_FLT_INVALID_NAME_REQUEST Windows filter manager error invalid name request fix 0xc01c0005 Windows 11 0xc01c0005 Windows 10 filter manager error code filter driver error Windows error 0xc01c0005 fix 0xc01c0005 filter manager registry fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.