Knowledge

ERROR_SXS_XML_E_UNCLOSEDSTARTTAG - 14060 (0x36EC)

Manifest Parse Error : Element was not closed.

Updated: Feb 21, 2026

Technical Background

The ERROR_SXS_XML_E_UNCLOSEDSTARTTAG error is a specific error code indicating that an XML manifest file contains an unclosed start tag. This error typically occurs during the parsing of XML content, which is often used in Windows for various configuration and deployment purposes.

Error Details

  • Error Name: ERROR_SXS_XML_E_UNCLOSEDSTARTTAG
  • Numeric Code: 14060 (0x36EC)
  • Short Description: Manifest parse error indicating an unclosed start tag in XML content.

Common Causes

The common cause of this error is the presence of an unclosed start tag within the XML manifest file. This can occur due to various reasons, such as:

  • Incorrectly formatted XML content.
  • Missing closing tags for elements.
  • Syntax errors in the XML structure.

Real-World Context

This error typically manifests when attempting to parse or validate an XML manifest file that contains structural issues. Such files are often used in scenarios involving side-by-side assembly (SxS) deployment, configuration settings, and other XML-based configurations within Windows environments.

Is This Error Critical?

The criticality of this error depends on the context in which it occurs. While it may not directly impact system stability or performance, it can prevent certain operations from completing successfully if the XML manifest is required for those operations.

How to Diagnose

To diagnose this issue, follow these steps:

  1. Review Operation Context: Ensure that the operation requiring the XML manifest file is being executed in an appropriate context where such files are expected and necessary.
  2. Validate Parameters: Verify that all parameters passed to functions or APIs related to XML parsing include valid and well-formed XML content.
  3. Confirm Object Types: Confirm that the object types involved (e.g., XML files, manifest files) are correctly identified and handled by the system.
  4. Verify Input Data: Inspect the XML content for any syntax errors, such as unclosed tags, to identify the root cause of the error.

How to Resolve

To resolve this issue, take the following actions:

  1. Correct Parameter Usage: Ensure that all parameters passed to functions or APIs related to XML parsing are correctly formatted and do not contain structural issues like unclosed start tags.
  2. Adjust Operation Context: If the operation is part of a larger process, ensure that the context in which it operates supports the necessary XML files.
  3. Restore Data: If possible, restore any corrupted or incorrectly formatted XML content to its correct state.
  4. Retry Operation with Valid Inputs: Attempt to re-run the operation using valid and correctly formatted input data.

Developer Notes

Developers should ensure that all XML-based configurations are well-formed and validated before use in Windows environments. This can be achieved through automated validation tools or by manually inspecting the XML content for any structural issues.

Related Errors

  • ERROR_SXS_XML_E_UNCLOSEDENDTAG: Similar error indicating an unclosed end tag in XML content.
  • ERROR_SXS_XML_E_BADXMLDECL: Error related to invalid XML declarations within manifest files.

FAQ

Q: What does the ERROR_SXS_XML_E_UNCLOSEDSTARTTAG error mean?

A: This error indicates that an XML manifest file contains an unclosed start tag, preventing proper parsing and execution of associated operations.

Q: How can I prevent this error from occurring?

A: Ensure all XML content is well-formed and validated before use. Use tools or manual inspection to check for any structural issues like unclosed tags.

Q: Can this error impact system stability?

A: While it may not directly affect system stability, it can prevent certain operations from completing successfully if the XML manifest is required for those operations.

Summary

The ERROR_SXS_XML_E_UNCLOSEDSTARTTAG error indicates a specific issue with an unclosed start tag in an XML manifest file. This error typically occurs during parsing and can be resolved by ensuring that all XML content is well-formed and validated before use.