| Previous | Next |
| UTC_E_SCRIPT_TYPE_INVALID | UTC_E_TRACEPROFILE_NOT_FOUND |
UTC_E_SCENARIODEF_NOT_FOUND
Separate cause from final symptom: scenario-definition lookup
UTC_E_SCENARIODEF_NOT_FOUND (0x87C51005) 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-definition lookup: the requested scenario identifier resolved to no installed or loaded definition. 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-definition lookup |
| Evidence to collect | scenario name or ID, configuration package/version, search locations, load events and caller request |
| Narrow comparison | query a known installed scenario through the same API and compare lookup diagnostics |
| Do not confuse with | UTC_E_TRACEPROFILE_NOT_FOUND applies to a referenced trace profile inside or beside a scenario |
A focused experiment
- Collect the high-value state: scenario name or ID, configuration package/version, search locations, load events and caller request.
- Use a passing control on the same Windows build, then query a known installed scenario through the same API and compare lookup diagnostics.
Nearby result: UTC_E_TRACEPROFILE_NOT_FOUND — applies to a referenced trace profile inside or beside a scenario.
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
Deploy or select the correct scenario definition; do not create an empty file under the missing name.
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.