Fix STATUS_FVE_FAILED_BAD_FS (0XC0210005) File System Inconsistent

What Triggers This Error

You're booting up a Windows machine—could be a Dell laptop or a custom workstation—and instead of seeing the login screen, you get a BitLocker recovery screen with error code 0xC0210005. The message says STATUS_FVE_FAILED_BAD_FS. This almost always happens after an unclean shutdown. Last month I had a client whose power supply died mid-Windows update. Another guy force-shut his PC during a BSOD. Both got this. The system's file system got corrupted, and BitLocker refuses to decrypt the drive until it's consistent.

What's Actually Going On

BitLocker encrypts the entire volume at the block level. When the file system metadata—like the MFT or the boot sector—gets messed up, BitLocker sees the inconsistency and throws this error. It's not a hardware failure (usually), and it's not a BitLocker bug. It's Windows being careful: I won't decrypt a potentially corrupt volume because you'd lose data. The fix is to repair the file system from the recovery environment. You'll need your BitLocker recovery key—that 48-digit number you (hopefully) saved or printed when you set up encryption.

How to Fix It

Step 1: Boot into Windows Recovery Environment (WinRE)

Insert a Windows installation USB or recovery drive. If you don't have one, you can create it from another working PC using the Media Creation Tool.
Boot from the USB. On most machines, spam F12, F2, or Esc during startup to get the boot menu.
Choose your language and keyboard layout, then click Repair your computer (bottom-left corner, not Install).
Select Troubleshoot → Command Prompt.

If you can't boot from USB, some PCs let you trigger WinRE by powering on and holding the power button during startup until you see a spinning circle. Then release and let it fail three times. Fourth boot should auto-enter recovery.

Step 2: Identify the BitLocker Drive Letter

In Command Prompt, run:

diskpart
list volume
exit

Look for the volume with the BitLocker label or the one that's your Windows drive (usually around 100–500 GB). Note its drive letter—say C:. But in WinRE, drive letters can shift. Your Windows partition might be D: or E:. Check each volume's label if needed. On one job, the Windows volume was F: and the boot partition was C:. Confusing, but you'll see it.

Step 3: Run chkdsk with Repair Flags

Run this command (replace D: with your Windows drive letter):

chkdsk D: /f /r /x

/f fixes file system errors.
/r locates bad sectors and recovers readable data.
/x dismounts the volume first (required if the volume is in use).

This will take a while—20 minutes to an hour depending on drive size and damage. Don't interrupt it. Let it finish. If chkdsk reports errors, it'll fix them. If it says the file system is NTFS and clean, move on.

Step 4: Unlock and Decrypt the Drive (If Needed)

After chkdsk, you might need to unlock the drive manually. Run:

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

Replace D: and YOUR-48-DIGIT-KEY with your actual recovery key (dashes included). It'll look like 123456-789012-.... If the unlock succeeds, you can then run:

manage-bde -off D:

This disables BitLocker. But you probably don't want that—you just want to boot. Instead, after unlocking, run:

bcdboot D:\Windows /s S: /f UEFI

Where S: is the EFI system partition (usually 100 MB, FAT32). This repairs the bootloader, which often gets clobbered during file system corruption.

Step 5: Reboot and Test

Close the Command Prompt, choose Continue or Turn off your PC, then boot normally. If the error is gone, you're golden. If not, you might have hardware issues or a deeper corruption.

Still Failing? Check These

Did you get the drive letter wrong? Try chkdsk on each volume that looks like your OS drive.
Is the drive failing physically? Run wmic diskdrive get status from the Command Prompt. If it says Pred Fail, replace the drive.
Do you have the wrong recovery key? If manage-bde unlock fails, you typed the key wrong or it's from a different drive. Check your Microsoft account or printout.
Is it a TPM issue? If chkdsk found nothing and the error persists, try clearing TPM from BIOS (but you'll need the recovery key for the next boot).

Bottom line: 9 times out of 10, a good chkdsk /f /r /x from WinRE fixes this. The other 1 time, you're looking at a hardware swap or a clean reinstall. But start here—it's saved my bacon more than once.