| Previous | Next |
| STATUS_PLATFORM_MANIFEST_FILE_NOT_AUTHORIZED | STATUS_PLATFORM_MANIFEST_BINARY_ID_NOT_FOUND |
STATUS_PLATFORM_MANIFEST_CATALOG_NOT_AUTHORIZED
The catalog is outside the platform-specific allow list
Catalog files can provide signatures for collections of binaries by storing their hashes under one signed object. This status means the catalog itself lacks authorization in the Platform Manifest. Even a correctly signed catalog cannot extend platform trust when the active manifest does not recognize it.
The cause is commonly a catalog from another OS build, device model, firmware bundle, or servicing level. Deploying the catalog into the catalog database may make it discoverable, but it does not satisfy the separate platform-manifest authorization check.
What to inspect
- Verify the catalog signature, signer, hash, package identity, and target Windows build.
- Determine which blocked files depend on this catalog and whether all came from one package.
- Inspect servicing logs for a mismatched or partially installed catalog/manifest pair.
- Install the complete authorized platform package from Windows Update or the OEM.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: catalog files and digital signatures
- Microsoft: SignTool
- Microsoft: deploy catalog files for App Control
Looking for a different code? Search another status or error code.