| Previous | Next |
| ERROR_PLATFORM_MANIFEST_INVALID | ERROR_PLATFORM_MANIFEST_CATALOG_NOT_AUTHORIZED |
ERROR_PLATFORM_MANIFEST_FILE_NOT_AUTHORIZED
The file is not authorized on this platform because an entry was not found in the Platform Manifest.
ERROR_PLATFORM_MANIFEST_FILE_NOT_AUTHORIZED is Win32 error 4572 (0x11DC) and belongs to Platform Manifest authorization.
Likely causes
- a particular file has no authorizing entry in the active Platform Manifest.
- the active platform identity disagrees with file path, hash, binary identity, manifest entries, and signature.
- the provisioning pipeline did not use the authorized file version or update the manifest through trusted servicing.
Troubleshooting steps
- Record file path, hash, binary identity, manifest entries, and signature.
- Record device identity and the active Platform Manifest generation.
What to verify
Verify whether a particular file has no authorizing entry in the active Platform Manifest. Check file path, hash, binary identity, manifest entries, and signature, the device identity, and the active Platform Manifest generation.
Handling, retry, and recovery
Use the authorized file version or update the manifest through trusted servicing. Preserve the artifact and authorization evidence before changing provisioning state.
Practical example
A board-support binary changes without a matching manifest entry and is rejected during platform validation.
Developer and administrator guidance
Identify the exact file hash, Binary ID, package version, and manifest file entry. Do not authorize an entire catalog merely to admit one unexpected binary. Replace the file with its approved build or publish a trusted manifest revision that names that file deliberately.
References
- Microsoft: System Error Codes (4000–5999) — reference for error 4572.
- Microsoft: How System Guard protects Windows — reference for error 4572.
- Microsoft: Windows security hardware — reference for error 4572.
Looking for a different code? Search another status or error code.
