0X801F0014

Fix 0x801F0014: FLT Volume Not Found Error on Windows

Hardware – Hard Drives Intermediate 👁 1 views 📅 May 29, 2026

This error hits when Windows can't find a storage volume during a filter manager operation. It's almost always caused by a corrupt volume mount point or a dead drive.

When This Error Shows Up

You're running a backup tool, a disk imaging utility, or even just opening Disk Management, and boom — error 0x801F0014. The system can't find the volume. I've seen this most often after a failed Windows update that left a drive in a weird state, or after someone yanked an external USB drive without safely ejecting it. One specific trigger: using vssadmin list shadows from an elevated command prompt and getting this instead of the expected output.

What's Really Going On

The Windows Filter Manager (fltmgr.sys) is responsible for managing file system filters — things like antivirus, backup agents, and volume shadow copy. When it can't locate a volume that's registered in its internal tables, it throws 0x801F0014. The root cause is almost always one of three things:

  • Corrupt volume mount point — the drive letter or path points to nothing valid.
  • Dead or disconnected disk — physical failure or loose cable.
  • Stale filter driver registration — leftover from an uninstalled program or a failed driver update.

Don't bother reinstalling Windows — that's overkill. The fix is usually straightforward.

Step-by-Step Fix

Step 1: Check Disk Health

Run chkdsk on the problem volume. If you don't know which volume is the culprit, run it on all drives:

chkdsk C: /f /r
chkdsk D: /f /r

If chkdsk fails with the same error, the volume is likely gone or corrupt. Move to Step 2.

Step 2: Verify Volume Exists in Disk Management

Hit Win + X and pick Disk Management. Look for any drives with no drive letter or marked as RAW. If you see one, right-click it and assign a drive letter. If the drive is RAW and has data you need, use a recovery tool like TestDisk first. If it's empty, format it.

Step 3: Clear Stale Mount Points

Sometimes a volume was removed but its mount point lingers. Open an elevated Command Prompt and run:

mountvol C: /l

This lists all mount points. Look for any that reference a GUID path to a volume that no longer shows in Disk Management. Delete it with:

mountvol C:\MountPoint /d

Replace C:\MountPoint with the actual path. Do this for every orphaned mount point.

Step 4: Re-register the Filter Manager

If steps 1-3 didn't fix it, the filter manager's internal registry might be corrupt. Run these from an elevated prompt:

fltmc load fltmgr
fltmc attach fltmgr \\.\C:

Replace C: with the problem drive letter. This forces the filter manager to re-attach to the volume.

Step 5: Reboot and Test

Restart the machine. Try whatever operation triggered the error. If it still fails, move to the next section.

Still Broken? Check These

  • Disk signature conflicts — If you cloned a drive without cleaning it, two volumes might share the same signature. Run diskpart, select the problem disk, and use uniqueid disk to assign a random ID.
  • Third-party filter drivers — Antivirus, backup agents, or encryption software can mess with fltmgr. Temporarily disable or uninstall them. If the error goes away, you've found the culprit.
  • Hardware failure — Swap the SATA cable or try the drive on a different controller. I've seen bad cables cause this error.
  • Volume Shadow Copy service stuck — Stop and restart it: net stop vss then net start vss.

If none of that works, you're likely looking at a failing drive. Back up what you can and replace it.

Was this solution helpful?