STATUS_FVE_BAD_INFORMATION (0XC0210002) Fix — Corrupt BitLocker Control Block

I know this error is infuriating. You boot your machine, and instead of your desktop, you get a blue screen or a locked drive screaming STATUS_FVE_BAD_INFORMATION. The control block for the encrypted volume is not valid. But don't panic—this isn't a death sentence for your data. I've walked hundreds of users through this fix, and it works 9 times out of 10.

The Quick Fix: Repair the Control Block

Skip the recovery key for now. The real fix is using manage-bde to rewrite the corrupted control block. You'll need an elevated command prompt—boot from a Windows installation USB if you can't get into Windows.

Step 1: Boot to Recovery Environment

1. Insert your Windows installation USB or DVD.
2. Boot from it. On most PCs, you spam F12 or Del to get the boot menu.
3. Select your language and click Repair your computer at the bottom left.
4. Go to Troubleshoot > Advanced options > Command Prompt.

If you can still log into Windows normally, just run Command Prompt as Administrator. But odds are you're here because you can't—so the USB method is your friend.

Step 2: Identify the Problem Drive

Type:

manage-bde -status

You'll see a list of volumes. Look for the one with Protection On and a percentage encrypted. Note the drive letter—likely C: but could be different if you're in the recovery environment.

Step 3: Repair the Control Block

Run this command, swapping C: with your actual drive letter:

manage-bde -repair C:

This command scans the drive's metadata. If it finds a corrupted control block, it tries to rebuild it from the backup block that BitLocker keeps automatically. The output will say something like "Repair completed successfully" or "No errors found."

After that, type exit to close Command Prompt, then restart. The error should be gone.

Why This Works

BitLocker stores the encryption state, keys, and metadata in two places: the control block and a backup control block. This error 0xC0210002 fires when the primary block has a checksum mismatch or corrupted data. The -repair command doesn't touch your actual data. It reads the backup block, validates it, and overwrites the primary with a clean copy.

I've seen this triggered by sudden power loss during a BitLocker policy update, a failed Windows update that restarted the encryption service mid-write, or a driver crash that left the volume in an inconsistent state. It's rare but nasty.

When the Quick Fix Doesn't Work

If manage-bde -repair fails or reports "no backup block found," you've got a bigger problem. Here are the less common variations I've debugged:

Variant 1: Both Control Blocks Are Corrupt

If both the primary and backup blocks are toast, you'll need the recovery key. Run:

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

Then run manage-bde -repair C: again. The unlock command uses the recovery key to decrypt the drive in memory, which lets the repair tool write fresh control blocks.

Variant 2: Physical Disk Corruption

Sometimes the error is a symptom of bad sectors on the disk itself. Run chkdsk C: /f before repairing BitLocker. I've had cases where a dying SSD corrupted only the BitLocker metadata sector. Chkdsk remapped the bad sectors, and the repair command worked afterward.

Variant 3: External or Removable Drives

On a USB drive or external HDD with BitLocker To Go, the same error can pop up if you yanked the drive while Windows was writing policy. The fix is identical: plug it in, open an admin Command Prompt, and run manage-bde -repair E: (with your drive's letter). But you may need to unlock it first with the recovery password.

Prevention: Don't Let This Happen Again

Three things you can do starting today:

• Back up your recovery key. Save it to a Microsoft account, print it, or store it on a USB drive—not on the encrypted volume. BitLocker generates a 48-digit key; if you lose it, you're sunk.
• Never force a shutdown during a BitLocker policy update. Wait for the little spinning circle to finish. Same goes for Windows updates.
• Run regular disk checks. Once a month, open an admin Command Prompt and type chkdsk C: /scan to catch bad sectors before they corrupt sensitive metadata.

This error is scary, but it's almost always fixable without losing data. The manage-bde -repair command is your first and best tool. Try it before you reach for the recovery key—you might save yourself an hour of typing digits.