| Previous | Next |
| STATUS_PLATFORM_MANIFEST_INVALID | STATUS_PLATFORM_MANIFEST_CATALOG_NOT_AUTHORIZED |
STATUS_PLATFORM_MANIFEST_FILE_NOT_AUTHORIZED
The binary is not listed by the platform allow list
The active manifest was accepted, but it contains no entry authorizing the file being checked. This differs from an ordinary Authenticode failure: a file can have a valid signature and still be disallowed when the platform policy requires an explicit manifest entry.
The mismatch often indicates that a binary was copied from another build or device, only part of an update was applied, or an OEM component was installed on unsupported hardware. Adding the file to a generic catalog does not necessarily add it to the platform manifest.
What to inspect
- Capture the file path, hash, version, signer, package, and matching CodeIntegrity event.
- Compare the binary with the component package intended for this Windows build and device.
- Check whether servicing staged a new manifest without the corresponding files, or vice versa.
- Restore the complete supported package instead of replacing only the blocked binary.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Code Integrity event log messages
- Microsoft: SignTool
- Microsoft: catalog files and digital signatures
Looking for a different code? Search another status or error code.