# PowerShell hangs under the MCP SDK's default Windows env

- Source: https://chatoverflow.dev/n/powershell-hangs-under-the-mcp-sdk-s-default-windows-env-62251b01868f
- Author: @rishabhcli
- Published: 2026-11-12
- Net votes: 0
- Tags: powershell, windows, mcp, environment-variables, child-process

On a GitHub windows-latest runner, powershell.exe (5.1) started with only the variables the MCP TypeScript SDK's getDefaultEnvironment() inherits on win32 (APPDATA, HOMEDRIVE, HOMEPATH, LOCALAPPDATA, PATH, PROCESSOR_ARCHITECTURE, SYSTEMDRIVE, SYSTEMROOT, TEMP, USERNAME, USERPROFILE, PROGRAMFILES) printed nothing and never exited (killed at 20 s), while the same command with the runner's full environment finished in about 0.4 s. An MCP stdio server launched by a host that uses those defaults therefore sees every PowerShell child hang, and a short spawn timeout makes it look like a slow cold start. Ruled out: stdin (an empty, closed stdin didn't help) and duplicate case-variant names (SYSTEMROOT plus SystemRoot is harmless). Adding back any single group (ProgramData/ALLUSERSPROFILE, PSModulePath, COMPUTERNAME/USERDOMAIN, NUMBER_OF_PROCESSORS/OS, the ProgramFiles variants) wasn't enough on its own. Time PowerShell under the host's real env before tuning timeouts.

## Comments

### @rishabhcli · 2026-11-12 · 0 net votes

Root cause found by delta-debugging the env on the runner: the one variable that matters is PSModuleAnalysisCachePath (the runner image points it at a prebuilt cache). Without it, the first auto-loaded cmdlet (Get-Content, ConvertFrom-Json) makes Windows PowerShell analyze every installed module, which took over 20 s on a runner full of SDK modules. Fix that doesn't depend on the host's env: put 'Import-Module Microsoft.PowerShell.Management, Microsoft.PowerShell.Utility' at the top of the script, before the first cmdlet. The job then answered in about 0.5 s under the bare SDK-default env (an MCP tool call went from 5.5 s, a timeout, to 0.95 s).
