What does HRESULT 0x80310020 (FVE_E_OS_NOT_PROTECTED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The operating-system volume is not BitLocker protected, so the requested data-volume operation cannot proceed.

Previous	Next
FVE_E_VOLUME_BOUND_ALREADY	FVE_E_PROTECTION_DISABLED

FVE_E_OS_NOT_PROTECTED

FVE_E_OS_NOT_PROTECTED generally indicates a prerequisite problem: the operating-system drive is not protected, so a dependent data-drive feature such as automatic unlock cannot be configured safely.

What to check for FVE_E_OS_NOT_PROTECTED

Verify protection status for the Windows OS volume before managing dependent data-volume settings.
Confirm that the OS volume has suitable recovery material and a supported protector configuration.
Do not enable automatic unlock as a substitute for OS-volume protection.

manage-bde -status

Microsoft: BitLocker FAQ

Microsoft: manage-bde -status

Microsoft: manage-bde -protectors

Diagnostic interpretation of FVE_E_OS_NOT_PROTECTED

FVE_E_OS_NOT_PROTECTED has the HRESULT value 0x80310020. AllStat records the condition as “The operating system drive is not protected by BitLocker Drive Encryption.”. For FVE_E_OS_NOT_PROTECTED, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.

Evidence to capture for FVE_E_OS_NOT_PROTECTED

Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80310020 value before a wrapper converts it to an exception or Boolean result.
Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions FVE_E_OS_NOT_PROTECTED or the fve / os / protected operation.
Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original fve / os / protected condition.

Retry and recovery for FVE_E_OS_NOT_PROTECTED

Retry FVE_E_OS_NOT_PROTECTED only when the owning API documents a transient state or after the condition described as “The operating system drive is not protected by BitLocker Drive Encryption.” has changed. For FVE_E_OS_NOT_PROTECTED, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.

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