| Previous | Next |
| STATUS_SXS_FILE_HASH_MISMATCH | STATUS_SXS_IDENTITIES_DIFFERENT |
STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT
One assembly identity maps to different manifest contents
STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT reports an identity collision: manifests claim the same side-by-side identity but their content differs. An identity is intended to identify one assembly definition, so using it for two differing dependency graphs or file lists makes binding ambiguous.
This is not an ordinary version conflict. A version conflict compares different required versions; this status says the supposed same identity is not stable. Treat it as a packaging or store-consistency problem and preserve both manifest copies for comparison.
What to inspect
- Compare the full raw manifests, including dependency,
file, hash and COM metadata, not only the assemblyIdentity element. - Trace which installer, update or private deployment introduced each copy of the identity.
- Assign a distinct, valid identity to a genuinely different assembly build rather than overwriting the existing one.
References
- Microsoft: application manifests
- Microsoft: assembly manifests
- Wine: activation-context implementation
Looking for a different code? Search another status or error code.