Knowledge

ERROR_SXS_XML_E_UNCLOSEDSTRING - 14062 (0x36EE)

Manifest Parse Error : A string literal was not closed.

Updated: Feb 21, 2026

Technical Background

The error code ERROR_SXS_XML_E_UNCLOSEDSTRING (14062, 0x36EE) is encountered during the parsing of XML manifests in the Windows Side-by-Side (SXS) assembly cache. This error indicates that a string literal within an XML manifest was not properly closed, leading to a parse failure.

Error Details

The ERROR_SXS_XML_E_UNCLOSEDSTRING error occurs when the XML parser encounters an unclosed string during the validation or processing of an XML manifest file. This can happen in various scenarios where XML manifests are used, such as during application deployment, assembly resolution, or runtime configuration.

Common Causes

  • Invalid parameter values: Incorrectly formatted strings within the XML manifest that do not adhere to the expected syntax rules.
  • Incorrect object type: The manifest file is being processed by an incorrect parser or handler that does not recognize the string format as part of its intended processing flow.
  • Exceeding limits: Although unlikely, it's possible that the length of a string could exceed system-defined limits for XML parsing.

Real-World Context

This error typically manifests when attempting to deploy or run an application that relies on SXS assemblies and their associated manifest files. The presence of this error can prevent the correct loading or execution of the application, leading to runtime failures.

Is This Error Critical?

The criticality of this error depends on the context in which it occurs. If the application is unable to load due to an unclosed string, it will fail at startup or during the first attempt to use a resource that requires manifest validation. However, if the application can continue running without the problematic manifest, the impact may be minimal.

How to Diagnose

To diagnose this error, follow these steps:

  1. Review operation context: Ensure that the XML manifest is being processed in the correct environment and by the appropriate parser.
  2. Validate parameters: Check all string literals within the manifest for proper formatting and ensure they are correctly closed.
  3. Confirm object types: Verify that the manifest file is intended to be parsed as an XML document and not misinterpreted by a different type of handler.

How to Resolve

To resolve this error, take the following actions:

  1. Correct parameter usage: Ensure all string literals in the manifest are properly formatted with correct opening and closing characters.
  2. Adjust operation context: If the manifest is being processed incorrectly, ensure that it is passed through the appropriate XML parser or handler.
  3. Restore data: If the manifest file has been corrupted, restore a clean copy from a backup or source control.

Developer Notes

When working with SXS manifests, always validate string literals to ensure they are correctly formatted and closed. This can be done programmatically by running the XML through a validation tool before deployment or execution.

Related Errors

  • ERROR_SXS_XML_E_MISSINGASSEMBLY (14063): Indicates missing assembly references in the manifest.
  • ERROR_SXS_XML_E_MALFORMED: General error indicating malformed XML content, which could include unclosed strings but may also be due to other issues.

FAQ

Q: Can this error occur during development?

A: Yes, it can occur if developers are manually editing SXS manifests and do not properly close string literals. Developers should ensure that all string literals in their manifests are correctly formatted.

Q: Is this error specific to certain versions of Windows?

A: This error is applicable across different versions of Windows where the SXS assembly cache and XML manifest processing are used, but its occurrence may vary based on the specific application or deployment scenario.

Summary

The ERROR_SXS_XML_E_UNCLOSEDSTRING (14062) error indicates a parse failure due to an unclosed string literal in an XML manifest. This can occur during various operations involving SXS assemblies and manifests, leading to potential runtime failures. By ensuring proper validation of strings within the manifest and using appropriate parsers, developers can mitigate this issue.