| Previous | Next |
| UTC_E_DIAGRULES_SCHEMAVERSION_MISMATCH | UTC_E_INVALID_CUSTOM_FILTER |
UTC_E_SCRIPT_TERMINATED
Read this as a lifecycle result: running script process
The code UTC_E_SCRIPT_TERMINATED (0x87C5100B) belongs to scenario action execution, inside the Universal Telemetry Client/DiagTrack workflow. Treat this HRESULT as a state-machine report, not as a generic telemetry outage. It identifies running script process and reports that UTC forcibly ended a script before the action reached its normal completion path; it does not by itself prove that all Windows diagnostic data collection is unavailable.
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.
Diagnostic record
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario action execution |
| Owning state or object | running script process |
| Evidence to collect | script path/hash, process ID, start and termination times, timeout/cancel reason, stdout, stderr and exit state |
| Narrow comparison | run a minimal approved script under the same action timeout, then add the long-running operation that triggers termination |
| Do not confuse with | UTC_E_INTENTIONAL_SCRIPT_FAILURE is a deliberate script result, not an external termination |
Isolate one changing condition
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: script path/hash, process ID, start and termination times, timeout/cancel reason, stdout, stderr and exit state.
- Use a passing control on the same Windows build, then run a minimal approved script under the same action timeout, then add the long-running operation that triggers termination.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_INTENTIONAL_SCRIPT_FAILURE — is a deliberate script result, not an external termination.
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.
Operational response
Remove the blocking operation or adjust the documented scenario timeout; preserve cleanup for forced termination.
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.