| 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. For FVE_E_DE_PREVENTED_FOR_OS, it belongs to the automatic Device Encryption part of BitLocker rather than to generic file I/O.
For FVE_E_DE_PREVENTED_FOR_OS, note: Automatic Device Encryption has stricter end-to-end prerequisites than manual BitLocker. When diagnosing FVE_E_DE_PREVENTED_FOR_OS, remember: An Auto-DE HRESULT should be reported with the device-encryption support reason and account/escrow state. For FVE_E_DE_PREVENTED_FOR_OS, note: Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. When diagnosing FVE_E_DE_PREVENTED_FOR_OS, 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? | For FVE_E_DE_PREVENTED_FOR_OS, 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
- For
FVE_E_DE_PREVENTED_FOR_OS, record Device Encryption support reasons, policy, account state, firmware/TPM posture, WinRE state and fixed-volume inventory. ForFVE_E_DE_PREVENTED_FOR_OS, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state. - For
FVE_E_DE_PREVENTED_FOR_OS, capturemanage-bde -statusand 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
FVE_E_DE_PREVENTED_FOR_OSfailure 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. For FVE_E_DE_PREVENTED_FOR_OS, 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 FVE_E_DE_PREVENTED_FOR_OS; 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 FVE_E_DE_PREVENTED_FOR_OS
| Checkpoint | How to interpret it for FVE_E_DE_PREVENTED_FOR_OS |
|---|---|
| Before the call | Record the target identity and the pre-call automatic Device Encryption state. For FVE_E_DE_PREVENTED_FOR_OS, 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 FVE_E_DE_PREVENTED_FOR_OS 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 FVE_E_DE_PREVENTED_FOR_OS request should then advance without removing an unrelated recovery route. |
| After reboot or remount | Recheck protection, conversion and lock state for FVE_E_DE_PREVENTED_FOR_OS; a successful management call is incomplete if the next boot cannot unlock the volume. |
Verification after the change
For FVE_E_DE_PREVENTED_FOR_OS, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_DE_PREVENTED_FOR_OS 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 FVE_E_DE_PREVENTED_FOR_OS request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.
Official documentation
Reference set for FVE_E_DE_PREVENTED_FOR_OS:
- Microsoft: BitLocker overview
- Microsoft: BitLocker CSP reference
- Microsoft: GetProtectionStatus method
- Microsoft: BitLocker drive encryption for OEMs
Looking for a different code? Search another status or error code.