| Previous | Next |
| FVE_E_TOKEN_NOT_IMPERSONATED | FVE_E_REBOOT_REQUIRED |
FVE_E_DRY_RUN_FAILED
A failed dry run is a deployment warning
Before encryption, BitLocker can stage the protector and reboot to test the actual preboot unlock path. FVE_E_DRY_RUN_FAILED means that validation did not obtain the required key through the configured TPM or startup-key mechanism. It does not by itself mean that user data has been encrypted incorrectly.
The test exists to catch conditions that are invisible from a running Windows session: disabled or unready TPM state, incompatible PCR policy, firmware that cannot read the startup-key device, and boot configuration that changes the measurements used by the protector.
What to collect before retrying
- TPM readiness and protector details from Windows, including the PCR validation profile.
- BitLocker-API Management and System event-log entries around the test reboot.
- Firmware mode, Secure Boot state, and whether the same USB port and device are available before Windows starts.
- A verified recovery password before changing TPM, BCD, firmware, or Secure Boot settings.
References
- Microsoft: BitLocker operations guide
- Microsoft: BitLocker countermeasures
- TCG: EFI platform measurements
Looking for a different code? Search another status or error code.