| Previous | Next |
| STATUS_SXS_COMPONENT_STORE_CORRUPT | STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT |
STATUS_SXS_FILE_HASH_MISMATCH
A declared assembly file fails manifest hash verification
STATUS_SXS_FILE_HASH_MISMATCH means that a file associated with an assembly did not match the verification information recorded in its assembly manifest. The failure is about the bytes of a declared member file, not just its presence or filename.
It differs from STATUS_SXS_FILE_HASH_MISSING, where the manifest lacks the verification information required by the operation. A mismatch can result from an incomplete deployment, a modified binary, a partial restore or a manifest copied from a different build; it does not by itself identify the cause.
What to inspect
- Identify the exact assembly member and compare its hash with the manifest value from a trusted package.
- Check package, backup and deployment logs for a mismatched manifest/binary pair or an interrupted update.
- Restore the complete signed package as a unit rather than replacing only the file or only the manifest.
References
- Microsoft: application manifests
- Microsoft: assembly manifests
- Wine: activation-context implementation
Looking for a different code? Search another status or error code.