| Previous | Next |
| UTC_E_EXE_TERMINATED | UTC_E_SETUP_NOT_AUTHORIZED |
UTC_E_ESCALATION_NOT_AUTHORIZED
Map the code to the scenario graph: escalation authorization policy
The code UTC_E_ESCALATION_NOT_AUTHORIZED (0x87C5101B) belongs to policy and trust enforcement, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. A reliable investigation preserves the producing action before any cleanup runs for this HRESULT. It identifies escalation authorization policy and reports that the scenario was allowed to load but its escalation phase lacked the required authorization; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.
DiagTrack applies allowlists, signer checks, path restrictions and destination-specific collection policy for this HRESULT. These gates are intended security/privacy boundaries. Diagnosis should identify the exact denied capability rather than recommending broad privilege or policy changes 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.
Data needed for triage
| UTC diagnostic field | Value |
|---|---|
| Producing layer | policy and trust enforcement |
| Owning state or object | escalation authorization policy |
| Decisive evidence | scenario signer, destination, requested actions, caller token, policy decision and denied capability |
| Narrow comparison | run an otherwise identical approved scenario under the intended service identity |
| Do not confuse with | UTC_E_SETUP_NOT_AUTHORIZED rejects the setup phase before escalation begins |
The AllStat message names the immediate condition as “Escalation for scenario failed due to insufficient permissions” 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.
Reproduce without collateral changes
- Associate this result with one request, one scenario version and one service process ID for this HRESULT.
- Save scenario signer, destination, requested actions, caller token, policy decision and denied capability and the first lower-level HRESULT if one exists for this HRESULT.
- Change no policy, provider set or destination except for this test: run an otherwise identical approved scenario under the intended service identity for this HRESULT.
- Compare the produced artifacts and operational events, not only the top-level return Value.
The most informative neighbor is UTC_E_SETUP_NOT_AUTHORIZED. The distinction is concrete: UTC_E_SETUP_NOT_AUTHORIZED rejects the setup phase before escalation begins 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.
Policy-preserving test
Build the passing case for this HRESULT with an approved path, signer, command or certificate while keeping the enforcement mechanism enabled for this HRESULT. This demonstrates compliance with the policy boundary rather than merely removing the boundary for this HRESULT.
Fix the contract
Use an authorized signed configuration or remove the forbidden action; do not grant broad interactive admin rights 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 authorization policy
- the nearby condition remains distinguishable: UTC_E_SETUP_NOT_AUTHORIZED rejects the setup phase before escalation begins
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for policy and trust enforcement while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for policy and trust enforcement while interpreting this result.
- Microsoft: CertVerifyCertificateChainPolicy — reference for policy and trust enforcement while interpreting it.
- Microsoft: Windows cryptography functions
Looking for a different code? Search another status or error code.