| Previous | Next |
| FVE_E_SECUREBOOT_CONFIGURATION_INVALID | FVE_E_SHADOW_COPY_PRESENT |
FVE_E_EDRIVE_DRY_RUN_FAILED
Where the operation stops
The value 0x803100BC, named FVE_E_EDRIVE_DRY_RUN_FAILED, is returned when the preflight test for hardware-based encryption failed before BitLocker committed the drive to eDrive mode. It belongs to the hardware-encrypted drive negotiation part of BitLocker rather than to generic file I/O.
Hardware encryption is not inferred from the SSD marketing name. Verify the encryption method reported by BitLocker and the drive capability returned through the storage and volume-encryption providers. 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.
| Question | What to verify |
|---|---|
| Which object failed? | The exact volume GUID, protector GUID, certificate or API target supplied by the caller. |
| Which state matters? | dry-run diagnostics, drive model and firmware, storage driver, UEFI mode, policy, security protocol status and event logs. |
| What is the nearest false lead? | a later runtime failure after hardware encryption is already active. |
Build a minimal diagnostic record
- Record dry-run diagnostics, drive model and firmware, storage driver, UEFI mode, policy, security protocol status and event logs.
Change only the failed prerequisite
update supported firmware/drivers or select software encryption; verify final encryption method instead of assuming fallback occurred.
manage-bde -status
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"State checks specific to FVE_E_EDRIVE_DRY_RUN_FAILED
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call hardware-encrypted drive negotiation state. The preflight test for hardware-based encryption failed before BitLocker committed the drive to eDrive mode. |
| At failure | Preserve dry-run diagnostics, drive model and firmware, storage driver, UEFI mode, policy, security protocol status and event logs. This proves whether this result came from BitLocker itself or from a wrapper translating another result. |
| After correction | Update supported firmware/drivers or select software encryption; verify final encryption method instead of assuming fallback occurred. |
Official documentation
Looking for a different code? Search another status or error code.