What does HRESULT 0x803100B2 (FVE_E_EDRIVE_INCOMPATIBLE_VOLUME) mean?

FVE_E_EDRIVE_INCOMPATIBLE_VOLUME

What BitLocker has already established

At HRESULT 0x803100B2, BitLocker has determined that the selected volume layout or drive capability cannot participate in Windows encrypted-drive hardware encryption. The FVE_E_EDRIVE_INCOMPATIBLE_VOLUME code does not by itself say that the volume master key is lost or that user data is corrupt.

Operational boundary: hardware-encrypted drive negotiation.

Note: Hardware-encrypted drives add firmware, storage-driver and drive-security state below the normal BitLocker volume provider. When diagnosing this result, remember: BitLocker can reject the hardware path before conversion starts, and policy may or may not permit a fallback to software encryption. Note: If policy permits software fallback, verify the final method explicitly. When diagnosing it, remember: A failed hardware dry run can otherwise leave an administrator assuming protection that never started.

Data to preserve before changing state

• record drive protocol/capability, volume layout, partitioning, firmware, storage driver and GetHardwareEncryptionStatus 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.

Related state to rule out

Do not merge this incident with FVE_E_KEY_LENGTH_NOT_SUPPORTED_BY_EDRIVE, where the device is otherwise considered but rejects a specific key size. If both appear with this result in one trace, preserve ordering because the first HRESULT normally identifies the prerequisite that caused later cleanup or fallback messages.

How to retest without losing evidence

Use software encryption unless the exact hardware and layout can be brought into a documented compatible configuration.

1. 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.
2. 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
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"

Diagnosis should be driven by the target object, effective policy and captured state snapshot rather than by a generic remediation applied to every BitLocker error.

State checks specific to the result

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.

Microsoft references

Reference set for it:

• Microsoft: Configure BitLocker policy
• Microsoft: Encrypted hard drives
• Microsoft: GetHardwareEncryptionStatus method
• Microsoft: BitLocker operations guide

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