| Previous | Next |
| MSSIPOTF_E_FILE_CHECKSUM | MSSIPOTF_E_FAILED_HINTS_CHECK |
MSSIPOTF_E_FAILED_POLICY
The signature does not meet the selected policy
MSSIPOTF_E_FAILED_POLICY is not the same as a malformed DSIG table or a broken cryptographic primitive. The public Windows description says that the signature lacks the attributes required by the policy. That makes the validation context important: the same signed data can be structurally readable yet unacceptable for a particular policy decision.
Start by keeping the exact verifier, policy, and input bytes together. A later conversion, optimization, or table rewrite changes the signed content and can cause an apparently unrelated policy outcome. Verify structure and checksum first, then inspect the signature and policy evidence exposed by the validation tool.
How to investigate
- Capture the selected policy and the full accompanying diagnostic, not only this HRESULT.
- Verify that the font binary is byte-identical to the artifact that was signed.
- Do not copy signature metadata from another font; rebuild the font and create a new signature for the final binary when policy requires one.
References
Looking for a different code? Search another status or error code.