| Previous | Next |
| UTC_E_UNAPPROVED_SCRIPT | UTC_E_SCENARIO_THROTTLED |
UTC_E_SCRIPT_MISSING
Interpret the result in context: RunScriptAction file resolution
When UTC_E_SCRIPT_MISSING (0x87C5103A) is returned, the producing layer is scenario action execution. Start by locating the exact scenario-engine boundary that emitted this value. The rejected object or state is RunScriptAction file resolution, and the specific condition is that the scenario references a script that is not present on the device at execution time. 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.
Build a minimal evidence set
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | RunScriptAction file resolution |
| Producing layer | scenario action execution |
| Do not confuse with | UTC_E_UNAPPROVED_SCRIPT means a present script failed policy approval |
| Evidence to collect | configured/expanded path, package revision, file deployment state, architecture and scenario version |
| Narrow comparison | place a minimal approved script at the exact resolved path and repeat the action |
Run an A/B check
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture configured/expanded path, package revision, file deployment state, architecture and scenario version. Do this before restarting the service or deleting any working directory.
- Perform this one-variable comparison: place a minimal approved script at the exact resolved path and repeat the action.
- After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created.
Nearby result: UTC_E_UNAPPROVED_SCRIPT — means a present script failed policy approval.
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.
Safe remediation
Fix package deployment or capability gating while preserving approval/signature requirements.
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.
