| Previous | Next |
| STATUS_FVE_WIPE_CANCEL_NOT_APPLICABLE | STATUS_FVE_SECUREBOOT_DISABLED |
STATUS_FVE_EDRIVE_DRY_RUN_FAILED
Meaning and context of STATUS_FVE_EDRIVE_DRY_RUN_FAILED
This is the encrypted-hard-drive variant of a BitLocker preflight failure. It points to the deployment requirements of the drive and platform rather than proving that user data or a normal software-encryption key is corrupt.
Check the physical drive type, controller mode, initialization state, firmware settings, and whether the platform meets the documented encrypted-hard-drive requirements. For example, supported startup-drive configurations depend on UEFI behavior, and the documented deployment requirements distinguish encrypted hard drives from generic self-encrypting drives.
Do not simply force the drive into a different encryption mode in production. First retain recovery material, capture the current encryption method and drive status, then correct the deployment preconditions or choose the supported BitLocker configuration.
Encrypted hard drives | BitLocker status | BitLocker operations
Native status interpretation for STATUS_FVE_EDRIVE_DRY_RUN_FAILED
STATUS_FVE_EDRIVE_DRY_RUN_FAILED is 0xC0210038, an NTSTATUS error value. AllStat describes it as “Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.”. For STATUS_FVE_EDRIVE_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_EDRIVE_DRY_RUN_FAILED
- Preserve STATUS_FVE_EDRIVE_DRY_RUN_FAILED before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Correlate STATUS_FVE_EDRIVE_DRY_RUN_FAILED with ETW, Event Viewer, protocol traces, or a dump from the component that owns fve / edrive / 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_EDRIVE_DRY_RUN_FAILED.
Recovery considerations for STATUS_FVE_EDRIVE_DRY_RUN_FAILED
A retry is appropriate only after the owner of STATUS_FVE_EDRIVE_DRY_RUN_FAILED has changed the state described by “Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.”, or when its contract explicitly marks the status as transient. For STATUS_FVE_EDRIVE_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.