ERROR_SXS_XML_E_MISSINGSEMICOLON - 14039 (0x36D7)
Manifest Parse Error : A semi colon character was expected.
Updated: Feb 21, 2026
Technical Background
The ERROR_SXS_XML_E_MISSINGSEMICOLON error code (14039, 0x36D7) is a specific error that occurs during the parsing of XML manifests in the Windows Side-by-Side (SXS) assembly cache. This error indicates that a semicolon character was expected but not found, which can disrupt the proper execution or loading of assemblies.
Error Details
The SXS subsystem uses manifest files to describe and manage side-by-side assemblies. These manifests are XML documents that contain metadata about assemblies, such as their versioning information, dependencies, and other attributes. During the assembly loading process, these manifests are parsed by the SXS engine to ensure that all necessary components are correctly loaded.
Common Causes
The error ERROR_SXS_XML_E_MISSINGSEMICOLON is typically caused by an invalid or malformed XML manifest file. Specifically, it indicates that a semicolon character was expected but not found in the XML document. This could be due to:
- Incorrectly formatted XML syntax.
- Missing or incorrectly placed semicolons in the manifest file.
- Corrupted manifest files.
Real-World Context
This error can occur when attempting to load a .NET assembly, install a Windows application, or update system components that rely on SXS assemblies. It is particularly relevant for developers working with managed code and XML-based configuration files.
Is This Error Critical?
The severity of this error depends on the context in which it occurs. If an application relies on a specific assembly that cannot be loaded due to this error, the application may fail to start or function correctly. However, the system itself is unlikely to be critically affected unless multiple critical assemblies are involved.
How to Diagnose
To diagnose and resolve ERROR_SXS_XML_E_MISSINGSEMICOLON, follow these steps:
- Review Operation Context: Ensure that the operation context is correct and that the manifest file being processed is intended for use in SXS assembly loading.
- Validate Parameters: Verify that all parameters passed to the SXS engine are valid and correctly formatted, particularly focusing on XML syntax.
- Confirm Object Types: Confirm that the object types (manifest files) being processed are of the correct type and format.
- Verify Input Data: Check the manifest file for any visible or hidden characters that might be causing issues, such as missing semicolons.
- Check Limits or Constraints: Ensure that there are no system limits or constraints that could affect the parsing of XML manifests.
How to Resolve
To resolve ERROR_SXS_XML_E_MISSINGSEMICOLON, take the following actions:
- Correct any syntax errors in the manifest file, ensuring all required semicolons are present and correctly placed.
- Use tools like an XML validator to check for and fix any issues with the manifest files.
- If the issue persists, consider restoring or re-downloading the affected assembly or application package.
Developer Notes
Developers should ensure that their XML manifests adhere to strict syntax rules, particularly regarding semicolons. This error can be avoided by using well-formed XML and validating all input data before it is processed by the SXS engine.
Related Errors
ERROR_SXS_XML_E_BADXMLFORMAT(14038): A more general XML parse error.ERROR_SXS_XML_E_UNEXPECTEDTOKEN(14042): An unexpected token was encountered in the manifest file.
FAQ
Q: What does the ERROR_SXS_XML_E_MISSINGSEMICOLON error mean?
A: This error indicates that a semicolon character was expected but not found during the parsing of an XML manifest file used by the SXS assembly cache.
Q: How can I prevent this error from occurring?
A: Ensure that all XML manifests are well-formed and adhere to strict syntax rules, particularly regarding semicolons. Use XML validation tools to check for and fix any issues before processing them with the SXS engine.
Summary
The ERROR_SXS_XML_E_MISSINGSEMICOLON error (14039) is a specific manifest parse error that occurs when an expected semicolon character is missing in an XML manifest file. This can disrupt the loading of assemblies and applications relying on the SXS assembly cache. By understanding its context, causes, and resolution steps, developers can effectively diagnose and resolve this issue.