question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PowerShell Extension 2020.4.0 Crashes VS Code during load

See original GitHub issue

System Details

  1. Windows 10, 1903
  2. VS Code v1.44.1 (System Setup)
  3. PowerShell Extension v2020.4.0
  4. Symantec Endpoint Protection 14.2.5323.2000
  5. $PSVersionTable
PSVersion 5.1.18362.628
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.628
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Issue Description

Fresh installed everything, right after launching VS Code and searched for PowerShell in Marketplace. Installing it crashes VS Code (I needed to force it to close and manually deleting the extension folder in %userprofile%.vscode to be able to launch VS Code properly).

Logs

4/17/2020 3:25:06 PM [NORMAL] - powershell.exe started.
4/17/2020 3:25:06 PM [NORMAL] - Waiting for session file
4/17/2020 3:27:06 PM [NORMAL] - Error occurred retrieving session file:
Timed out waiting for session file to appear.
4/17/2020 3:27:06 PM [NORMAL] - Language server startup failed.
4/17/2020 3:27:06 PM [ERROR] - The language service could not be started: 
4/17/2020 3:27:06 PM [ERROR] - Timed out waiting for session file to appear.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
tonsanchezcommented, Apr 22, 2020

@tonsanchez it sounds like our problems are probably the same. Are you running Avecto/BeyondTrust on the workstation you are having problems with? I’m wondering if the problem doesn’t lay there.

Here’s another case of this problem with someone running Avecto: #2066

That’s right. My workstation laptop is also running Avecto/BeyondTrust.

1reaction
EdCallahancommented, Apr 21, 2020

What if you try and start with PowerShell 5.1 x86 @tonsanchez? To do that on my computer I can edit “$env:AppData\Code\User\settings.json” and set the default powershell version with:

“powershell.powerShellDefaultVersion”: “Windows PowerShell (x86)”

I run with very little delay running x86, and even faster with PowerShell 7.0. The crippling delay is only from PowerShell 5.1 x64 on my boxes.

Read more comments on GitHub >

github_iconTop Results From Across the Web

PowerShell session has terminated upon loading a script ...
I Was having the same issues connecting to a remote session with VS Code, was getting the same output from VS Code.
Read more >
PowerShell Extension for Visual Studio Code August 2022 ...
This release adds a walkthrough experience for getting started with PowerShell in VS Code, more regression tests, a major LSP client library ...
Read more >
tsm configuration set Options
Below is a list of configuration options or keys that you can set with the tsm configuration set command. In many cases you...
Read more >
PowerShell editing with Visual Studio Code
The extension works anywhere you can run VS Code and PowerShell 7 or higher. The extension also works for Windows PowerShell 5.1. The...
Read more >
Auto Formatting PowerShell in Visual Studio Code
Formatting a PowerShell Script · Download and install Visual Studio Code. · Once Visual Studio Code is installed, add the PowerShell extension:
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found