| Previous | Next |
| SDIAG_E_CANNOTRUN | SDIAG_E_RESOURCE |
SDIAG_E_VERSION
SDIAG_E_VERSION — 0x803C0109
This code places the first failure in troubleshooting-pack version compatibility. Operationally, the installed WTP runtime does not support the pack version or schema/features declared by the diagnostic package.
Operational meaning
A troubleshooting pack has distinct initialization, detection, resolution, and verification phases. Keep the ordinary result report together with the debug report, and identify whether the pack script, PowerShell host, managed host, resource loader, trust check, or verifier produced the first failure.
A missing resource or unsupported platform condition may coexist, but this code specifically identifies version compatibility.
Build the incident record
- Pack manifest/schema version, tools used to build it, and target Windows build
- Runtime/WTP component version and architecture
- Backward-compatible features versus newly introduced elements
- Pack signing/catalog state after any down-level rebuild
Identifiers, timestamps, versions, counts, state flags, hashes, and redacted paths normally provide enough correlation. Keep credentials, private keys, message bodies, recovery material, and personal data out of routine incident logs.
Tests that separate the causes
- Build the smallest pack using the same schema version.
- Run the package on its documented target build.
- Rebuild with the oldest required toolchain and compare manifest differences.
Repair without losing evidence
The corrective action should be narrow: Align the pack schema/toolchain with the supported Windows range or ship versioned packages selected by preflight logic.
Close the incident only when each supported OS selects and runs the correct package version, while down-level controls reject newer schemas cleanly.
Technical references
The details above are grounded in the following Microsoft specifications and API documentation:
Looking for a different code? Search another status or error code.