HRESULT 0x803100BF (FVE_E_EDRIVE_INCOMPATIBLE

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This PC's firmware is not capable of supporting hardware encryption.

Previous	Next
FVE_E_POLICY_INVALID_ENHANCED_BCD_SETTINGS	FVE_E_PROTECTOR_CHANGE_MAX_PASSPHRASE_CHANGE_ATTEMPTS_REACHED

FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE

Read this as a state-machine result

FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case platform or drive firmware does not provide the behavior required for BitLocker hardware encryption.

For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, note: Hardware-encrypted drives add firmware, storage-driver and drive-security state below the normal BitLocker volume provider. When diagnosing FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, remember: BitLocker can reject the hardware path before conversion starts, and policy may or may not permit a fallback to software encryption.

What the code does not prove

The closest misleading interpretation is an incompatible volume layout or disallowing Group Policy. For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, 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

For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, record system firmware and drive firmware versions, UEFI storage path, drive capability report, vendor advisories and dry-run result. For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, 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 FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, note: If policy permits software fallback, verify the final method explicitly. When diagnosing FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, remember: A failed hardware dry run can otherwise leave an administrator assuming protection that never started.

A low-risk recovery path

For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, apply supported firmware updates or use software encryption rather than attempting unsupported vendor security-mode changes.
After correcting the FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE condition is still active.
Before a FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE 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"

Result interpretation for FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE

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

State checks specific to FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE

Checkpoint	How to interpret it for FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE
Before the call	Record the target identity and the pre-call hardware-encrypted drive negotiation state. For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, the decisive boundary is that platform or drive firmware does not provide the behavior required for BitLocker hardware encryption.
At failure	Preserve system firmware and drive firmware versions, UEFI storage path, drive capability report, vendor advisories and dry-run result. This proves whether FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE came from BitLocker itself or from a wrapper translating another result.
After correction	Apply supported firmware updates or use software encryption rather than attempting unsupported vendor security-mode changes. The FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

For FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE 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 FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE:

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