| Previous | Next |
| WCM_E_RESTRICTIONFAILED | WCM_E_CYCLICREFERENCE |
WCM_E_MANIFESTCOMPILATIONFAILED
WCM_E_MANIFESTCOMPILATIONFAILED is the failure HRESULT 0x80220022 (signed decimal -2145255390, unsigned decimal 2149711906). Its severity bit is 1, facility is 34 (FACILITY_STATE_MANAGEMENT), and the facility-specific code field is 0x0022.
AllStat records the Windows SDK description as “XSD/XML Manifest compilation failed.”
Meaning in Settings Management Infrastructure
The SMI manifest compiler rejected the XML/XSD input. The operation reached schema compilation after the stream is readable but before a namespace can expose its settings model. The first branch to test is whether XML is well formed but violates the expected XSD; keep that separate from the possibility that schema references or namespaces are unresolved.
Point of failure
At this boundary, capture all ISettingsResult entries with source line and context, then correlate it with original manifest plus imported/included schemas. Assign ownership only after checking target build and SMIEngine.dll version.
Causes to test independently
- XML is well formed but violates the expected XSD
- schema references or namespaces are unresolved
- duplicate type/element declarations conflict during merge
- the manifest uses constructs unsupported by the target compiler
Data to collect
- all ISettingsResult entries with source line and context
- original manifest plus imported/included schemas
- target build and SMIEngine.dll version
- preprocessed artifact after substitutions and conditional generation
- a minimal compile containing the first failing declaration
Step-by-step diagnosis
- validate XML well-formedness and schema conformance separately
- resolve imports/includes using the same package layout as deployment
- fix the earliest compiler diagnostic before chasing later cascades
- compile with target-matched tools
- retain generated artifacts and hashes for reproducible builds
Recovery strategy
Retry requires corrected manifest input or a target-compatible compiler/schema set. Repeating compilation unchanged is deterministic.
What this value does not mean
WCM_E_INVALIDSTREAM can fail before compilation because the stream itself is unusable. MANIFESTCOMPILATIONFAILED means the compiler received data but could not build metadata.
Illustrative scenario
A manifest references an XSD type from an omitted include. The XML parses, but compilation cannot resolve the type declaration.
Implementation guidance
For operational telemetry, retain target build and SMIEngine.dll version; also record preprocessed artifact after substitutions and conditional generation. Preserve a redacted summary of a minimal compile containing the first failing declaration; use a cryptographic hash when that evidence is a file, stream, or generated artifact.
Official Microsoft references.
- Microsoft: SMI error and success constants.
- Microsoft: Settings Management Infrastructure API.
- Microsoft: SMI interfaces.
- Microsoft: ISettingsContext::Deserialize.
- Microsoft: ISettingsResult::GetLine.
Looking for a different code? Search another status or error code.