Site icon EfmSoft

What does HRESULT 0x803100C9 (FVE_E_DE_OS_VOLUME_NOT_PROTECTED) mean?

 
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.

Evaluate every fixed volume and the OS trust anchor together. Automatic unlock and device-wide compliance can fail because a secondary volume is outside policy.

Diagnostic map

Layerautomatic Device Encryption
Proof to collectOS volume encryption and protection status, protectors, recovery escrow, conversion state and device-encryption policy result
Different conditionan unencrypted secondary data volume; the OS volume is the trust anchor for automatic unlock and device posture
First safe changeestablish supported OS-volume protection and verified recovery escrow before addressing dependent fixed volumes

A focused verification sequence

  • Record OS volume encryption and protection status, protectors, recovery escrow, conversion state and device-encryption policy result.
msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"

State checks specific to FVE_E_DE_OS_VOLUME_NOT_PROTECTED

StageHow to interpret it
Before the callRecord the target identity and the pre-call automatic Device Encryption state. Automatic Device Encryption cannot claim a protected device because the operating-system volume is not currently protected.
At failurePreserve OS volume encryption and protection status, protectors, recovery escrow, conversion state and device-encryption policy result.
After correctionEstablish supported OS-volume protection and verified recovery escrow before addressing dependent fixed volumes.

Official references


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

Exit mobile version