ERROR_SXS_XML_E_MISSINGEQUALS - 14073 (0x36F9)
Manifest Parse Error : Missing equals sign between attribute and attribute value.
Updated: Feb 21, 2026
Technical Background
The ERROR_SXS_XML_E_MISSINGEQUALS (14073) is a specific error code related to the Windows Side-by-Side (SxS) manifest parsing process. This error indicates that an XML-based manifest file has been encountered with improperly formatted attributes, specifically missing equals signs between attribute names and their values.
Error Details
The error ERROR_SXS_XML_E_MISSINGEQUALS is generated when a manifest parser encounters an issue during the validation of an XML document. The primary cause of this error is the absence of an equals sign (=) in the syntax of an XML attribute, which is essential for correctly identifying and parsing the attribute-value pairs.
Common Causes
- Invalid parameter values: Incorrectly formatted attributes within a manifest file can lead to this error.
- Incorrect object type: The manifest being parsed may not be properly structured or contain incorrect types of elements that are expected by the parser.
Real-World Context
This error typically occurs during the execution of applications that rely on SxS manifests for component discovery and loading. These manifests are used to describe dependencies, versioning information, and other metadata required for the proper functioning of components within an application or system.
Is This Error Critical?
The criticality of this error depends on the context in which it occurs. In most cases, encountering ERROR_SXS_XML_E_MISSINGEQUALS will prevent the affected component from loading correctly, potentially leading to application failures or crashes. However, the impact can vary based on whether the missing equals sign is part of a critical manifest that is essential for system operation.
How to Diagnose
To diagnose this error, follow these steps:
- Review Operation Context: Ensure that the manifest file being parsed is correct and intended for use in the current context.
- Validate Parameters: Check all attributes within the manifest files to ensure they are correctly formatted with equals signs separating attribute names from their values.
- Confirm Object Types: Verify that the XML documents adhere to the expected structure and contain valid object types as defined by the SxS framework.
How to Resolve
To resolve this issue, take the following actions:
- Correct Parameter Usage: Ensure all attributes in manifest files are correctly formatted with equals signs.
- Adjust Operation Context: If the error is encountered during application execution, review and adjust any configuration or deployment settings that may be causing improper manifest usage.
- Restore Data: In some cases, restoring a properly formatted backup of the manifest file might resolve the issue.
- Retry Operation with Valid Inputs: Attempt to reload or reinitialize the component using valid manifest files.
Developer Notes
Developers should ensure that all XML-based manifests used in their applications are correctly formatted and validated before deployment. This can be achieved through automated validation tools or by implementing custom checks within application code.
Related Errors
ERROR_SXS_FILE_HASH(14072): Indicates a hash mismatch during manifest parsing.ERROR_SXS_XML_E_MISSINGQUOTE(13985): Occurs when an attribute value is missing a closing quote in the XML document.
FAQ
Q: What causes ERROR_SXS_XML_E_MISSINGEQUALS?
A: This error occurs due to improperly formatted attributes within manifest files, specifically missing equals signs between attribute names and their values.
Q: How can I prevent this error from occurring?
A: Ensure all XML-based manifests are correctly formatted with valid attribute syntax. Use validation tools or custom checks in your code to catch and correct such issues before deployment.
Summary
ERROR_SXS_XML_E_MISSINGEQUALS is a specific error related to the parsing of XML manifest files used by the Windows Side-by-Side framework. Properly formatted manifests are crucial for the successful loading and execution of components within an application or system. By understanding the causes, diagnosing the issue, and taking appropriate corrective actions, developers can mitigate this error and ensure smooth operation.