| Previous | Next |
| UTC_E_SETUP_NOT_AUTHORIZED | UTC_E_COMMAND_LINE_NOT_AUTHORIZED |
UTC_E_CHILD_PROCESS_FAILED
Where the UTC workflow stopped: completed child process
UTC_E_CHILD_PROCESS_FAILED (0x87C5101D) is a Universal Telemetry Client result from the scenario action execution layer. The key question is which UTC object rejected the request. The relevant state is completed child process: a UTC-launched process exited with a nonzero status without being forcibly terminated. This identifies a specific UTC/DiagTrack condition, not a general service failure.
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.
Evidence to preserve
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario action execution |
| Owning state or object | completed child process |
| Evidence to collect | executable hash, exact arguments, working directory, environment, exit code, stdout/stderr and duration |
| Narrow comparison | execute the same binary and arguments under the service account outside the scenario harness |
| Do not confuse with | UTC_E_EXE_TERMINATED means UTC ended a still-running process |
Controlled reproduction
- Collect the high-value state: executable hash, exact arguments, working directory, environment, exit code, stdout/stderr and duration.
- Use a passing control on the same Windows build, then execute the same binary and arguments under the service account outside the scenario harness.
Nearby result: UTC_E_EXE_TERMINATED — means UTC ended a still-running process.
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.
Correction and verification
Fix the child program or its inputs and retain its native exit code alongside this HRESULT.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario action execution while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario action execution while interpreting this result.
- Microsoft: UniversalTelemetryClient operational-log guidance — reference for scenario action execution while interpreting it.
- Microsoft: About Windows Error Reporting
Looking for a different code? Search another status or error code.