| Previous | Next |
| FVE_E_DE_PREVENTED_FOR_OS | FVE_E_DE_VOLUME_NOT_SUPPORTED |
FVE_E_DE_VOLUME_OPTED_OUT
Read this as a state-machine result
FVE_E_DE_VOLUME_OPTED_OUT is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case the specific volume carries an opt-out from automatic Device Encryption management.
For FVE_E_DE_VOLUME_OPTED_OUT, note: Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. When diagnosing FVE_E_DE_VOLUME_OPTED_OUT, 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.
What the code does not prove
The closest misleading interpretation is an unsupported volume that could never participate; opt-out is an explicit state or policy decision. For FVE_E_DE_VOLUME_OPTED_OUT, verify the returning method and state transition before assigning the incident to disk corruption, TPM failure or bad credentials.
Inspect the target, not just the message
- For
FVE_E_DE_VOLUME_OPTED_OUT, record volume opt-out flag, provisioning history, management policy, volume identity and any OEM/deployment customization. ForFVE_E_DE_VOLUME_OPTED_OUT, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state. - For
FVE_E_DE_VOLUME_OPTED_OUT, 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_VOLUME_OPTED_OUTfailure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.
For FVE_E_DE_VOLUME_OPTED_OUT, note: Automatic Device Encryption has stricter end-to-end prerequisites than manual BitLocker. When diagnosing FVE_E_DE_VOLUME_OPTED_OUT, remember: An Auto-DE HRESULT should be reported with the device-encryption support reason and account/escrow state.
A low-risk recovery path
- For
FVE_E_DE_VOLUME_OPTED_OUT, remove the opt-out only through the supported management workflow after confirming the volume should be automatically managed. - After correcting the
FVE_E_DE_VOLUME_OPTED_OUTprerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that theFVE_E_DE_VOLUME_OPTED_OUTcondition is still active. - Before a
FVE_E_DE_VOLUME_OPTED_OUTremediation 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"
Result interpretation for FVE_E_DE_VOLUME_OPTED_OUT
After correction, compare the new conversion, protection and lock state with the original snapshot. A different HRESULT after FVE_E_DE_VOLUME_OPTED_OUT is useful because it means the request crossed this boundary and reached the next prerequisite.
State checks specific to FVE_E_DE_VOLUME_OPTED_OUT
| Checkpoint | How to interpret it for FVE_E_DE_VOLUME_OPTED_OUT |
|---|---|
| Before the call | Record the target identity and the pre-call automatic Device Encryption state. For FVE_E_DE_VOLUME_OPTED_OUT, the decisive boundary is that the specific volume carries an opt-out from automatic Device Encryption management. |
| At failure | Preserve volume opt-out flag, provisioning history, management policy, volume identity and any OEM/deployment customization. This proves whether FVE_E_DE_VOLUME_OPTED_OUT came from BitLocker itself or from a wrapper translating another result. |
| After correction | Remove the opt-out only through the supported management workflow after confirming the volume should be automatically managed. The FVE_E_DE_VOLUME_OPTED_OUT request should then advance without removing an unrelated recovery route. |
| After reboot or remount | Recheck protection, conversion and lock state for FVE_E_DE_VOLUME_OPTED_OUT; a successful management call is incomplete if the next boot cannot unlock the volume. |
Verification after the change
For FVE_E_DE_VOLUME_OPTED_OUT, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_DE_VOLUME_OPTED_OUT 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_VOLUME_OPTED_OUT request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.
References
Reference set for FVE_E_DE_VOLUME_OPTED_OUT:
- Microsoft: BitLocker CSP reference
- Microsoft: GetProtectionStatus method
- Microsoft: BitLocker drive encryption for OEMs
- Microsoft: BitLocker overview
Looking for a different code? Search another status or error code.
