What does HRESULT 0x87C51007 (UTC_E_FORWARDER_ALREADY_ENABLED) mean?

UTC_E_FORWARDER_ALREADY_ENABLED

Locate the rejected contract: trigger-forwarder state

The code UTC_E_FORWARDER_ALREADY_ENABLED (0x87C51007) belongs to trigger-forwarder lifecycle, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. The symbolic name points to a narrow UTC contract that can be tested directly for this HRESULT. It identifies trigger-forwarder state and reports that an enable operation targeted a forwarder whose current state is already enabled; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.

Trigger forwarders connect a producer to scenario trigger processing and have their own registration and enable state for this HRESULT. Reusing a handle after configuration reload or crossing producer types can fail before any scenario filter is evaluated 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.

Capture checklist

The AllStat message names the immediate condition as “Trigger forwarder is already enabled” 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.

Comparison with a passing case

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture forwarder type, producer identity, registration handle, enable timestamp and duplicate caller for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
3. Perform this one-variable comparison: disable and re-enable the same instance once, then repeat the enable call to confirm idempotency behavior for this HRESULT.
4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.

The most informative neighbor is UTC_E_FORWARDER_PRODUCER_MISMATCH. The distinction is concrete: UTC_E_FORWARDER_PRODUCER_MISMATCH indicates a type/producer mismatch rather than a duplicate state change 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.

Platform-state note

Capture capability and identity state at the moment this result is returned. Session, container, service and destination state can change asynchronously, so a later successful query does not describe the failed generation for this HRESULT.

Resolution and regression test

Make enable idempotent in the caller or skip it when the queried state is already enabled 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 trigger-forwarder state
• the nearby condition remains distinguishable: UTC_E_FORWARDER_PRODUCER_MISMATCH indicates a type/producer mismatch rather than a duplicate state change

Technical references

• Microsoft Open Specifications: Windows error-code registry — reference for trigger-forwarder lifecycle while interpreting this result.
• Microsoft: Universal Telemetry Client configuration diagnosis — reference for trigger-forwarder lifecycle while interpreting it.
• Microsoft: Event Tracing for Windows
• Microsoft: UniversalTelemetryClient operational-log guidance

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