PowerShell extension (and Integrated Console) never starts

[dtbiedrzycki]

System Details

System Details Output

### VSCode version: 1.30.1 dea8705087adb1b5e5ae1d9123278e178656186a x64

### VSCode extensions:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]


### PSES version:

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.16299.666
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.666
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

All right click console options fail (i.e. Run Selection).

Expected Behaviour

If I highlight code and press F8 (or right click and Run Selection), I expect the command(s) to be run in the terminal window.

Actual Behaviour

A pop-up appears stating <ConsoleFeature>: Unable to instantiate; language client undefined.

Attached Logs

There are no logs in the extension logs folder (even with logs set to Diagnostic) and the lines below are the only output in the PowerShell Extension console:

12/26/2018 10:34:57 AM [NORMAL] - Visual Studio Code v1.30.1 64-bit
12/26/2018 10:34:57 AM [NORMAL] - PowerShell Extension v1.10.2
12/26/2018 10:34:57 AM [NORMAL] - Operating System: Windows 64-bit
12/26/2018 10:35:10 AM [ERROR] - <ConsoleFeature>: Unable to instantiate; language client undefined.

[TylerLeonhardt]

Can you confirm that the PowerShell Integrated Console is open?

[dtbiedrzycki]

I don't believe it is. When I try to open it via the command palette, nothing happens either.

[SydneyhSmith]

@dtbiedrzycki it would be helpful to know what command you were trying to run when you reached this error, a screenshot of your VSCode environment when this occurred would be even better, thanks!

[SydneyhSmith]

@dtbiedrzycki this should be fixed by a recent PR in #1690

[eduardcloud]

Here an approaching issue trying to open new Terminal after default crashes:
1/16/2019 5:38:54 PM [ERROR] - The language service could not be started: 1/16/2019 5:38:54 PM [ERROR] - Timed out waiting for session file to appear. 1/16/2019 5:39:33 PM [ERROR] - <ConsoleFeature>: Unable to instantiate; language client undefined.

[eduardcloud]

Here an approaching issue trying to open new Terminal after default crashes:
1/16/2019 5:38:54 PM [ERROR] - The language service could not be started: 1/16/2019 5:38:54 PM [ERROR] - Timed out waiting for session file to appear. 1/16/2019 5:39:33 PM [ERROR] - <ConsoleFeature>: Unable to instantiate; language client undefined.

Ok, I solved this changing the loglevel on VSCode settings from Warning to Normal. Maybe a Powershell modules update broke it?
Thanks

[SydneyhSmith]

@dtbiedrzycki Closing as the update to the extension that should fix this is out, will re-open if this issue is still happening!

[dtbiedrzycki]

Hey @SydneyhSmith, my apologies for the extremely long delay. I've updated the PowerShell extension to version 1.11.0 and my problem remains. See the attached gif showing the issue:

[IzzyRise]

I had this exactly same issue. Disabling, enabling then reload solved it for me.

[SydneyhSmith]

Thanks for reporting this, it could be from being on a restricted system, is your environment restricted in any way (group policy etc.), if so this could be the cause--try this https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/using-vscode?view=powershell-6#installing-the-powershell-extension-on-restricted-systems and let us know if that helps at all.

[dtbiedrzycki]

I had this exactly same issue. Disabling, enabling then reload solved it for me.

This did not work for me :(.

[dtbiedrzycki]

Thanks for reporting this, it could be from being on a restricted system, is your environment restricted in any way (group policy etc.), if so this could be the cause--try this https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/using-vscode?view=powershell-6#installing-the-powershell-extension-on-restricted-systems and let us know if that helps at all.

I ran the command provided in the link, was not prompted, and the command executed successfully. I also tried running VS Code as an administrator and still get the same behavior.

[dtbiedrzycki]

I've also tried uninstalling and re-installing VS Code and get the same result as well.

[SydneyhSmith]

@dtbiedrzycki we are trying to diagnose this issue, would you mind looking in the logs file, they should be at ~/.VSCode/extensions/ms-vscode.powershell-1.11.0/logs ? Thanks!

[dtbiedrzycki]

The directory is empty :(
I also double checked and I have the "powershell.developer.editorServicesLogLevel" set to "Diagnostic".

[SydneyhSmith]

Assuming this is resolved for everyone since there has been no activity since my last check-in, please let us know if this is not the case, thanks!

[pgemme]

I was having this issue and reverting to 2019.5.0 fixed it for me.

[ActionExpress50]

I was having this issue and reverting to 2019.5.0 fixed it for me.

Even running VS Code under SYSTEM account does not help.

+1. Need a fix.

[SydneyhSmith]

@ActionExpress50 thanks for commenting on this issue, it would be great if you could open a new issue in our repo with logs/detailed explanation of the issue you are hitting so we can diagnose what is going on since the issue described that the root of the thread seems to have been resolved--thanks!

[mabead]

I installed PowerShell 7 from here and it fixed the problem for me.

[rjmholt]

I installed PowerShell 7 from here and it fixed the problem for me.

Yeah, this likely means that the issue is what I think it is in #2538. Resolving the right dependency in .NET Core is much much easier, so we have a well-defined solution that works for PS 6 and 7.

[js82jumper]

I also ran into this on a completely clean install and can confirm that installing PowerShell 7 fixed mine as well.

[steveaf]

I had the same "language service could not be started" issue in VS Code. I have both PowerShell and PowerShell Core 7 on Windows. In both with elevated PowerShell commands I set-executionpolicy unrestrected and no longer have an issue.

[clouditgirl]

I had this exactly same issue. Disabling, enabling then reload solved it for me.

This did not work for me :(.

didn't work for me either.

[Meron-cloud]

Hello
I have the same issue

[SydneyhSmith]

@Meron-cloud thanks--looks like you may be hitting a new issue could you please open a new issue with the information requested in the template it would be really helpful if you could also attach the logs--instructions for how to do that are here