| Previous | Next |
| UTC_E_GETFILE_FILE_PATH_NOT_APPROVED | UTC_E_TIME_TRIGGER_ON_START_INVALID |
UTC_E_ESCALATION_DIRECTORY_ALREADY_EXISTS
Separate cause from final symptom: escalation working-directory creation
The code UTC_E_ESCALATION_DIRECTORY_ALREADY_EXISTS (0x87C5102F) belongs to DiagTrack scenario-definition processing, inside the Universal Telemetry Client/DiagTrack workflow. The first diagnostic step is to separate configuration, policy and runtime state. It identifies escalation working-directory creation and reports that the run expected to create a fresh working directory but a file-system object already occupies that path; 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.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Producing layer | DiagTrack scenario-definition processing |
| Owning state or object | escalation working-directory creation |
| Evidence to collect | computed path, scenario/run IDs, owner, creation time, contents, active process and prior cleanup events |
| Narrow comparison | use a new run identifier and verify that a fresh directory is created atomically |
| Do not confuse with | UTC_E_ESCALATION_ALREADY_RUNNING means an active run owns scenario state even if its directory is valid |
A focused experiment
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: computed path, scenario/run IDs, owner, creation time, contents, active process and prior cleanup events.
- Use a passing control on the same Windows build, then use a new run identifier and verify that a fresh directory is created atomically.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_ESCALATION_ALREADY_RUNNING — means an active run owns scenario state even if its directory is valid.
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
Complete stale-run cleanup only after proving no active owner; keep artifacts needed for postmortem analysis.
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.