What does HRESULT 0x803100AF (FVE_E_EDRIVE_NO_FAILOVER_TO_SW) mean?

FVE_E_EDRIVE_NO_FAILOVER_TO_SW

The exact BitLocker condition

FVE_E_EDRIVE_NO_FAILOVER_TO_SW (0x803100AF) identifies the point where hardware-encryption setup failed and policy forbids falling back to BitLocker software encryption. 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.

Do not confuse it with a nearby failure

Keep this separate from FVE_E_EDRIVE_DISALLOWED_BY_GP, where hardware encryption itself is prohibited rather than required without fallback. 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 hardware-encryption policy, fallback setting, drive readiness, firmware/driver versions and dry-run failure.

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

State checks specific to FVE_E_EDRIVE_NO_FAILOVER_TO_SW

References

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