| Previous | Next |
| WEP_E_NO_LICENSE | WEP_E_UNEXPECTED_FAIL |
WEP_E_OS_NOT_PROTECTED
WEP_E_OS_NOT_PROTECTED identifies this condition: the non-Microsoft provider does not report the Windows operating-system drive as actively protected.
Where the failure sits
Windows Encryption Provider integration has separate gates for provider licensing, hardware readiness, volume support, provisioning, active protection, device-lock configuration, and EAS compliance. WEPHOSTSVC events should therefore be read alongside the third-party provider’s own inventory and logs, not as a replacement for them.
Other fixed volumes being protected cannot compensate for an unprotected OS volume when device encryption is required.
Facts to collect first
- OS volume identity, provider protection state, encryption progress, and key protectors
- Boot mode, recovery environment, and preboot authentication state
- Provider/WEPHOSTSVC events and EAS RequireEncryption result
- Whether protection is pending, suspended, failed, or never provisioned
Change one variable at a time
- Query provider status after a full reboot rather than only during conversion.
- Compare a protected data volume with the OS volume.
- Complete encryption on a lab system and test recovery boot.
Verification after correction
Repair the failed contract rather than the surrounding system: Provision and activate OS-volume protection with validated recovery access, then allow conversion and required reboots to finish.
Close the incident only when the OS drive reports active protection after cold boot, recovery media works, and compliance detects deliberate suspension.
Technical references
Looking for a different code? Search another status or error code.