STATUS_FVE_OLD_METADATA_COPY (0XC0210020) – Backup Metadata Outdated

The 30-Second Fix: Check the Drive Status

Before you panic, run this quick check. Open an admin Command Prompt (Win+X, then “Command Prompt (Admin)”) and type:

manage-bde -status

Look for the drive that’s showing a protection status like “Unknown” or “Fully Decrypted”. If it’s not fully encrypted, you might just have a stale metadata copy from a failed resize — I saw this last week on a client’s Lenovo laptop after they shrunk a partition with Disk Management.

If the drive is fully encrypted and still throwing the error, move on to the next fix. This is rare — 90% of the time, the drive is in a weird partial state.

The 5-Minute Moderate Fix: Clear and Recreate the Metadata Backup

This fix directly addresses the stale backup copy. It’s non-destructive — we’re not removing the encryption, just refreshing the metadata.

1. Open an admin Command Prompt (again).
2. Type this for the affected drive (replace C: with your actual drive letter):

manage-bde -lock C: -ForceDismount

Wait 30 seconds, then unlock it:

manage-bde -unlock C: -RecoveryPassword

You’ll need your 48-character BitLocker recovery key — check Microsoft account, AD, or printed copy. If you don’t have it, you’re stuck in recovery mode (skip to the advanced fix below).

After unlocking, run:

manage-bde -protectors -enable C:

Then check the status again:

manage-bde -status

If the error disappears, you’re golden. If not, the metadata might be truly corrupt — try the advanced fix.

The 15+ Minute Advanced Fix: Full Metadata Repair

This is the nuclear option. You’re going to backup the critical data, then rebuild the BitLocker metadata from scratch. I’ve used this on a Dell PowerEdge server that BSOD’d after a failed Windows update and refused to boot correctly.

Step 1: Backup Everything

Boot from a Windows installation USB or a live Linux USB (I prefer Hiren’s Boot CD PE because it includes BitLocker tools). Copy the entire encrypted drive contents to an external drive — don’t risk losing data if the repair goes south.

Step 2: Suspend and Remove BitLocker

From the Windows recovery environment (Shift+F10 during boot), run:

manage-bde -off C:

This decrypts the drive completely. It takes time — an hour for a 256GB SSD. Once done, verify with:

manage-bde -status

You should see “Protection Off” and “Decryption Complete”.

Step 3: Re-encrypt from a Clean State

Enable BitLocker fresh:

manage-bde -on C:

This creates new metadata from scratch. The old backup copy is gone. After encryption completes (again, might take a while), run:

manage-bde -status

The error should be gone. I’d also run chkdsk C: /f before re-encrypting if you suspect disk corruption — a client had bad sectors mimicking this error.

When to Give Up and Use Recovery Console

If none of these work, you’re looking at a corrupted BitLocker volume. Boot from a Windows install USB, go to “Repair your computer” > “Troubleshoot” > “Advanced Options” > “Command Prompt”, and run:

repair-bde C: -rp 000000-000000-000000-000000-000000-000000-000000-000000

Replace the zeros with your 48-character recovery password (no hyphens in the actual command). This forces a raw decryption — it’s slow, but it’s your last shot before a full format-and-restore.

Pro tip: Always store your recovery key somewhere you can access without the drive — I keep mine in a password manager with a printed backup in my safe. This error is a harsh reminder that BitLocker metadata can break silently.