| Previous | Next |
| STATUS_FVE_NOT_ENCRYPTED | STATUS_FVE_TOO_SMALL |
STATUS_FVE_BAD_INFORMATION
Meaning and context of STATUS_FVE_BAD_INFORMATION
The failure concerns BitLocker’s per-volume control information, not the syntax of a management request. It therefore differs from STATUS_FVE_BAD_DATA, which points to malformed data supplied to the control engine by a caller.
Preserve the volume, its recovery information, and the exact status before attempting any intrusive operation. Repeatedly changing protectors, repartitioning, or initializing the disk does not reconstruct valid encrypted-volume control state and can remove evidence needed for a supported recovery process.
Collect the BitLocker status, the event-log context, the volume identity, and the operation that produced the error. Then decide whether the issue is limited to management metadata or whether a recovery procedure is required; a wrong recovery password is diagnosed separately as an authentication failure.
Microsoft NTSTATUS reference | BitLocker recovery overview | BitLocker operations guide
Native status interpretation
STATUS_FVE_BAD_INFORMATION is 0xC0210002, an NTSTATUS error value. AllStat describes it as “The control block for the encrypted volume is not valid.”. 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.
- Log the operation associated with fve / information, the object or handle type, process and thread identity, and the state transition immediately before the return.
- 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 control block for the encrypted volume is not valid.”, 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.