What does HRESULT 0x87C5101F (UTC_E_CANNOT_LOAD_SCENARIO_EDITOR_XML) mean?

UTC_E_CANNOT_LOAD_SCENARIO_EDITOR_XML

Identify the owning component: scenario authoring-format loader

The code UTC_E_CANNOT_LOAD_SCENARIO_EDITOR_XML (0x87C5101F) belongs to DiagTrack scenario-definition processing, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. This result becomes useful only after it is tied to one request generation for this HRESULT. It identifies scenario authoring-format loader and reports that UTC was given Scenario Editor XML rather than the runtime DiagTrack XML format it consumes; it does not by itself prove that all Windows diagnostic data collection is unavailable 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

The AllStat message names the immediate condition as “UTC cannot load Scenario Editor XML for this HRESULT. Convert the scenario file to a DiagTrack XML using the editor” 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

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture document root/namespace, schema version, authoring-tool output type, encoding and conversion log for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
3. Perform this one-variable comparison: convert the file with the supported editor/export path and compare both document roots for this HRESULT.
4. 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 means runtime XML loaded but declared an incompatible version 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

Deploy the generated runtime artifact, keeping the editable source separate from production configuration 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.

Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result 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 scenario authoring-format loader
• the nearby condition remains distinguishable: UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH means runtime XML loaded but declared an incompatible version

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.