| Previous | Next |
| STATUS_FVE_BAD_METADATA_POINTER | STATUS_FVE_REBOOT_REQUIRED |
STATUS_FVE_OLD_METADATA_COPY
Meaning and context of STATUS_FVE_OLD_METADATA_COPY
BitLocker has detected that a backup metadata copy is stale. The important distinction is that this is a consistency warning between copies of BitLocker control information, not a statement that user files have been decrypted or that a supplied recovery credential is incorrect.
Preserve the current drive state and collect the time and context of the last encryption, decryption, resize, recovery, firmware, and power events. Re-running an arbitrary protector operation can make the investigation harder because it changes the metadata that needs comparison.
Before using recovery tooling, verify that the recovery material belongs to this exact volume. The repair workflow writes salvage output to a different destination, and its documentation warns that a key package can be necessary when BitLocker metadata is corrupt.
repair-bde recovery tool | BitLocker status | NTSTATUS reference
Native status interpretation
STATUS_FVE_OLD_METADATA_COPY is 0xC0210020, an NTSTATUS error value. AllStat describes it as “The backup copy of the metadata is out of date.”. The first useful question is which native API, IRP, protocol operation, or subsystem in the kernel, native API, or subsystem that returned the status produced that status.
Debugging sequence
- Preserve this result before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Correlate this result with ETW, Event Viewer, protocol traces, or a dump from the component that owns fve / old / metadata / copy; do not diagnose from translated text alone.
- For kernel I/O, keep the device stack, IRP major/minor function, request parameters, completion routine, and the first component that completed the request with this result.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “The backup copy of the metadata is out of date.”, or when its contract explicitly marks the status as transient. If the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Looking for a different code? Search another status or error code.