| Previous | Next |
| SDIAG_E_SCRIPT | SDIAG_E_MANAGEDHOST |
SDIAG_E_POWERSHELL
Treat this HRESULT as a marker, not as a request for a generic restart or reinstall. It is returned when WTP could not initialize, communicate with, or execute through its hosted PowerShell runtime.
Operational meaning
A troubleshooting pack has distinct initialization, detection, resolution, and verification phases. Keep the ordinary result report together with the debug report, and identify whether the pack script, PowerShell host, managed host, resource loader, trust check, or verifier produced the first failure.
Do not collapse this result into a nearby status. A valid PowerShell script can still fail if the hosted runtime cannot start or accept commands. Compare lifecycle, identity, caller, and first API.
Build the incident record
| Preserve before changing state | Diagnostic value |
|---|---|
| PowerShell engine/version, WTP host process, runspace initialization error, and module load events | Separates contract failure from environment. |
| Language mode, execution policy, AppLocker/WDAC, and constrained environment | Creates a stable before/after control. |
| Debug report and PowerShell operational logs | Tests whether the first boundary moves. |
| Difference between built-in and custom troubleshooting packs | Pins evidence to one attempt. |
Identifiers, timestamps, versions, counts, state flags, hashes, and redacted paths normally provide enough correlation. Keep credentials, private keys, message bodies, recovery material, and personal data out of routine incident logs.
Tests that separate the causes
- Run a minimal signed pack containing one trivial PowerShell detector; retain one negative control so that a broad workaround is not mistaken for a root-cause correction.
- Start PowerShell under the same identity and policy context; keep every other input fixed and record the first event that differs from the failing run.
- Remove nonessential modules/profiles from the test pack; use a disposable or backed-up environment when the comparison changes boot, security, device, queue, or encryption state.
If the failure disappears after a broad restart, treat that as a clue about lifetime or state, not as proof of repair. Reproduce the original hosted PowerShell runtime interaction operation with targeted instrumentation before closing the incident.
Interpretation boundaries
Use the outcomes to narrow the layer rather than to accumulate unrelated fixes for hosted PowerShell runtime interaction:
| Observed result | Interpretation |
|---|---|
| The minimal or known-good comparison succeeds | The control works; inspect production-specific state. |
| The control fails at the same first operation | The control also fails; inspect host/provider evidence. |
| A new HRESULT marks another boundary | The failure moved to another boundary; diagnose the new status separately rather than treating it as confirmation that the entire operation is fixed. |
Repair without losing evidence
Repair the failed contract rather than the surrounding system: Restore the supported PowerShell/WTP host environment and remove incompatible policy or module dependencies. Preserve the pre-change configuration or trace.
Close the incident only when a minimal pack and the original pack both create runspaces reliably under interactive and unattended execution. Repeat under the original identity and state. A different environment is comparison, not proof.
Technical references
Use these sources for the formal contract, then combine them with evidence from the returning application or service for hosted PowerShell runtime interaction:
- Microsoft Open Specifications: HRESULT values.
- Microsoft: Windows Troubleshooting Platform.
- Microsoft: About WTP.
- Microsoft: debugging troubleshooting packs.
Looking for a different code? Search another status or error code.