| Previous | Next |
| FVE_E_VOLUME_EXTEND_PREVENTS_EOW_DECRYPT | FVE_E_PROTECTION_CANNOT_BE_DISABLED |
FVE_E_NOT_DE_VOLUME
The exact BitLocker condition
FVE_E_NOT_DE_VOLUME (0x803100D7) identifies the point where the requested operation is specific to automatically managed Device Encryption volumes, but this volume is not marked as one. Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. It evaluates platform eligibility, account-backed recovery escrow, all applicable fixed volumes and protection state; failure of Auto-DE does not automatically mean manual BitLocker is unavailable.
Automatic Device Encryption has stricter end-to-end prerequisites than manual BitLocker. An Auto-DE HRESULT should be reported with the device-encryption support reason and account/escrow state.
Do not confuse it with a nearby failure
Keep this separate from FVE_E_DE_VOLUME_NOT_SUPPORTED, which says the volume cannot participate rather than simply not being enrolled. That distinction determines whether the next check belongs to policy, protector inventory, volume geometry, firmware, account escrow or the calling application's buffer contract.
Evidence that distinguishes the condition
msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"Safe corrective sequence
- Use normal BitLocker management for the volume or enroll it through the supported Device Encryption provisioning workflow.
State checks specific to FVE_E_NOT_DE_VOLUME
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call automatic Device Encryption state. The requested operation is specific to automatically managed Device Encryption volumes, but this volume is not marked as one. |
| At failure | Preserve device-encryption management state, volume identity, opt-out flag, manual BitLocker configuration and calling API. |
References
Looking for a different code? Search another status or error code.