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. Correlate this HRESULT with the exact request attempt that returned it. 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.

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

Prove the condition

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. Do this before restarting the service or deleting any working directory.
3. Perform this one-variable comparison: convert the file with the supported editor/export path and compare both document roots.
4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created.

Nearby result: UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH — means runtime XML loaded but declared an incompatible version.

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

Deploy the generated runtime artifact, keeping the editable source separate from production configuration.

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