The Language Service Could not be started

[spidey323]

The extension wont even load so I can't get the PSVersion.
Everything was working fine until the update of the powershell extension.

Issue Description

The Language Service Could not be started
3/6/2020 8:24:21 AM [NORMAL] - Visual Studio Code v1.42.1 64-bit
3/6/2020 8:24:21 AM [NORMAL] - PowerShell Extension v2020.3.0
3/6/2020 8:24:21 AM [NORMAL] - Operating System: Windows 64-bit
3/6/2020 8:24:21 AM [NORMAL] - Language server starting --
3/6/2020 8:24:21 AM [NORMAL] -     PowerShell executable: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
3/6/2020 8:24:21 AM [NORMAL] -     PowerShell args: -NoProfile -NonInteractive -ExecutionPolicy Bypass -Command Import-Module 'c:\Users\xxxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.3.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users\xxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules' -EnableConsoleRepl -LogLevel 'Normal' -LogPath 'c:\Users\xxxxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\logs\1583504661-d29ecc6e-241c-4f6d-a6ef-96dc719a4e801583504610369\EditorServices.log' -SessionDetailsPath 'c:\Users\xxxxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\sessions\PSES-VSCode-16792-972902' -FeatureFlags @() 
3/6/2020 8:24:21 AM [NORMAL] -     PowerShell Editor Services args: Import-Module 'c:\Users\xxxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.3.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users\xxxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules' -EnableConsoleRepl -LogLevel 'Normal' -LogPath 'c:\Users\michael.hagedorn\.vscode\extensions\ms-vscode.powershell-2020.3.0\logs\1583504661-d29ecc6e-241c-4f6d-a6ef-96dc719a4e801583504610369\EditorServices.log' -SessionDetailsPath 'c:\Users\xxxxx\.vscode\extensions\ms-vscode.powershell-2020.3.0\sessions\PSES-VSCode-16792-972902' -FeatureFlags @() 
3/6/2020 8:24:21 AM [NORMAL] - powershell.exe started.
3/6/2020 8:24:21 AM [NORMAL] - Waiting for session file
3/6/2020 8:26:21 AM [NORMAL] - Error occurred retrieving session file
3/6/2020 8:26:21 AM [NORMAL] - Language server startup failed.
3/6/2020 8:26:21 AM [ERROR] - The language service could not be started: 
3/6/2020 8:26:21 AM [ERROR] - Timed out waiting for session file to appear.

Name                           Value
----                           -----
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

[rjmholt]

Everything was working fine until the update of the powershell extension.

This is at least a reasonable sign that it's some we might be able to fix. We've seen other issues like this where an OS update causes issues.

It looks like this is a session file issue but we don't log enough information to discern the problem. It might be available in VSCode's own logs (try the Developer: Show Logs option and pick Extension Host) or possibly in the developer tools console (available in the help menu -- looks like Chrome's dev tools console). Alternatively, if you install this build it should log the relevant information in the same log as the one you posted:

psvsix.zip

[spidey323]

I'm glad it looks fixable. I've tried uninstalling/re-installing several times. Looks like it happened with the update for March. (I even tried installing an older version. Appreciate your help.
Here's the log output from the above command:

[2020-03-06 13:56:12.488] [exthost] [info] extension host started
[2020-03-06 13:56:12.544] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-03-06 13:56:12.545] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-03-06 13:56:12.554] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-03-06 13:56:12.555] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/emmet/dist/extension
[2020-03-06 13:56:12.588] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.git","_lower":"vscode.git"},"activationEvent":"*"}
[2020-03-06 13:56:12.588] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/git/dist/main
[2020-03-06 13:56:12.634] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-03-06 13:56:12.634] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/merge-conflict/dist/extension
[2020-03-06 13:56:12.641] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-03-06 13:56:12.641] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/search-result/dist/extension.js
[2020-03-06 13:56:12.645] [exthost] [info] ExtensionService#_doActivateExtension vscode.vscode-account {"startup":true,"extensionId":{"value":"vscode.vscode-account","_lower":"vscode.vscode-account"},"activationEvent":"*"}
[2020-03-06 13:56:12.645] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/vscode-account/dist/extension.js
[2020-03-06 13:56:12.651] [exthost] [info] eager extensions activated

[spidey323]

The application hangs as soon as I install the powershell ext so I have to keep it disabled. -FYI

[spidey323]

[rjmholt]

Here's the log output from the above command:

Hmmm, I don't see anything of use in there (unfortunately VSCode's own logs are quite opaque).

Could you try installing the (zipped) VSIX I linked above? Can do it like this:

expand-archive ./psvsix.zip ./psext.vsix
code --install-extension ./psext.vsix

You'll then need to disable the PowerShell extension (because the VSIX is a "PowerShell Preview" extension) and restart VSCode.

Hopefully that will log the reason for startup failure.

The hang you're seeing may well be #2377, which is a VSCode bug we're still waiting on a fix for.

[spidey323]

I dont see the link. The hang is more when the extension is trying to be loaded, that's what happens.
Please let me know how to get the VSIX. I need to get up and running asap. thanks

[spidey323]

I've already tried the Powershell preview ext and get the same behavior.

[TylerLeonhardt]

The link is in this comment: #2526 (comment)

[rjmholt]

Link

[happywino]

I started seeing the same issue today, possibly right after VSCode autoupdated. If I run the launch command from a regular command prompt here's the error I get;

Import-Module : The module manifest 'C:\Users\ad_jcphilli\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules\Powe
rShellEditorServices\PowerShellEditorServices.psd1' could not be processed because it is not a valid Windows
PowerShell restricted language file. Remove the elements that are not permitted by the restricted language:
At C:\Users\ad_jcphilli\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules\PowerShellEditorServices\PowerShellEdi
torServices.psd1:12 char:18
+ RootModule = if ($PSEdition -eq 'Core')
+                  ~~~~~~~~~~
A variable that cannot be referenced in restricted language mode or a Data section is being referenced. Variables that
can be referenced include the following: $PSCulture, $PSUICulture, $true, $false, and  $null.
At line:1 char:1
+ Import-Module 'c:\Users\ad_jcphilli\.vscode\extensions\ms-vscode.powershell-2020 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (C:\Users\ad_jcp...orServices.psd1:String) [Import-Module], Missing
   MemberException
    + FullyQualifiedErrorId : Modules_InvalidManifest,Microsoft.PowerShell.Commands.ImportModuleCommand

Start-EditorServices : The term 'Start-EditorServices' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:151
+ ... ervices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostPro ...
+                    ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Start-EditorServices:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

[spidey323]

@rjmholt Where do I place the psvsix.zip so code can unzip and install?

[happywino]

After a little more investigation I think the issue might be the use of $PSEdition in .vscode\extensions\ms-vscode.powershell-2020.3.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1

According to this source;

By default, only the following variables are permitted in RestrictedLanguage mode:

$PSCulture
$PSUICulture
$True
$False
$Null
Module manifests, which use RestrictedLanguage mode, permit the following additional variables as well:

$PSScriptRoot
$PSEdition (in PowerShell Core)
$EnabledExperimentalFeatures (in PowerShell Core)

I am not using PowerShell Core;

Name Value

---

PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 6.3.9600.19170
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2

That said, when I change line 12 of the psd1 from

RootModule = if ($PSEdition -eq 'Core')
    {
        'bin/Core/Microsoft.PowerShell.EditorServices.Hosting.dll'
    }
    else
    {
        'bin/Desktop/Microsoft.PowerShell.EditorServices.Hosting.dll'
    }

to

RootModule = 'bin/Desktop/Microsoft.PowerShell.EditorServices.Hosting.dll'

I don't see the error but the terminal window displays the text below but never finishes loading.

 =====> PowerShell Integrated Console <=====

[rjmholt]

Where do I place the psvsix.zip so code can unzip and install?

@spidey323 You need to unzip it yourself and then install the VSIX in code or through PowerShell.

Try running this in PowerShell:

expand-archive ./psvsix.zip ./psext.vsix
code --install-extension ./psext.vsix

[rjmholt]

PSVersion 4.0

@happywino you're using PowerShell 4, which the PowerShell extension no longer supports.

Even changing the manifest, PSES won't load properly because PSReadLine does not support PowerShell 4.

The $PSEdition variable in manifests is permitted from PS 5.1.

[happywino]

Ouch, so what version of the extension should I install and use given I have no control of the powershell version installed on my environment?

…

On Fri, Mar 6, 2020, 4:52 PM Robert Holt ***@***.***> wrote: PSVersion 4.0 @happywino <https://github.com/happywino> you're using PowerShell 4, which the PowerShell extension no longer supports <#1310> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2526?email_source=notifications&email_token=ADRA3LTFZKMO7VINL2R4V2DRGGLEBA5CNFSM4LDF2SYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEODJQYI#issuecomment-596023393>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADRA3LWRYSKTVFOY2JZPZITRGGLEBANCNFSM4LDF2SYA> .

[TylerLeonhardt]

In the extensions pane click on the gear:

Then click "Install another version..."

and choose the one right before the last one.

That said...

I would highly recommend pushing on those that do have control to upgrade to Windows PowerShell 5.1 (in-place upgrade)...

or better yet, go get PowerShell 7 which is a side-by-side install with Windows PowerShell and has the best experience with the vscode extension.

[lzocateli]

Guys, I noticed that the PowerShell extension was giving an error when opening a .ps1 file, so I uninstalled it, closed vscode and tried to install again, I couldn't, now it's not possible to install, see the generated log.
VSIXInstaller_0b284ba3-a28e-4f61-a104-2a0db64c4bd2.log

[spidey323]

@rjmholt : This appears to be an issue. Do we wait for a fix or what's the next action plan?

[TylerLeonhardt]

Can you also attach the logs for the PowerShell extension here so we can get a better idea of what's going on?

Please make sure you enable Diagnostic logging:

"powershell.developer.editorServicesLogLevel": "Diagnostic"

[mmascolino]

1583783706-7a4eb4ff-6b52-4f10-809c-1f499e45a07d1583783704111.zip
I too can reproduce this although there isn't much in the logs despite turning on the diagnostic logging.

[rjmholt]

and tried to install again, I couldn't, now it's not possible to install, see the generated log.

@lincolnzocateli those logs look like something Visual Studio might create, which is where the VSIX tries to install itself if you double click on it. How are you installing the PowerShell extension? The best way is to find it in the VSCode marketplace and install it directly by clicking on the install button

[rjmholt]

@mmascolino that does match the OP's log issue.

Can you try installing this VSIX (you will need to unzip it and then install it into VSCode, disable the PowerShell extension and make sure that one is picked up as powershell-preview) and collecting the logs from that?

[rjmholt]

@spidey323

Do we wait for a fix or what's the next action plan?

We currently need more information to reproduce this issue. Without that information, we're unable to fix it, since we haven't been able to reproduce this issue in our environments.

If you're able to install this VSIX and send the same logs to us again, that would help us resolve this issue.

[rjmholt]

I think this is #2538. Going to use that issue, since there's good info in there

[richardm1]

Another Avecto DefendPoint victim here. Same issue. I'm going to make a bunch of noise here and see if I can get someone to rattle Avecto's cage and push for a fix.

[EdCallahan]

Another Avecto DefendPoint victim here. Same issue. I'm going to make a bunch of noise here and see if I can get someone to rattle Avecto's cage and push for a fix.

I've run some troubleshooting for Avecto and they remoted into my machine late last week to investigate. Hoping to have a resolution from them yet this week, or at least a plan. They think it's something in the rules, but I suspect the problem is deeper than that.

Creating a rule that elevates code.exe and all subprocesses helps a lot, but does not fix the problem. However with that rule in place x64 powershell starts in under two minutes on my machine, without it powershell basically won't start at all.

[richardm1]

@EdCallahan would you happen to have a ticket number with the Avecto folks? I'm having a hard time getting traction here so I'd like to hand my people a ready-made support call -- they're giving me a hard time when I ask them to escalate to somebody who has Avecto's phone number. :-(

[EdCallahan]

@EdCallahan would you happen to have a ticket number with the Avecto folks? I'm having a hard time getting traction here so I'd like to hand my people a ready-made support call -- they're giving me a hard time when I ask them to escalate to somebody who has Avecto's phone number. :-(

@richardm1 Yes: CS0879827

I'm disappointed I haven't heard back from them yet. There were some lost communications at first, and a switch in who was handling the ticket. And I was away for a week. But the guy I finally worked with when he remoted into my machine seemed very competent, and was going to reproduce the problem on a test box. I haven't heard if he succeeded or not, or if there's been headway in finding a solution. I will report here when I hear something.

[SydneyhSmith]

Adding a link to a comment made in another issue in case it might be helpful for users here:
#2014 (comment)

[EdCallahan]

@rjmholt @richardm1 @TylerLeonhardt @tastrsks

Avecto/BeyondTrust got back to me yesterday. Creating a workstyle that allows code.exe and all subprocesses to execute, either passive or with added admin rights, typically gets my powershell server to start within two minutes. Avecto experimented with our policy set and found if we moved that workstyle farther up to be processed before some other workstyles, that delay was down to 20 seconds.

This solution seems specific to our policy set, and to me does not resolve the problem. I've pushed back on Avecto for a better solution.

Powershell 5.1 x86 and Powershell 7 seem unaffected. But in a corporate environment where developers are afflicted with BeyondTrust/Avecto Privilege Guard, I'm not sure VS Code is a viable platform for 5.1 x64 development. Getting the corporate security team to experiment with the Avecto policies to get things running, let alone get BeyondTrust to dig into them, is beyond most developers.

[SydneyhSmith]

Thanks @EdCallahan that is really helpful information, I think in order for us to move forward we likely need to better understand BeyondTrust/Avecto....we'd be happy to follow up with your support contacts there...if you are interested in following up with us send an email to [email protected] and we will figure out what the next steps are....thanks!

[EdCallahan]

BeyondTrust recommended I update to version 5.6.126, and similarly to what was reported at #2014 (comment)] I got dramatically better results. I did continue to have sporadic lockups starting PowerShell 5.1 x64 servers, and sometimes x86 as well. However, reordering my workstyles combined with upgrading seems to have fixed things. Although I haven't worked under this configuration for long.

@SydneyhSmith, I passed on that email address to BeyondTrust.

[arcotek-ltd]

I've spoken with one of my company's Avecto SMEs and apparently there is a memory leak, that's been present in the client since November, so we can't upgrade at the moment.

I've tried setting the extension to x86, with no luck. Is there anything from VSCode / extension side that we can do, whilst we wait for Avecto?

Thanks.

[portanoo]

I have the same problem with Powershell language service on VSCode.
In fact I detect that on my SharePoint Server, If I remove the "add-pssnapin Microsoft.sharePoint.Powershell" from profile.ps1, the Powershell Language service can start.
Does it mean it's not possible to mix add-pssnapin in profile and use powershell language service in the same time ?
We need the add-pssnapin in profile to use Custom Powershell and load automatically Microsoft.sharePoint.Powershell add-in when opening Powershell console

[tsunami28]

I had a same issue (Avecto on business laptop) and last night found a solution.
I installed latest PS7 and in VSC under "Configure PowerShell language based settings" I changed the path to use pwsh:
"terminal.integrated.shell.windows": "C:\Program Files\PowerShell\7\pwsh.exe"
It is a bit leggy but it works.

[JoeBrunsTR]

Visual Studio Code v1.54.1 64-bit

3/6/2021 4:47:38 PM [ERROR] - Could not start language service:
3/6/2021 4:47:38 PM [ERROR] - Error: Connection to server got closed. Server will not be restarted.

Same thing has happened again.

[kihtov23]

Same for me

[ZonderP]

And for me
Edit:
For me it started after Visual Studio 2019 update to 16.9.0 and Visual Code automatic update to 1.54.1 and after the update of the Powershell Extension to 2021.2.2 (I think the update was from v2021.2.1-preview).
So not really an idea what caused this issue.
The issue started yesterday and also continued today after a reboot of my machine.

For what it's worth and maybe it can help narrowing down the issue:
I somehow managed to get rid of it by executing the following command:

Import-Module $HOME.vscode\extensions\ms-vscode.powershell*\modules\PowerShellEditorServices\PowerShellEditorServices.psd1

which I found here:
https://community.idera.com/database-tools/powershell/powertips/b/tips/posts/fixing-vscode-powershell-issues-part-1

I use Powershell 5.1 and 7.1.2 side by side and applied the above for both versions and both elevated and non elevated.
I didn't get a prompt at all, but after applying it, the error was gone.

[AkosBatorfi]

I've got this same error message. It looks like it's not liking PowerShell 5.1 somehow.

[andyleejordan]

@JoeBrunsTR @kihtov23 @ZonderP @AkosBatorfi

Thanks for your reports. Please note that "The Language Service Could not be started" is a generic message indicating the extension could not communicate with the language server. This particular GitHub issue was closed last year as it was a different bug report, and the issue with the Visual Studio Code 1.54 update is actually #3227. Please use caution in commenting on old, closed issues; most likely you need to find an existing open issue, or open a new issue. The good news is that the issue with VS Code has been resolved microsoft/vscode#117649 and will be in the next VS Code release.

[Mike-Remoni]

I have recently been experiencing the same thing. I am a daily, professional user of VS code and the PS extension, and since monday last week (10 days ago) it stopped working. I have tried reinstalling both VS code and the PS extension, and downdraded the extension to a previous version to no avail.

However, whenright-klicking on the PS status in the bottom right corner and selecting "Restart current session", it starts up nicely in PS 5.1.

[andyleejordan]

@h4tt3n Please see the comment above yours, thanks! #2526 (comment)