| Previous | Next |
| SDIAG_E_SCRIPT | SDIAG_E_MANAGEDHOST |
SDIAG_E_POWERSHELL
SDIAG_E_POWERSHELL means that 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.
A valid PowerShell script can still fail if the hosted runtime cannot start or accept commands.
Build the incident record
- PowerShell engine/version, WTP host process, runspace initialization error, and module load events
- Language mode, execution policy, AppLocker/WDAC, and constrained environment
- Debug report and PowerShell operational logs
- Difference between built-in and custom troubleshooting packs
Tests that separate the causes
- Run a minimal signed pack containing one trivial PowerShell detector.
- Start PowerShell under the same identity and policy context.
- Remove nonessential modules/profiles from the test pack.
How to interpret the comparison
Use the outcomes to narrow the layer rather than to accumulate unrelated fixes for hosted PowerShell runtime interaction:
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.
Close the incident only when a minimal pack and the original pack both create runspaces reliably under interactive and unattended execution.
Technical references
Looking for a different code? Search another status or error code.