| Previous | Next |
| FVE_E_DE_HARDWARE_NOT_COMPLIANT | FVE_E_DE_PROTECTION_SUSPENDED |
FVE_E_DE_WINRE_NOT_CONFIGURED
Device encryption depends on a recoverable boot path
FVE_E_DE_WINRE_NOT_CONFIGURED applies to automatic device-encryption provisioning. Windows Recovery Environment must be registered and reachable so recovery and reset workflows can unlock the operating-system volume when normal startup protection cannot.
The presence of a recovery partition is not enough. Its image path, BCD registration, enabled state, and relationship to the current Windows installation must all be valid. Imaging, partition cloning, and manual partition changes commonly leave stale WinRE configuration.
What to inspect
- Use
reagentc /infoto verify status, location, and the target Windows installation. - Confirm that
winre.wimexists at the registered path and that the partition is accessible before the OS drive is unlocked. - Check BCD and recovery-partition changes made by deployment or servicing tools.
- After repairing WinRE, re-evaluate device-encryption readiness instead of manually forcing encryption around the failed prerequisite.
References
- Microsoft: REAgentC command-line options
- Microsoft: BitLocker recovery overview
- Microsoft: BitLocker planning guide
Looking for a different code? Search another status or error code.
