| Previous | Next |
| STATUS_FVE_VOLUME_EXTEND_PREVENTS_EOW_DECRYPT | STATUS_FVE_PROTECTION_DISABLED |
STATUS_FVE_NOT_DE_VOLUME
Meaning and context of STATUS_FVE_NOT_DE_VOLUME
This status is about the Device Encryption management model, not a claim that the drive has no BitLocker data. The selected volume is not one Windows automatically manages as a Device Encryption volume, so a Device Encryption-specific operation is not applicable.
Identify whether the target is the operating-system volume, a fixed data volume, removable media, or a volume managed through another BitLocker workflow. Use the normal BitLocker tools to inspect its conversion, protection, lock, and protector states before deciding which management path applies.
Do not equate Device Encryption with every BitLocker deployment. Windows can use BitLocker through different volume roles and administration surfaces, and an operation designed for automatic device management can legitimately reject a manually managed volume.
BitLocker OEM guidance | BitLocker operations | BitLocker status
Native status interpretation
STATUS_FVE_NOT_DE_VOLUME is 0xC021003D, an NTSTATUS error value. AllStat describes it as “This action isn't supported because this drive isn't automatically managed with device 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 / de / 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 action isn't supported because this drive isn't automatically managed with device 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.