What does HRESULT 0x87C51003 (UTC_E_AOT_NOT_RUNNING) mean?

UTC_E_AOT_NOT_RUNNING

Identify the owning component: always-on trace controller

The code UTC_E_AOT_NOT_RUNNING (0x87C51003) belongs to ETW trace-session control, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. This result becomes useful only after it is tied to one request generation for this HRESULT. It identifies always-on trace controller and reports that an operation assumed that the configured always-on trace had an active ETW session, but no such session was running; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.

Code-specific check: The defining condition is “The always-on-trace is not running” Confirm that condition at the producing API before applying recovery intended for a neighboring result.

The Universal Telemetry Client controls ETW sessions on behalf of diagnostic scenarios for this HRESULT. ETW sessions have controller-owned names, in-memory buffers, providers, logging modes and lifetimes; a status at this layer should be correlated with the actual session list rather than inferred from the presence of an ETL file 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.

What to capture before retrying

The AllStat message names the immediate condition as “The always-on-trace is not running” 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.

Prove the boundary

1. Associate this result with one request, one scenario version and one service process ID for this HRESULT.
2. Save AutoLogger configuration, service state, ETW session list, boot sequence and first UTC operational events and the first lower-level HRESULT if one exists for this HRESULT.
3. Change no policy, provider set or destination except for this test: restart only the responsible service or boot-time trace configuration and verify whether the expected session appears for this HRESULT.
4. Compare the produced artifacts and operational events, not only the top-level return Value.

The most informative neighbor is UTC_E_TRACERS_DONT_EXIST. The distinction is concrete: UTC_E_TRACERS_DONT_EXIST means tracer objects were never initialized, not merely that the always-on session stopped 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.

Trace-session note

Use an ETW controller view to list session name, GUID, mode, buffers and enabled providers while this result is active. The presence of an ETL file from an earlier run is not proof that the required in-memory session currently exists or is owned by UTC for this HRESULT.

Confirm the repair

Repair the AutoLogger or service startup path before retrying the dependent action; do not fabricate an ETL file 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 always-on trace controller
• the nearby condition remains distinguishable: UTC_E_TRACERS_DONT_EXIST means tracer objects were never initialized, not merely that the always-on session stopped

Technical references

• Microsoft Open Specifications: Windows error-code registry — reference for ETW trace-session control while interpreting it.
• Microsoft: Universal Telemetry Client configuration diagnosis
• Microsoft: Event Tracing for Windows
• Microsoft: WPR and ETW sessions

Looking for a different code? Search another status or error code.