| Previous | Next |
| UTC_E_EVENTLOG_ENTRY_MALFORMED | UTC_E_SCRIPT_TERMINATED |
UTC_E_DIAGRULES_SCHEMAVERSION_MISMATCH
Identify the owning component: diagnostic-rules document version
When UTC_E_DIAGRULES_SCHEMAVERSION_MISMATCH (0x87C5100A) is returned, the producing layer is DiagTrack scenario-definition processing for this HRESULT. This result becomes useful only after it is tied to one request generation for this HRESULT. The rejected object or state is diagnostic-rules document version, and the specific boundary is that the diagrules document declares a schema version outside the range supported by this UTC client for this HRESULT. Later service errors should not replace this first result in the incident record for this HRESULT.
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 for this HRESULT. Mixing authoring files or package versions can make an otherwise valid identifier unusable for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
What to capture before retrying
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | diagnostic-rules document version |
| Producing layer | DiagTrack scenario-definition processing |
| Do not confuse with | UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH applies to the scenario document rather than diagrules |
| Decisive evidence | diagrules schemaversion, client build, package provenance, signing information and load event |
| Narrow comparison | load a rules file generated for the target build while keeping the scenario and triggers constant |
The AllStat message names the immediate condition as “<diagrules> node contains a schemaversion which is not compatible with this client” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.
Prove the boundary
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture diagrules schemaversion, client build, package provenance, signing information and load event for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
- Perform this one-variable comparison: load a rules file generated for the target build while keeping the scenario and triggers constant for this HRESULT.
- After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.
The most informative neighbor is UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH. The distinction is concrete: UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH applies to the scenario document rather than diagrules for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.
Configuration-generation check
Hash the scenario, rules and referenced profile files used for this HRESULT, 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 for this HRESULT.
Confirm the repair
Ship the rules package that matches the installed client or transform it with the supported authoring tool for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.
Avoid broad registry resets or global service-policy changes until the single-owner comparison has been run for this HRESULT. They can hide the original configuration generation without proving the contract was corrected for this HRESULT.
- the same request now produces its documented success or nonfatal status without a second hidden retry
- the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
- teardown followed by a second run does not reuse stale state or recreate diagnostic-rules document version
- the nearby condition remains distinguishable: UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH applies to the scenario document rather than diagrules
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 this result.
- Microsoft: UniversalTelemetryClient operational-log guidance — reference for DiagTrack scenario-definition processing while interpreting it.
- Microsoft: Windows Event Log query schema
Looking for a different code? Search another status or error code.