HRESULT 0x80310031 (FVE_E_PROTECTOR_EXISTS): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The requested BitLocker key protector type already exists on the volume.

Previous	Next
FVE_E_BOOTABLE_CDDVD	FVE_E_RELATIVE_PATH

FVE_E_PROTECTOR_EXISTS

FVE_E_PROTECTOR_EXISTS means that BitLocker rejected adding a duplicate protector of a type that is limited to one instance for the selected volume.

How to investigate for FVE_E_PROTECTOR_EXISTS

List the existing protectors and compare the requested type with the current configuration.
Use the existing protector where appropriate instead of adding a duplicate.
When replacement is required, verify the new recovery path before removing an old protector.

Microsoft: manage-bde

Diagnostic interpretation of FVE_E_PROTECTOR_EXISTS

FVE_E_PROTECTOR_EXISTS has the HRESULT value 0x80310031. AllStat records the condition as “This key protector cannot be added. Only one key protector of this type is allowed for this drive.”. For FVE_E_PROTECTOR_EXISTS, 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_PROTECTOR_EXISTS

Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80310031 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_PROTECTOR_EXISTS or the fve / protector / exists operation.
Reproduce FVE_E_PROTECTOR_EXISTS with the smallest valid input and note whether the result changes with identity, architecture, service state, or target object.

Retry and recovery for FVE_E_PROTECTOR_EXISTS

Retry FVE_E_PROTECTOR_EXISTS only when the owning API documents a transient state or after the condition described as “This key protector cannot be added. Only one key protector of this type is allowed for this drive.” has changed. For FVE_E_PROTECTOR_EXISTS, 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.