PowerShell extension (and Integrated Console) never starts

[dtbiedrzycki]

System Details

System Details Output

### VSCode version: 1.30.1 dea8705087adb1b5e5ae1d9123278e178656186a x64

### VSCode extensions:
christian-kohler.npm-intellisense@1.3.0
christian-kohler.path-intellisense@1.4.2
CoenraadS.bracket-pair-colorizer@1.0.61
DavidAnson.vscode-markdownlint@0.22.0
dbaeumer.vscode-eslint@1.7.2
eg2.vscode-npm-script@0.3.5
jasonnutter.search-node-modules@1.3.0
jebbs.plantuml@2.10.1
ms-mssql.mssql@1.4.0
ms-vscode.csharp@1.17.1
ms-vscode.PowerShell@1.10.2
rebornix.ruby@0.21.0
waderyan.nodejs-extension-pack@0.1.9
xabikos.JavaScriptSnippets@1.7.2
yzhang.markdown-all-in-one@1.8.0


### 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: