| 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.”
Looking for a different code? Search another status or error code.