| Previous | Next |
| STATUS_FVE_DRY_RUN_FAILED | STATUS_FVE_OLD_METADATA_COPY |
STATUS_FVE_BAD_METADATA_POINTER
Meaning and context of STATUS_FVE_BAD_METADATA_POINTER
This result is about a metadata location recorded on the protected volume. It is not the same as an unavailable recovery password, a locked volume, or an NTFS path problem; the control data needed to interpret the BitLocker volume contains an invalid pointer.
Avoid disk-layout changes, repartitioning, initialization, or any utility that writes a new boot record while evidence is still needed. First capture the exact physical disk and volume mapping, retain the recovery password or key package, and determine whether the fault follows the disk or only one Windows installation.
For a severely damaged BitLocker drive, Microsoft documents repair-bde as a salvage tool that writes output elsewhere. It may need both a recovery credential and the key package associated with that particular volume; it is not a replacement for a backup.
repair-bde recovery tool | BitLocker recovery planning | NTSTATUS reference
Native status interpretation
STATUS_FVE_BAD_METADATA_POINTER is 0xC021001F, an NTSTATUS error value. AllStat describes it as “The metadata disk region pointer is incorrect.”. 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 / metadata / pointer; 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 metadata disk region pointer is incorrect.”, 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.