What does HRESULT 0x80310095 (FVE_E_REMOVAL_OF_DRA_FAILED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Removal of the data recovery agent certificate must be done using the Certificates snap-in.

Previous	Next
FVE_E_PRIVATEKEY_AUTH_FAILED	FVE_E_OPERATION_NOT_SUPPORTED_ON_VISTA_VOLUME

FVE_E_REMOVAL_OF_DRA_FAILED

Read this as a state-machine result

FVE_E_REMOVAL_OF_DRA_FAILED is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case the caller tried to remove a data recovery agent protector through an API path that does not own DRA certificate lifecycle.

Note: A BitLocker key protector wraps access to the volume master key. When diagnosing this result, remember: TPM, TPM+PIN, startup key, recovery password, password, certificate and Network Unlock protectors have different volume and policy rules; changing one is not the same as decrypting the volume.

What the code does not prove

The closest misleading interpretation is a missing DRA certificate or failed private-key authentication; the removal mechanism itself is unsupported here. Verify the returning method and state transition before assigning the incident to disk corruption, TPM failure or bad credentials.

Inspect the target, not just the message

record DRA certificate thumbprint, certificate store, protector list, Group Policy DRA configuration and the tool used for removal. 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.

Note: Protector inventory should be treated like a set of independent unlock routes. When diagnosing this result, remember: Record protector GUID and type; the presence of a recovery password does not prove that the PIN/password protector being changed exists.

A low-risk recovery path

remove or update the DRA through the Certificates snap-in and managed policy workflow, then verify remaining recovery paths.
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 -protectors -get C:\npowershell -NoProfile -Command "Get-BitLockerVolume C: | Format-List KeyProtector,ProtectionStatus,VolumeStatus"

Result Interpretation

After correction, compare the new conversion, protection and lock state with the original snapshot. A different HRESULT after this result is useful because it means the request crossed this boundary and reached the next prerequisite.

State checks specific to it

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call key-protector lifecycle state. The decisive boundary is that the caller tried to remove a data recovery agent protector through an API path that does not own DRA certificate lifecycle.
At failure	Preserve DRA certificate thumbprint, certificate store, protector list, Group Policy DRA configuration and the tool used for removal. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Remove or update the DRA through the Certificates snap-in and managed policy workflow, then verify remaining recovery paths. 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.

References

Reference set for it:

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