| Previous | Next |
| EAS_E_POLICY_COMPLIANT_WITH_ACTIONS | EAS_E_CURRENT_USER_HAS_BLANK_PASSWORD |
EAS_E_REQUESTED_POLICY_NOT_ENFORCEABLE
EAS_E_REQUESTED_POLICY_NOT_ENFORCEABLE identifies this condition: the requested EAS setting is stricter than Windows or the relevant account/provider can enforce.
What the status narrows down
EAS compliance is a policy merge, not a single password test. Windows evaluates the requested settings against local accounts, connected accounts, domain or management policy, and operating-system capabilities; the individual fields in EasComplianceResults show which requirement changed the decision.
User action cannot make an inherently unsupported policy enforceable on that platform/account type.
Evidence worth preserving
- Requested value and corresponding Windows/local/account capability
- Account types on the device and which are evaluated locally
- Conflicting Group Policy/MDM/EAS sources and the strictest merged result
- Per-policy compliance result, not only the aggregate HRESULT
A controlled diagnostic sequence
- Lower the test policy to the documented supported boundary.
- Evaluate local, domain, and Microsoft accounts separately.
- Compare CheckCompliance without applying changes.
Correction and proof
The corrective action should be narrow: Adjust the server policy to a supported value or use a management authority that can enforce the requirement.
Close the incident only when policy design tests cover every supported account type and reject configurations that Windows would only appear to enforce.
Technical references
Looking for a different code? Search another status or error code.