| Previous | Next |
| STATUS_PLATFORM_MANIFEST_NOT_ACTIVE | STATUS_APPEXEC_CONDITION_NOT_SATISFIED |
STATUS_PLATFORM_MANIFEST_NOT_SIGNED
The manifest lacks the required trusted signature
A platform manifest controls authorization of privileged or platform-specific content, so Windows requires it to be signed. This status indicates that the expected signature is absent or not present in the required form. It is distinct from STATUS_PLATFORM_MANIFEST_NOT_AUTHORIZED, where a signed or otherwise recognized manifest is rejected for this machine.
Unsigned policy material should not be enabled by weakening Code Integrity. The reliable fix is to obtain the correct manifest from signed Windows or OEM servicing media and investigate why an unsigned object replaced the original.
What to inspect
- Verify the manifest with the appropriate signature tool and record whether any signature is present.
- Check file provenance, modification time, ACLs, and the component package that installed it.
- Review servicing and endpoint-security logs for quarantine, rollback, or replacement.
- Restore the signed package and recheck Code Integrity before launching dependent components.
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.