What does HRESULT 0x803100D5 (FVE_E_ADBACKUP_NOT_ENABLED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator.

Previous	Next
FVE_E_EOW_NOT_SUPPORTED_IN_VERSION	FVE_E_VOLUME_EXTEND_PREVENTS_EOW_DECRYPT

FVE_E_ADBACKUP_NOT_ENABLED

The failed prerequisite

FVE_E_ADBACKUP_NOT_ENABLED / 0x803100D5 marks a rejected BitLocker transition: effective policy prevents recovery information for this drive type from being backed up to Active Directory Domain Services.

Note: A managed restriction is part of the security design. When diagnosing this result, remember: Record which authority delivered it and whether the requested operation is mandatory for compliance or merely a convenience feature.

Diagnostic map

Layer	policy and authorization
Proof to collect	drive type, effective recovery-backup policy, domain join, escrow target, policy source and attempted backup method
Different condition	an AD connectivity, schema or permission failure after backup is allowed
First safe change	enable the correct AD DS backup policy centrally or use another approved escrow destination before depending on the protector

Note: BitLocker evaluates the target volume together with effective Group Policy or MDM policy, Windows edition, caller authorization and the requested protector or management method. When diagnosing this result, remember: A policy HRESULT therefore describes a rejected configuration decision, not evidence that encrypted sectors are damaged.

A focused verification sequence

record drive type, effective recovery-backup policy, domain join, escrow target, policy source and attempted backup method. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
capture manage-bde -status and 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

enable the correct AD DS backup policy centrally or use another approved escrow destination before depending on the protector.
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.

manage-bde -status
gpresult /h bitlocker-policy.html

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 policy and authorization state. The decisive boundary is that effective policy prevents recovery information for this drive type from being backed up to Active Directory Domain Services.
At failure	Preserve drive type, effective recovery-backup policy, domain join, escrow target, policy source and attempted backup method. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Enable the correct AD DS backup policy centrally or use another approved escrow destination before depending on the protector. 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:

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