What does HRESULT 0x803100D1 (FVE_E_DE_PREVENTED_FOR_OS) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Device encryption is currently blocked by this PC's configuration.

Previous	Next
FVE_E_NO_SUCH_CAPABILITY_ON_TARGET	FVE_E_DE_VOLUME_OPTED_OUT

FVE_E_DE_PREVENTED_FOR_OS

Where the operation stops

The value 0x803100D1, named FVE_E_DE_PREVENTED_FOR_OS, is returned when automatic Device Encryption is blocked by the current operating-system configuration or eligibility result. It belongs to the automatic Device Encryption part of BitLocker rather than to generic file I/O.

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

Question	What to verify
Which object failed?	The exact volume GUID, protector GUID, certificate or API target supplied by the caller.
Which state matters?	Device Encryption support reasons, policy, account state, firmware/TPM posture, WinRE state and fixed-volume inventory.
What is the nearest false lead?	manual BitLocker being administratively disabled; this code belongs to the automatic device-encryption decision.

Build a minimal diagnostic record

record Device Encryption support reasons, policy, account state, firmware/TPM posture, WinRE state and fixed-volume inventory. 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.

Change only the failed prerequisite

correct the reported eligibility blocker or deploy BitLocker explicitly under managed policy if automatic provisioning is not appropriate. Collect a fresh state snapshot and issue a single retry from the same management layer.

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

Do not delete all key protectors, clear a TPM, reformat a partition or decrypt the volume as a generic response to this result; those actions affect different trust layers and can destroy the easiest recovery route.

Use the Device Encryption support reason as the starting point

This code is the automatic-provisioning decision for the operating-system installation. System Information can report a Device Encryption Support reason such as firmware, TPM, WinRE, policy or account prerequisites. Capture that reason together with the OS volume state instead of guessing from a single hardware feature.

If the machine does not qualify for automatic enablement, an administrator can still evaluate a managed manual BitLocker deployment. Keep those two deployment models separate in compliance reports.

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 automatic Device Encryption is blocked by the current operating-system configuration or eligibility result.
At failure	Preserve Device Encryption support reasons, policy, account state, firmware/TPM posture, WinRE state and fixed-volume inventory. This proves whether this result came from BitLocker itself or from a wrapper translating another result.
After correction	Correct the reported eligibility blocker or deploy BitLocker explicitly under managed policy if automatic provisioning is not appropriate. 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 this result 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.

Official documentation

Reference set for it:

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