| Previous | Next |
| STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT | STATUS_SXS_ASSEMBLY_IS_NOT_A_DEPLOYMENT |
STATUS_SXS_IDENTITIES_DIFFERENT
The expected and actual assembly identities differ
STATUS_SXS_IDENTITIES_DIFFERENT means that two identities being compared are not the same. A dependency reference must exactly match the corresponding defining assembly identity where the manifest rules require it; a near match in assembly name is not enough.
Compare every identity field, including architecture, language, version and public-key token. This differs from STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT: that status finds equal identities with conflicting content, while this one finds different identities before content equivalence is assumed.
What to inspect
- Collect both complete identities from the dependency reference and the resolved assembly manifest.
- Check architecture and language before replacing runtimes; x86 and amd64 assemblies can share a familiar product name but are not interchangeable.
- Correct the manifest reference or deploy the exact assembly it names instead of changing only a displayed DLL filename.
References
- Microsoft: application manifests
- Microsoft: assembly manifests
- Wine: activation-context implementation
Looking for a different code? Search another status or error code.