ERROR_SXS_DUPLICATE_ASSEMBLY_NAME - 14027 (0x36CB)
Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.
Updated: Feb 21, 2026
Introduction
The ERROR_SXS_DUPLICATE_ASSEMBLY_NAME error code (14027, 0x36CB) is encountered when an application manifest references two or more components that are different versions of the same assembly. This error indicates a violation of the Windows Side-by-Side (SXS) deployment rules and can prevent the application from starting correctly.
Technical Background
The SXS subsystem in Windows manages side-by-side assemblies, which allows multiple versions of the same DLL to coexist on the system without conflicts. Each assembly is uniquely identified by its name and version. The manifest file associated with an application or component defines these dependencies and ensures that the correct version of each assembly is loaded at runtime.
Error Details
The ERROR_SXS_DUPLICATE_ASSEMBLY_NAME error occurs when a manifest specifies multiple versions of the same assembly, which violates the SXS rules. This can happen due to incorrect configuration in the manifest or issues during deployment and installation processes.
Common Causes
- Incorrect Manifest Configuration: The application manifest may incorrectly specify different versions of the same assembly.
- Deployment Issues: During the deployment process, multiple versions of the same assembly might be installed with conflicting names or version numbers.
- Corrupted Data: Corrupted manifest files can lead to incorrect references and trigger this error.
Real-World Context
This error is typically encountered when deploying applications that rely on SXS assemblies. It can also occur during development, especially in scenarios where multiple versions of the same component are being tested or deployed simultaneously.
Is This Error Critical?
The severity of this error depends on the application and its dependencies. If not resolved, it may prevent the application from starting correctly, leading to runtime failures or crashes.
How to Diagnose
To diagnose this issue, follow these steps:
- Review Manifest Files: Check the manifest files for any incorrect assembly references.
- Validate Assembly Versions: Ensure that all referenced assemblies have unique names and version numbers.
- Check Deployment Process: Verify that the deployment process is correctly managing assembly versions.
How to Resolve
To resolve this issue, take the following actions:
- Correct Manifest Configuration: Update the manifest files to ensure correct references to each assembly.
- Adjust Assembly Versions: Ensure that all assemblies have unique names and version numbers.
- Re-deploy Application: Re-deploy the application with corrected manifest files and verified assembly versions.
Developer Notes
When developing applications that rely on SXS assemblies, it is crucial to ensure that manifests are correctly configured and that deployment processes handle assembly versions appropriately.
Related Errors
ERROR_SXS_FILE_HASH_MISMATCHERROR_SXS_KEY_NOT_FOUNDFAQ
Q: What causes the
ERROR_SXS_DUPLICATE_ASSEMBLY_NAMEerror?A: The error occurs when an application manifest references multiple versions of the same assembly, violating SXS rules.
Q: How can I prevent this error from occurring?
A: Ensure that your manifest files correctly reference unique assembly names and version numbers. Verify that deployment processes handle assembly versions appropriately.
Summary
The
ERROR_SXS_DUPLICATE_ASSEMBLY_NAMEerror indicates a violation of the SXS rules in Windows, specifically when an application manifest references multiple versions of the same assembly. By carefully managing manifest configurations and ensuring correct assembly versions during deployment, developers can prevent this issue from occurring.