Powershell Language Server didn't start #5129
Labels
Area-Startup
Issue-Bug
A bug to squash.
Needs: Author Feedback
Please give us the requested feedback!
Prerequisites
Summary
When ever i vs code it show following error message "Powershell Language Server didn't start"
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe '-NoProfile', '-ExecutionPolicy', 'Bypass', '-Command', 'Import-Module 'c:\Users\awano.vscode\extensions\ms-vscode.powershell-2024.4.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2024.4.0' -BundledModulesPath 'c:\Users\awano.vscode\extensions\ms-vscode.powershell-2024.4.0\modules' -EnableConsoleRepl -StartupBanner "PowerShell Extension v2024.4.0 Copyright (c) Microsoft Corporation. https://aka.ms/vscode-powershell Type 'help' to get help. " -LogLevel 'Normal' -LogPath 'c:\Users\awano\AppData\Roaming\Code\User\globalStorage\ms-vscode.powershell\logs\1737368448-f45e265f-e6c9-4ff9-a858-bf45372db3d71737368446592' -SessionDetailsPath 'c:\Users\awano\AppData\Roaming\Code\User\globalStorage\ms-vscode.powershell\sessions\PSES-VSCode-27136-476651.json' -FeatureFlags @() '" terminated with ...
PowerShell Version
Visual Studio Code Version
Extension Version
[email protected]
Steps to Reproduce
1/20/2025 10:20:48 AM [NORMAL] - Visual Studio Code: v1.96.4 64-bit on Windows 64-bit
1/20/2025 10:20:48 AM [NORMAL] - PowerShell Extension: v2024.4.0
1/20/2025 10:20:49 AM [NORMAL] - Starting 'Windows PowerShell (x64)' at: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
1/20/2025 10:20:49 AM [NORMAL] - PowerShell process started with PID: 27948
1/20/2025 10:21:08 AM [WARNING] - PowerShell process terminated or Extension Terminal was closed, PID: 27948
1/20/2025 10:21:09 AM [ERROR] - Extension Terminal is undefined.
1/20/2025 10:21:09 AM [ERROR] - PowerShell Language Server process didn't start!
Visuals
No response
Logs
No response
The text was updated successfully, but these errors were encountered: