| Previous | Next |
| STATUS_GRAPHICS_SESSION_TYPE_CHANGE_IN_PROGRESS | STATUS_FVE_NOT_ENCRYPTED |
STATUS_FVE_LOCKED_VOLUME
Meaning and context of STATUS_FVE_LOCKED_VOLUME
BitLocker recognizes this as an encrypted volume, but Windows does not currently hold a usable volume master key for normal file-system access. It is therefore different from a damaged file system and also different from a recovery credential that was already tried and rejected.
Check the exact target volume and its recovery-key identifier before supplying a recovery password or recovery key. manage-bde -status and Get-BitLockerVolume distinguish a locked protected volume from one that is merely not encrypted. Do not format, initialize, or remove protectors to make the status disappear; none of those actions unlock existing encrypted data.
When an expected TPM or automatic-unlock protector no longer releases the key, use the configured recovery path and then investigate the changed boot, firmware, or management state. STATUS_FVE_FAILED_AUTHENTICATION is the nearby code for a recovery authentication attempt that failed; this code does not itself say that a supplied credential was invalid.
BitLocker overview | BitLocker recovery overview | manage-bde reference
Native status interpretation
STATUS_FVE_LOCKED_VOLUME is 0xC0210000, an NTSTATUS error value. AllStat describes it as “This volume is locked by BitLocker Drive Encryption.”. 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 / locked / volume, 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 “This volume is locked by BitLocker Drive Encryption.”, 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.