You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2026-08-09 22:47:04.732 [info] Visual Studio Code: v1.107.0 64-bit on Windows 64-bit
2026-08-09 22:47:04.732 [info] PowerShell Extension: v2025.4.0
2026-08-09 22:47:04.848 [info] Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2026-08-09 22:47:05.799 [info] PowerShell process started with PID: 9340
2026-08-09 22:47:39.278 [warning] Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
2026-08-09 22:49:10.369 [warning] PowerShell process terminated or Extension Terminal was closed, PID: 9340
2026-08-09 22:49:10.417 [error] Extension Terminal is undefined.
2026-08-09 22:49:10.981 [error] PowerShell Language Server process didn't start!
2026-08-09 22:49:11.545 [warning] Re-entered 'start' so waiting...
2026-08-09 22:49:11.624 [info] Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2026-08-09 22:49:12.076 [info] PowerShell process started with PID: 20496
2026-08-09 22:49:45.075 [warning] Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
2026-08-09 22:47:04.732 [info] Visual Studio Code: v1.107.0 64-bit on Windows 64-bit
2026-08-09 22:47:04.732 [info] PowerShell Extension: v2025.4.0
2026-08-09 22:47:04.848 [info] Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2026-08-09 22:47:05.799 [info] PowerShell process started with PID: 9340
2026-08-09 22:47:39.278 [warning] Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
2026-08-09 22:49:10.369 [warning] PowerShell process terminated or Extension Terminal was closed, PID: 9340
2026-08-09 22:49:10.417 [error] Extension Terminal is undefined.
2026-08-09 22:49:10.981 [error] PowerShell Language Server process didn't start!
2026-08-09 22:49:11.545 [warning] Re-entered 'start' so waiting...
2026-08-09 22:49:11.624 [info] Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2026-08-09 22:49:12.076 [info] PowerShell process started with PID: 20496
2026-08-09 22:49:45.075 [warning] Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
Visuals
2026-08-09 22:47:04.732 [info] Visual Studio Code: v1.107.0 64-bit on Windows 64-bit
2026-08-09 22:47:04.732 [info] PowerShell Extension: v2025.4.0
2026-08-09 22:47:04.848 [info] Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2026-08-09 22:47:05.799 [info] PowerShell process started with PID: 9340
2026-08-09 22:47:39.278 [warning] Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
2026-08-09 22:49:10.369 [warning] PowerShell process terminated or Extension Terminal was closed, PID: 9340
2026-08-09 22:49:10.417 [error] Extension Terminal is undefined.
2026-08-09 22:49:10.981 [error] PowerShell Language Server process didn't start!
2026-08-09 22:49:11.545 [warning] Re-entered 'start' so waiting...
2026-08-09 22:49:11.624 [info] Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2026-08-09 22:49:12.076 [info] PowerShell process started with PID: 20496
2026-08-09 22:49:45.075 [warning] Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
Thanks for the report! This looks like a genuine startup failure — the extension launched Windows PowerShell 5.1 and PSES died after roughly 2 minutes without initializing, leaving Extension Terminal is undefined.
To help diagnose this, we need a few more details:
PSES log files — The extension output channel (what you pasted) only shows high-level events. The actual PSES logs have the crash reason. You can find them with:
Please share the contents of the most recent .log file.
Privilege enforcement / security software — The warning "Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance." appeared twice. Are you running any endpoint protection, DLP, application control (AppLocker / WDAC), or enterprise MDM software? If so, what product?
Reproduction steps — What were you doing when this happened (opening a specific file, just launching VS Code, etc.)? Does it happen every time, or only sometimes?
Network / proxy — Is VS Code running in an environment with a proxy or restricted network access?
Without the PSES log files in particular, it is very difficult to identify the root cause.
Activity
github-actions commentedon Aug 10, 2026
Thanks for the report! This looks like a genuine startup failure — the extension launched Windows PowerShell 5.1 and PSES died after roughly 2 minutes without initializing, leaving
Extension Terminal is undefined.To help diagnose this, we need a few more details:
PSES log files — The extension output channel (what you pasted) only shows high-level events. The actual PSES logs have the crash reason. You can find them with:
Please share the contents of the most recent
.logfile.Privilege enforcement / security software — The warning "Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance." appeared twice. Are you running any endpoint protection, DLP, application control (AppLocker / WDAC), or enterprise MDM software? If so, what product?
Reproduction steps — What were you doing when this happened (opening a specific file, just launching VS Code, etc.)? Does it happen every time, or only sometimes?
Network / proxy — Is VS Code running in an environment with a proxy or restricted network access?
Without the PSES log files in particular, it is very difficult to identify the root cause.
Add this agentic workflows to your repo
To install this agentic workflow, run