| Previous | Next |
| STATUS_SXS_THREAD_QUERIES_DISABLED | STATUS_SXS_PROCESS_DEFAULT_ALREADY_SET |
STATUS_SXS_ASSEMBLY_MISSING
Resolve the exact missing assembly identity
Side-by-side binding uses an assembly identity that can include name, version, architecture, language, and public-key token. Installing a similarly named runtime is not sufficient if one identity field differs from the dependency recorded in the manifest.
Use the activation trace to find the requesting manifest, the complete dependent identity, and every path searched. This separates a genuinely absent assembly from an architecture mismatch, policy redirection problem, or private assembly deployed beside the wrong executable.
What to inspect
- Run sxstrace while reproducing the launch or activation failure and parse the trace.
- Compare the dependency identity with the installed assembly manifest and application architecture.
- Check embedded and external application manifests and private assembly directories.
- Repair or deploy the exact dependency instead of copying individual DLLs without their manifest.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: application manifests
- Microsoft: assembly manifests
- Microsoft: sxstrace command
Looking for a different code? Search another status or error code.