Language server startup failed: PowerShellEditorServices missing.
See original GitHub issueSystem Details
- 
Operating system name and version:
Ubuntu 16.04 - 
VS Code version:
1.12.2 - 
PowerShell extension version: 1.1.0
 - 
Output from
$PSVersionTable: Name Value 
PSVersion                      6.0.0-alpha
PSEdition                      Core
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
BuildVersion                   3.0.0.0
GitCommitId                    v6.0.0-alpha.14
CLRVersion
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
Copy / paste the below commands into the PowerShell Integrated Terminal, and paste the output here
code -v
1.12.2
19222cdc84ce72202478ba1cec5cb557b71163de
$pseditor.EditorServicesVersion
Nothing
code --list-extensions --show-versions
austin.code-gnu-global@0.2.2
donjayamanne.githistory@0.2.0
donjayamanne.javadebugger@0.1.0
donjayamanne.python@0.6.4
goessner.mdmath@1.2.9
lukehoban.Go@0.6.61
mathiasfrohlich.latexcompile@0.7.0
ms-vscode.cpptools@0.11.1
ms-vscode.csharp@1.9.0
ms-vscode.latex@0.1.3
ms-vscode.PowerShell@1.1.0
redhat.java@0.4.0
streetsidesoftware.code-spell-checker@1.1.0
tomoki1207.pdf@0.2.0
$PSVersionTable
Name                           Value                                                                                                                                                                               
----                           -----                                                                                                                                                                               
PSVersion                      6.0.0-alpha                                                                                                                                                                         
PSEdition                      Core                                                                                                                                                                                
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                                                                                                             
BuildVersion                   3.0.0.0                                                                                                                                                                             
GitCommitId                    v6.0.0-alpha.14                                                                                                                                                                     
CLRVersion                                                                                                                                                                                                         
WSManStackVersion              3.0                                                                                                                                                                                 
PSRemotingProtocolVersion      2.3                                                                                                                                                                                 
SerializationVersion           1.1.0.1 
Issue Description
When I start up VSCode the Powershell Language Server fails to load. There is an error message in the 'PowerShell Integrated Terminal" but it is erased before I can read it. I took a screenshot of this error (after many attempts) and attached in zip file. There is no useful error message in the logs, maybe this should be fixed (another bug report?).
Attached Logs
Issue Analytics
- State:
 - Created 6 years ago
 - Comments:12 (1 by maintainers)
 

Top Related StackOverflow Question
Ahh! Sorry guys, I just realized what the problem is. You both need to upgrade to PowerShell 6.0.0-alpha.18 or higher. I’d recommend 6.0.0-beta.1. Once you install that version of PowerShell everything should start working.
Thanks for the info @AJDulk can you open a new issue (easier for us, to track) and attach the logs so we can get a better idea of what’s going on?