| Previous | Next |
| STATUS_FVE_NO_AUTOUNLOCK_MASTER_KEY | STATUS_FVE_NO_FEATURE_LICENSE |
STATUS_FVE_MOR_FAILED
Meaning and context of STATUS_FVE_MOR_FAILED
This is a platform-firmware result, not an ordinary volume-encryption error. BitLocker requested a memory-clearing action for restart, but firmware did not enable it. Changing a recovery password or re-running a file-system check does not address that firmware boundary.
Record the device model, firmware version, Secure Boot state, recent firmware configuration changes, and the exact BitLocker operation. Test on a supported maintenance path after confirming the vendor’s firmware guidance; do not weaken BitLocker configuration merely to hide the status.
The UEFI ecosystem defines the boot variables and interfaces used by platform firmware, while BitLocker relies on the boot environment for offline protection. This makes a firmware update or vendor-specific remediation a more relevant lead than a generic disk repair.
UEFI Boot Manager | BitLocker OEM guidance | NTSTATUS reference
Native status interpretation
STATUS_FVE_MOR_FAILED is 0xC0210025, an NTSTATUS error value. AllStat describes it as “The system firmware failed to enable clearing of system memory on reboot.”. 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
- Preserve this result before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Compare the exact fve / mor operation on a working system and record differences in object lifetime, access token, device state, negotiated protocol, and policy.
- 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 this result.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “The system firmware failed to enable clearing of system memory on reboot.”, or when its contract explicitly marks the status as transient. 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.