| Previous | Next |
| FVE_E_DE_PROTECTION_SUSPENDED | FVE_E_DE_DEVICE_LOCKEDOUT |
FVE_E_DE_OS_VOLUME_NOT_PROTECTED
The failed prerequisite
FVE_E_DE_OS_VOLUME_NOT_PROTECTED / 0x803100C9 marks a rejected BitLocker transition: automatic Device Encryption cannot claim a protected device because the operating-system volume is not currently protected.
Note: Evaluate every fixed volume and the OS trust anchor together. When diagnosing this result, remember: Automatic unlock and device-wide compliance can fail because a secondary volume is outside policy.
Diagnostic map
| Layer | automatic Device Encryption |
|---|---|
| Proof to collect | OS volume encryption and protection status, protectors, recovery escrow, conversion state and device-encryption policy result |
| Different condition | an unencrypted secondary data volume; the OS volume is the trust anchor for automatic unlock and device posture |
| First safe change | establish supported OS-volume protection and verified recovery escrow before addressing dependent fixed volumes |
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.
A focused verification sequence
- record OS volume encryption and protection status, protectors, recovery escrow, conversion state and device-encryption policy result. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
- capture
manage-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 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.
Recommended operational response
- establish supported OS-volume protection and verified recovery escrow before addressing dependent fixed volumes.
- 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"Interpretation checkpoint
This result identifies a condition but not every owner of the surrounding state. Preserve the original caller, volume GUID and event sequence so the correction is applied at the right layer.
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 automatic Device Encryption cannot claim a protected device because the operating-system volume is not currently protected. |
| At failure | Preserve OS volume encryption and protection status, protectors, recovery escrow, conversion state and device-encryption policy result. This proves whether it came from BitLocker itself or from a wrapper translating another result. |
| After correction | Establish supported OS-volume protection and verified recovery escrow before addressing dependent fixed volumes. 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.
Official references
Reference set for it:
- 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.