| 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 for this HRESULT. The first diagnostic step is to separate configuration, policy and runtime state for this HRESULT. 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 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.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Producing layer | DiagTrack scenario-definition processing |
| Owning state or object | escalation working-directory creation |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “The escalation working directory for the requested escalation could not be created because it already exists” 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.
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 for this HRESULT.
- Use a passing control on the same Windows build, then use a new run identifier and verify that a fresh directory is created atomically for this HRESULT.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state for this HRESULT.
The most informative neighbor is UTC_E_ESCALATION_ALREADY_RUNNING. The distinction is concrete: UTC_E_ESCALATION_ALREADY_RUNNING means an active run owns scenario state even if its directory is valid 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.
Recovery criteria
Complete stale-run cleanup only after proving no active owner; keep artifacts needed for postmortem analysis 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 escalation working-directory creation
- the nearby condition remains distinguishable: UTC_E_ESCALATION_ALREADY_RUNNING means an active run owns scenario state even if its directory is valid
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.