| Previous | Next |
| STATUS_PLATFORM_MANIFEST_CATALOG_NOT_AUTHORIZED | STATUS_PLATFORM_MANIFEST_NOT_ACTIVE |
STATUS_PLATFORM_MANIFEST_BINARY_ID_NOT_FOUND
The binary cannot be matched to a manifest entry
Platform authorization can depend on an identifier embedded in the file’s signed metadata rather than only on its path or hash. This status means Windows could not find the Binary ID needed to associate the file with an entry in the active manifest. The file may still contain an ordinary Authenticode signature, but not the identity expected by this policy.
The usual explanation is a binary built or signed outside the required platform pipeline, a stripped or modified signature, or a component from a different release. Re-signing it with an unrelated certificate does not create the required platform identity.
What to inspect
- Use SignTool and PE inspection tools to record all embedded signatures and signed attributes.
- Compare the file with the vendor-supplied binary for the same build and device.
- Check whether packaging, optimization, or security software modified the signed image.
- Replace the file through the original signed component package.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: SignTool
- Microsoft: Code Integrity event log messages
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.