HRESULT 0x803100D7 (FVE_E_NOT_DE_VOLUME): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This action isn't supported because this drive isn't automatically managed with device encryption.

Previous	Next
FVE_E_VOLUME_EXTEND_PREVENTS_EOW_DECRYPT	FVE_E_PROTECTION_CANNOT_BE_DISABLED

FVE_E_NOT_DE_VOLUME

The exact BitLocker boundary

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. Note: Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. When diagnosing this result, remember: 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.

Note: Automatic Device Encryption has stricter end-to-end prerequisites than manual BitLocker. When diagnosing this result, remember: 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

record device-encryption management state, volume identity, opt-out flag, manual BitLocker configuration and calling API. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
capture manage-bde -status and the protector inventory for the exact volume GUID, not only the drive letter, because letters can change in WinRE, clusters and deployment environments.
Export BitLocker operational events for the result failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

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.
After correcting the result prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the condition is still active.
Before a this result remediation deletes protectors, changes firmware mode, resizes partitions or decrypts a production drive, verify that an independent recovery method is available and escrowed in the intended directory or account.

The boundary above identifies which BitLocker state must change before a retry can be meaningful; repeating the call without changing that state only adds noise.

State checks specific to the result

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call automatic Device Encryption state. The decisive boundary is that 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. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Use normal BitLocker management for the volume or enroll it through the supported Device Encryption provisioning workflow. The request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for it; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

Success means more than the absence of a dialog. Confirm that the condition represented by it now matches the intended design, that the protector inventory has not lost an independent recovery route, and that the next reboot or remount can unlock the volume. If the request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for it:

Looking for a different code? Search another status or error code.