| Previous | Next |
| STATUS_FVE_LOCKED_VOLUME | STATUS_FVE_BAD_INFORMATION |
STATUS_FVE_NOT_ENCRYPTED
Meaning and context of STATUS_FVE_NOT_ENCRYPTED
This is an operation-to-volume mismatch: the caller requested a BitLocker-specific action for a volume that is not in the encrypted state that the action requires. It is not the same as a locked BitLocker volume, because a locked volume is encrypted and awaits an unlock protector.
Check the mount point, volume role, conversion state, and encryption method before changing any protectors. manage-bde -status or Get-BitLockerVolume should be used to confirm the target rather than relying on a drive letter that may have changed after attaching media or entering Windows Recovery Environment.
A repair or unlock operation intended for a protected data drive will not become valid simply by supplying a recovery password to an unencrypted target. First establish whether the correct volume was selected and whether BitLocker was ever enabled on it.
BitLocker overview | BitLocker operations guide | manage-bde reference
Native status interpretation
STATUS_FVE_NOT_ENCRYPTED is 0xC0210001, an NTSTATUS error value. AllStat describes it as “The volume is not encrypted, no key is available.”. 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 / encrypted, 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 volume is not encrypted, no key is available.”, 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.