| Previous | Next |
| STATUS_SYSTEM_INTEGRITY_POLICY_VIOLATION | STATUS_SYSTEM_INTEGRITY_POLICY_NOT_SIGNED |
STATUS_SYSTEM_INTEGRITY_INVALID_POLICY
The policy file itself is invalid
Before enforcement, Windows validates policy structure, identifiers, rule options, signatures when required, and relationships between base and supplemental policies. This status means the supplied policy failed that validation and therefore cannot become an active policy.
Possible causes include truncation, deployment of XML instead of compiled policy, unsupported options for the operating-system build, a mismatched supplemental policy, or corruption during transport. It should not be diagnosed as an ordinary application block.
What to inspect
- Record the policy file path, size, hash, PolicyID, BasePolicyID, and Windows build.
- Validate and compile the source policy using the supported App Control tooling for the target release.
- Check CodeIntegrity events for the exact parsing, option, or relationship failure.
- Redeploy the known-good compiled policy atomically rather than modifying the active file in place.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: App Control policy rules and options
- Microsoft: App Control event IDs
- Microsoft: App Control troubleshooting
Looking for a different code? Search another status or error code.