| Previous | Next |
| STATUS_FVE_DEBUGGER_ENABLED | STATUS_FVE_BAD_METADATA_POINTER |
STATUS_FVE_DRY_RUN_FAILED
Meaning and context of STATUS_FVE_DRY_RUN_FAILED
This is a failure of the dry-run or preflight path: BitLocker could not obtain the encryption key required to continue. It is therefore more specific than a later conversion error and does not by itself prove that volume encryption has started or that encrypted sectors were damaged.
Collect the target volume role, configured protector types, current conversion state, and the local BitLocker event data. For an operating-system volume, also record TPM, boot, and policy changes that occurred before the attempt. Do not delete a working recovery protector while isolating the preflight failure.
Use the supported management interface to compare what the policy requires with what the volume actually has. The Win32_EncryptableVolume provider exposes the volume and protector state; manage-bde -status is the quick command-line view.
Win32_EncryptableVolume | BitLocker status | BitLocker configuration
Native status interpretation for STATUS_FVE_DRY_RUN_FAILED
STATUS_FVE_DRY_RUN_FAILED is 0xC021001E, an NTSTATUS error value. AllStat describes it as “The BitLocker encryption key could not be obtained.”. For STATUS_FVE_DRY_RUN_FAILED, the first useful question is which native API, IRP, protocol operation, or subsystem in the kernel, native API, or subsystem that returned the status produced that status.
Debugging sequence for STATUS_FVE_DRY_RUN_FAILED
- Preserve STATUS_FVE_DRY_RUN_FAILED before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Correlate STATUS_FVE_DRY_RUN_FAILED with ETW, Event Viewer, protocol traces, or a dump from the component that owns fve / dry / run; do not diagnose from translated text alone.
- For kernel I/O, keep the device stack, IRP major/minor function, request parameters, completion routine, and the first component that completed the request with STATUS_FVE_DRY_RUN_FAILED.
Recovery considerations for STATUS_FVE_DRY_RUN_FAILED
A retry is appropriate only after the owner of STATUS_FVE_DRY_RUN_FAILED has changed the state described by “The BitLocker encryption key could not be obtained.”, or when its contract explicitly marks the status as transient. For STATUS_FVE_DRY_RUN_FAILED, if the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Looking for a different code? Search another status or error code.