| Previous | Next |
| FVE_E_NO_AUTOUNLOCK_MASTER_KEY | FVE_E_HIDDEN_VOLUME |
FVE_E_MOR_FAILED
This failure is in the firmware security handoff
FVE_E_MOR_FAILED concerns the Memory Overwrite Request mechanism, not encryption of sectors on disk. The operating system uses a UEFI variable to tell platform firmware that secrets may remain in memory and that RAM must be cleared during reset. If firmware cannot create, update, or honor that state, BitLocker reports this failure.
The TCG reset-attack mitigation specification defines the variable across reboot boundaries. Modern systems may also implement a lock variable so an untrusted software component cannot clear the request after it has been asserted.
What to investigate
- Check for firmware updates and platform diagnostics related to UEFI variable services.
- Record VBS and HVCI state because MOR lock behavior differs on systems using virtualization-based security.
- Distinguish a failed request from proof that memory was not cleared; the platform firmware is the component that performs the wipe.
- Avoid repeatedly clearing TPM or BitLocker protectors, which does not repair UEFI variable handling.
References
- Microsoft: MOR lock version 2
- TCG: Platform Reset Attack Mitigation Specification
- UEFI: variable and boot services specification
Looking for a different code? Search another status or error code.