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.

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

Data to preserve before changing state

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.

manage-bde -status
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"

State checks specific to FVE_E_EDRIVE_INCOMPATIBLE_VOLUME

Microsoft references

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