FVE_E_FAILED_BAD_FS (0X80310014) on BitLocker: File System Corrupt

1. The Most Common Cause: Dirty Volume from a Bad Shutdown

I know this error is infuriating — you just want to unlock your drive, and Windows tells you the file system is inconsistent. I've seen this dozens of times on laptops that lost power during an update or after a forced shutdown. The fix is straightforward.

BitLocker checks the NTFS file system before it lets you access the drive. If Windows thinks the volume is "dirty" (meaning it has pending repairs from a crash or improper shutdown), it blocks BitLocker and throws 0x80310014.

The real fix: Run a file system repair from an elevated command prompt. This clears the dirty flag.

Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin)). Then run:

chkdsk /f D:

Replace D: with the actual drive letter of your BitLocker drive. If it's the system drive (usually C:), you'll get a prompt to schedule a check at next reboot. Say yes by typing Y and rebooting.

After chkdsk finishes, run this to force BitLocker to re-evaluate the drive:

manage-bde -status D:

You should now see the drive as "Unlocked" and the file system as "Healthy". If that doesn't work, try the next cause.

2. The Second Cause: Corrupted Volume Metadata (More Stubborn)

Sometimes chkdsk alone isn't enough. I've had cases where the NTFS metadata got slightly corrupted — not enough to cause data loss, but enough to confuse BitLocker. This is common after an interrupted disk check or a failed disk repair tool.

The fix: Use PowerShell to repair the volume directly.

Open PowerShell as Administrator (right-click Start > Windows PowerShell (Admin)). Then run:

Repair-Volume -DriveLetter D -OfflineScanAndFix

Again, replace D with your drive letter. The -OfflineScanAndFix flag is important — it takes the volume offline temporarily, scans it, and fixes what it can. This usually clears the dirty flag that chkdsk missed.

If you get an error saying the volume can't be taken offline, close all programs using that drive, or restart in Safe Mode and try again.

Once that's done, check BitLocker status again:

manage-bde -status D:

If it still shows the error, move to the third cause.

3. The Third Cause: Corrupt File System on a BitLocker-Encrypted Drive (Rare but Nasty)

This tripped me up the first time too — you repair the file system and the dirty flag is gone, but BitLocker still won't unlock. What's happening is the NTFS file system itself has deeper corruption that a simple chkdsk can't fix. This can happen if you used third-party disk tools (like a Linux USB) that wrote something weird to the partition.

The fix: Use the BitLocker recovery key to unlock the drive, then run a full chkdsk /r (which scans bad sectors and recovers readable data).

First, get your recovery key. If you don't have it saved, check your Microsoft account at https://account.microsoft.com/devices/recoverykey — it's tied to the device where you enabled BitLocker.

Once you have the 48-digit recovery key, open an admin command prompt and unlock the drive:

manage-bde -unlock D: -RecoveryPassword YOUR-48-DIGIT-KEY

Replace the key with yours (no hyphens). If it says "The volume cannot be unlocked", double-check the key — it's case-insensitive but the groups matter.

After unlock, run a deep scan:

chkdsk /r D:

This takes a while (could be hours on a large drive), but it finds and marks bad sectors. Once it's done, restart and try the Repair-Volume command again. This combination usually fixes the most stubborn cases.

Quick-Reference Summary Table

That's it. I know this error feels scary because it blocks access to your encrypted data, but the file system fix is almost always enough. If none of these work, the drive hardware might be failing — back up what you can and consider replacing the drive.

One last thing: always have your BitLocker recovery key saved somewhere safe (like printed out or in your Microsoft account). It's the only way into your data if something goes wrong with the file system.