| Previous | Next |
| UTC_E_API_BUSY | UTC_E_EXCLUSIVITY_NOT_AVAILABLE |
UTC_E_TRACE_MIN_DURATION_REQUIREMENT_NOT_MET
Interpret the result in context: minimum trace observation window
UTC_E_TRACE_MIN_DURATION_REQUIREMENT_NOT_MET has the unsigned value 0x87C5102C. In UTC it comes from ETW trace-session control, where minimum trace observation window owns the decision. Start by locating the exact scenario-engine boundary that emitted this Value. The immediate contract failed because the active trace has not collected data for long enough to satisfy the escalation contract, so diagnosis should remain at that boundary until a controlled comparison crosses it for this HRESULT.
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.
Build a minimal evidence set
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | minimum trace observation window |
| Producing layer | ETW trace-session control |
| Do not confuse with | UTC_E_REESCALATED_TOO_QUICKLY measures time since a prior escalation, not trace runtime |
| Decisive evidence | session start time, required minimum, current monotonic elapsed time, profile ID and trigger time |
| Narrow comparison | let the identical trace run beyond the threshold before replaying the trigger |
The AllStat message names the immediate condition as “The running trace profile does not have a sufficient runtime to fulfill the escalation request” 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.
Run an A/B check
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: session start time, required minimum, current monotonic elapsed time, profile ID and trigger time for this HRESULT.
- Use a passing control on the same Windows build, then let the identical trace run beyond the threshold before replaying the trigger 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_REESCALATED_TOO_QUICKLY. The distinction is concrete: UTC_E_REESCALATED_TOO_QUICKLY measures time since a prior escalation, not trace runtime 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.
Safe remediation
Delay escalation or lower the documented requirement only when the diagnostic design remains valid 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.
Deleting the working directory, killing all ETW sessions or retrying in a tight loop can suppress this result temporarily while leaving the underlying lifecycle defect intact 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 minimum trace observation window
- the nearby condition remains distinguishable: UTC_E_REESCALATED_TOO_QUICKLY measures time since a prior escalation, not trace runtime
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for ETW trace-session control while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for ETW trace-session control while interpreting it.
- Microsoft: Event Tracing for Windows
- Microsoft: WPR and ETW sessions
Looking for a different code? Search another status or error code.