What does HRESULT 0x80310084 (FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON) mean?

 
Previous Next
FVE_E_POLICY_CONFLICT_FDV_RK_OFF_AUK_ON FVE_E_NON_BITLOCKER_OID

FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON

FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON BitLocker detected conflicting policy for a removable data drive: automatic unlock is enabled while the required user recovery option is disabled. The policy set is internally inconsistent.

What to check for FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON

  • Review removable-drive recovery settings and automatic-unlock settings as one configuration set.
  • Either allow the required recovery option or remove the automatic-unlock requirement.
  • Verify the effective policy after management refresh before retrying BitLocker setup.
gpresult /h "%TEMP%\bitlocker-gpo.html"

Microsoft: Configure BitLocker policy settings

Microsoft: manage-bde

Microsoft: manage-bde -protectors

Diagnostic interpretation of FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON

FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON has the HRESULT value 0x80310084. AllStat records the condition as “BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. For FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON, bitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.”. For FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON, 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_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80310084 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_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON or the fve / policy / conflict / rdv / rk operation.
  • For FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.

Retry and recovery for FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON

Retry FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON only when the owning API documents a transient state or after the condition described as “BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. For FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON, bitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.” has changed. For FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON, 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.