HRESULT 0x803100D3 (FVE_E_DE_VOLUME_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Device encryption isn't available for this drive.

Previous	Next
FVE_E_DE_VOLUME_OPTED_OUT	FVE_E_EOW_NOT_SUPPORTED_IN_VERSION

FVE_E_DE_VOLUME_NOT_SUPPORTED

What BitLocker has already established

At HRESULT 0x803100D3, BitLocker has determined that the selected volume type or layout is outside the set supported by automatic Device Encryption. The FVE_E_DE_VOLUME_NOT_SUPPORTED code does not by itself say that the volume master key is lost or that user data is corrupt.

Operational boundary: automatic Device Encryption.

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 it, remember: An Auto-DE HRESULT should be reported with the device-encryption support reason and account/escrow state.

Data to preserve before changing state

record volume role, bus/media type, filesystem, partition attributes, fixed/removable classification and device-encryption policy scope. 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.

Related state to rule out

Do not merge this incident with manual BitLocker support, which may still exist for the same volume under administrator control. If both appear with this result in one trace, preserve ordering because the first HRESULT normally identifies the prerequisite that caused later cleanup or fallback messages.

How to retest without losing evidence

Manage the volume with an appropriate manual BitLocker policy or redesign the storage layout instead of forcing Auto-DE.

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.

msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"

Diagnosis should be driven by the target object, effective policy and captured state snapshot rather than by a generic remediation applied to every BitLocker error.

Volume eligibility is the failing axis

This result is tied to the selected volume rather than the computer-wide hardware posture. Record whether the target is fixed or removable, its partition role, filesystem, bus type and any hidden or recovery attributes. Other volumes on the same computer can qualify for automatic Device Encryption while this one remains outside the supported set.

Do not clear or replace the TPM to address this code. Decide whether the volume should be manually managed with BitLocker, excluded by design, or recreated with a supported storage role.

State checks specific to it

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 selected volume type or layout is outside the set supported by automatic Device Encryption.
At failure	Preserve volume role, bus/media type, filesystem, partition attributes, fixed/removable classification and device-encryption policy scope. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Manage the volume with an appropriate manual BitLocker policy or redesign the storage layout instead of forcing Auto-DE. 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.

Microsoft references

Reference set for it:

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