FVE_E_BAD_DATA (0X80310016) Fix: Malformed BitLocker Data

You're stuck with BitLocker's 'bad data' error. Let's get you back in.

That 0X80310016 error — FVE_E_BAD_DATA — shows up when you're trying to unlock a BitLocker drive, and Windows says the encryption data is malformed. It's a nuisance because it looks like your drive's toast, but it's usually fixable. Here's the exact routine I've used on dozens of help desk calls.

The Real Fix: Clean Up BitLocker's Metadata

Skip the fancy tools. Skip the third-party recovery software. The fix is a built-in command that scrubs the corrupted metadata and lets you start fresh without losing your data — as long as you have your recovery key or password.

1. Open an elevated Command Prompt. Click Start, type cmd, right-click Command Prompt, and pick 'Run as administrator.'
2. Check your drive's current state. Type manage-bde -status C: (replace C: with your actual drive letter). You'll see something like 'Protection On' or 'Protection Off' and a warning about bad data. This confirms the error is real and not a fluke.
3. Unlock the drive with your recovery key. Run manage-bde -unlock C: -RecoveryPassword . If you don't have the key, stop here — you'll need it from your Microsoft account or AD. After this command, you should see 'The drive was successfully unlocked.'
4. Turn off BitLocker temporarily. Run manage-bde -off C:. This decrypts the drive. It can take a while depending on size — think 30 minutes to a few hours. You'll know it's done when manage-bde -status C: shows 'Decryption' at 100%.
5. Re-enable BitLocker. Once decrypted, run manage-bde -on C:. This creates fresh, clean encryption metadata. After it completes, the original error won't come back.

Expected outcome after step 3: The error message disappears, and you can access the drive normally. Steps 4 and 5 are preventative — they wipe the corrupted data entirely.

Why This Works

FVE_E_BAD_DATA means the encryption metadata — the little chunk of data that holds keys and volume info — got scrambled. It's usually from a partial TPM update, a bad shutdown during BitLocker activity, or a disk sector error. By decrypting and re-encrypting, you're writing fresh metadata from scratch. The old corrupted stuff gets overwritten. You don't need to nuke the drive or reformat, which is the biggest win.

I've also seen this error on USB drives where the flash controller flaked out mid-write. Same fix works there, just swap the drive letter.

Less Common Variations

Sometimes the error appears when enabling BitLocker, not just unlocking. For example, you try to turn on BitLocker on a new drive and get 0X80310016. That's rarer, but it happens with drives that have leftover GPT partitions or previous encryption remnants.

Fix for that variation:

• Open Disk Management (diskmgmt.msc).
• Delete all partitions on the drive. Yes, all of them. This wipes old metadata completely.
• Create a new Simple Volume, format it as NTFS.
• Run manage-bde -on X: again. It should work now because there's no old junk interfering.

Another rare one: the error during resume from sleep. A wonky TPM driver sends a bad command, BitLocker flips out. This is a driver issue, not a data issue. The fix is to update your TPM firmware from your motherboard maker's site, or disable TPM-based key protection and use a password instead.

Prevention Tips

You don't want to deal with this again. Here's how to keep it from coming back:

• Don't force-shut down. If you see 'Configuring BitLocker' on boot, let it finish. Power loss during that phase corrupts metadata fast.
• Update TPM firmware before enabling BitLocker. Go to your PC or motherboard manufacturer's support page and grab the latest TPM update. Old firmware has known bugs that produce malformed data.
• Back up your recovery key. Save it to your Microsoft account and also print a copy. Without it, step 3 in the fix above fails entirely.
• Run chkdsk quarterly. Bad sectors can corrupt metadata. A simple chkdsk C: /f keeps the drive healthy.

That's it. No voodoo, no third-party tools. Just a clean decryption, re-encryption, and a few smart habits. You're back in business.