What does HRESULT 0x803100D0 (FVE_E_NO_SUCH_CAPABILITY_ON_TARGET) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The target of an invocation does not support requested capability.

Previous	Next
FVE_E_BUFFER_TOO_LARGE	FVE_E_DE_PREVENTED_FOR_OS

FVE_E_NO_SUCH_CAPABILITY_ON_TARGET

The exact BitLocker boundary

FVE_E_NO_SUCH_CAPABILITY_ON_TARGET (0x803100D0) identifies the point where the target object or platform does not implement the BitLocker capability requested by the management invocation. Note: Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. When diagnosing this result, remember: It evaluates platform eligibility, account-backed recovery escrow, all applicable fixed volumes and protection state; failure of Auto-DE does not automatically mean manual BitLocker is unavailable.

Note: “Encrypted” and “protected” are not synonyms. When diagnosing this result, remember: Compliance normally requires active protectors and recoverable escrow, not merely a completed sector conversion.

Do not confuse it with a nearby failure

Keep this separate from an operation blocked by policy despite being supported; capability discovery itself fails here. That distinction determines whether the next check belongs to policy, protector inventory, volume geometry, firmware, account escrow or the calling application's buffer contract.

Evidence that distinguishes the condition

record target type and version, method/capability identifier, OS SKU, provider version and capability-query result. 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.

msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"

Safe corrective sequence

feature-detect before invocation and choose a supported alternative rather than retrying the same method.
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.

The boundary above identifies which BitLocker state must change before a retry can be meaningful; repeating the call without changing that state only adds noise.

State checks specific to the result

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call automatic Device Encryption state. The decisive boundary is that the target object or platform does not implement the BitLocker capability requested by the management invocation.
At failure	Preserve target type and version, method/capability identifier, OS SKU, provider version and capability-query result. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Feature-detect before invocation and choose a supported alternative rather than retrying the same method. 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.