| 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.
The Universal Telemetry Client controls ETW sessions on behalf of diagnostic scenarios. 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.
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 |
| Evidence to collect | 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 |
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.
- Use a passing control on the same Windows build, then let the identical trace run beyond the threshold before replaying the trigger.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_REESCALATED_TOO_QUICKLY — measures time since a prior escalation, not trace runtime.
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.
Safe remediation
Delay escalation or lower the documented requirement only when the diagnostic design remains valid.
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.