| Previous | Next |
| UTC_E_INVALID_FILTER | UTC_E_ESCALATION_NOT_AUTHORIZED |
UTC_E_EXE_TERMINATED
Separate cause from final symptom: RunExeWithArgs child process
When UTC_E_EXE_TERMINATED (0x87C5101A) is returned, the producing layer is scenario action execution. The first diagnostic step is to separate configuration, policy and runtime state. The rejected object or state is RunExeWithArgs child process, and the specific condition is that UTC terminated an executable action because of cancellation, timeout, shutdown or scenario transition. Keep this first HRESULT even if a later service call reports another error.
Scenario actions run under service-controlled identity, timeout and cancellation rules. The useful evidence is the exact action instance and its child process or script state, not a later generic service event. Stdout, stderr and native exit values should be retained separately from the UTC HRESULT.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | RunExeWithArgs child process |
| Producing layer | scenario action execution |
| Do not confuse with | UTC_E_CHILD_PROCESS_FAILED records a process that exited itself with a nonzero code |
| Evidence to collect | binary path/hash, command line, PID, job object, timeout, termination reason, stdout and stderr |
| Narrow comparison | run a fast no-op executable under the same action, then reproduce the blocking workload |
A focused experiment
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: binary path/hash, command line, PID, job object, timeout, termination reason, stdout and stderr.
- Use a passing control on the same Windows build, then run a fast no-op executable under the same action, then reproduce the blocking workload.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_CHILD_PROCESS_FAILED — records a process that exited itself with a nonzero code.
Child-action accounting
Keep process creation, job assignment, timeout, cancellation, exit code and output capture as separate timestamps. That sequence reveals whether the child failed itself, was terminated by UTC or never started.
Recovery criteria
Make the child honor cancellation and complete within the action budget; preserve partial output for diagnosis.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario action execution while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: About Windows Error Reporting
Looking for a different code? Search another status or error code.