| Previous | Next |
| UTC_E_ESCALATION_TIMED_OUT | UTC_E_TRIGGER_MISMATCH |
UTC_E_SETUP_TIMED_OUT
Separate cause from final symptom: scenario setup deadline
UTC_E_SETUP_TIMED_OUT (0x87C51021) is a Universal Telemetry Client result from the DiagTrack scenario-definition processing layer. The first diagnostic step is to separate configuration, policy and runtime state. The relevant state is scenario setup deadline: the setup phase did not reach its ready state within the allotted interval. This identifies a specific UTC/DiagTrack condition, not a general service failure.
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.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Producing layer | DiagTrack scenario-definition processing |
| Owning state or object | scenario setup deadline |
| Evidence to collect | setup action sequence, per-action start/stop, service/RPC waits, deadline and cancellation result |
| Narrow comparison | precreate the prerequisite in a test image and verify that the same scenario proceeds to escalation |
| Do not confuse with | UTC_E_ESCALATION_TIMED_OUT occurs after setup succeeded |
A focused experiment
- Associate this result with one request, one scenario version and one service process ID.
- Save setup action sequence, per-action start/stop, service/RPC waits, deadline and cancellation result and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: precreate the prerequisite in a test image and verify that the same scenario proceeds to escalation.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_ESCALATION_TIMED_OUT — occurs after setup succeeded.
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.
Recovery criteria
Make setup bounded and observable; do not increase escalation duration to hide a setup deadlock.
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.