| Previous | Next |
| STATUS_ACCESS_DISABLED_BY_POLICY_PATH | STATUS_ACCESS_DISABLED_BY_POLICY_OTHER |
STATUS_ACCESS_DISABLED_BY_POLICY_PUBLISHER
The executable signer did not satisfy the publisher policy
Publisher rules evaluate the Authenticode signing identity and can include certificate subject, issuing authority, product, file name, and version constraints. A valid digital signature is not automatically an authorization; it must match the rule and remain acceptable under certificate policy.
Preserve the signed file before re-signing or rebuilding it. Inspect the full certificate chain, timestamp, product metadata, and rule version bounds. Broadly trusting an entire publisher to unblock one binary can authorize more software than intended.
What to inspect
- Verify Authenticode signature, timestamp, chain, and file version.
- Identify which publisher-rule field failed to match.
- Narrow any exception to the necessary product, file, and version range.
References
- Microsoft: Software Restriction Policies
- Microsoft: SaferIdentifyLevel
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.