| Previous | Next |
| UTC_E_WINRT_INIT_FAILED | UTC_E_INVALID_FILTER |
UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH
Identify the owning component: scenario document schema version
UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH has the unsigned value 0x87C51018. In UTC it comes from DiagTrack scenario-definition processing, where scenario document schema version owns the decision. Correlate this HRESULT with the exact request attempt that returned it. The immediate contract failed because the scenario definition itself targets a schema version incompatible with the installed client, so diagnosis should remain at that boundary until a controlled comparison crosses it.
DiagTrack scenarios are configuration-driven state machines. A scenario definition, its diagnostic rules, referenced profiles, triggers and action graph must all come from a compatible configuration generation. Mixing authoring files or package versions can make an otherwise valid identifier unusable.
What to capture before retrying
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | scenario document schema version |
| Producing layer | DiagTrack scenario-definition processing |
| Do not confuse with | UTC_E_DIAGRULES_SCHEMAVERSION_MISMATCH concerns the companion diagnostic-rules document |
| Evidence to collect | scenario schemaversion, UTC build, package revision, authoring-tool version and signature |
| Narrow comparison | load a scenario exported for the exact target build while reusing its referenced profiles |
Prove the condition
- Associate this result with one request, one scenario version and one service process ID.
- Save scenario schemaversion, UTC build, package revision, authoring-tool version and signature and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: load a scenario exported for the exact target build while reusing its referenced profiles.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_DIAGRULES_SCHEMAVERSION_MISMATCH — concerns the companion diagnostic-rules document.
Configuration-generation check
Hash the scenario, rules and referenced profile files used and record the UTC process start time. If files changed after the process loaded them, restart only after preserving the prior generation so the comparison remains auditable.
Confirm the repair
Regenerate or deploy a compatible scenario package rather than editing only the error code.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for DiagTrack scenario-definition processing while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for DiagTrack scenario-definition processing while interpreting it.
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: Windows Event Log query schema
Looking for a different code? Search another status or error code.