We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whenever I start VS Code for the first time in a Windows session, PowerShell extension starts with a warning.
Moreover, closing the terminal session results in the below mentioned error.
Plus, the PowerShell extension banner message is looking odd:
Name Value ---- ----- PSVersion 7.4.4 PSEdition Core GitCommitId 7.4.4 OS Microsoft Windows 10.0.19045 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0.} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0
1.92.1 x64
[email protected]
No response
21.8.2024 16:17:03 [NORMAL] - Visual Studio Code: v1.92.1 64-bit on Windows 64-bit 21.8.2024 16:17:03 [NORMAL] - PowerShell Extension: v2024.2.2 21.8.2024 16:17:03 [NORMAL] - Starting 'PowerShell (x64)' at: C:\Program Files\PowerShell\7\pwsh.exe 21.8.2024 16:17:04 [NORMAL] - PowerShell process started with PID: 9012 21.8.2024 16:17:07 [WARNING] - PowerShell process terminated or Extension Terminal was closed, PID: 9012 21.8.2024 16:17:08 [ERROR] - Extension Terminal is undefined. 21.8.2024 16:17:09 [ERROR] - PowerShell Language Server process didn't start!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Prerequisites
Summary
Whenever I start VS Code for the first time in a Windows session, PowerShell extension starts with a warning.
Moreover, closing the terminal session results in the below mentioned error.
Plus, the PowerShell extension banner message is looking odd:
PowerShell Version
Visual Studio Code Version
Extension Version
[email protected]
Steps to Reproduce
Visuals
No response
Logs
The text was updated successfully, but these errors were encountered: