| 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 for this HRESULT. Treat this HRESULT as a state-machine report, not as a generic telemetry outage for this HRESULT. 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 for this HRESULT.
Scenario actions run under service-controlled identity, timeout and cancellation rules for this HRESULT. The useful evidence is the exact action instance and its child process or script state, not a later generic service event for this HRESULT. stdout, stderr and native exit values should be retained separately from the UTC HRESULT 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.
Diagnostic record
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario action execution |
| Owning state or object | running script process |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “RunScriptAction was forced to terminate a script” 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.
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 for this HRESULT.
- 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 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_INTENTIONAL_SCRIPT_FAILURE. The distinction is concrete: UTC_E_INTENTIONAL_SCRIPT_FAILURE is a deliberate script result, not an external termination 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.
Child-action accounting
Keep process creation, job assignment, timeout, cancellation, exit code and output capture as separate timestamps for this HRESULT. That sequence reveals whether the child failed itself, was terminated by UTC or never started for this HRESULT.
Operational response
Remove the blocking operation or adjust the documented scenario timeout; preserve cleanup for forced termination 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.
Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result 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 running script process
- the nearby condition remains distinguishable: UTC_E_INTENTIONAL_SCRIPT_FAILURE is a deliberate script result, not an external 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.