| Previous | Next |
| STATUS_SXS_KEY_NOT_FOUND | STATUS_SXS_WRONG_SECTION_TYPE |
STATUS_SXS_VERSION_CONFLICT
A required assembly version conflicts with one already active
STATUS_SXS_VERSION_CONFLICT means that the application requested a component version that conflicts with a version requirement already active in the current side-by-side context. The failure is about coexisting identity requirements, not merely an absent installation.
Check the full identity rather than only the version number. In a manifest, version interacts with assembly name, processor architecture, language and public-key token. Replacing a shared runtime with a different build can change the conflict into a different binding problem rather than resolve it.
What to inspect
- List the active manifest dependencies and the dependency that introduced the conflicting identity.
- Check whether a plug-in, COM server or isolation-aware wrapper activated another context before the failing call.
- Correct the manifest dependency graph or isolate the component; do not overwrite a shared side-by-side assembly to satisfy one executable.
References
Looking for a different code? Search another status or error code.