Powershell: Initialization Error

[cmcknz77]

logs.zip

System Details

• Operating system name and version: Windows 10 - x64 - 10.0.14393
• VS Code version: 1.10.2
• PowerShell extension version: 0.10.1
• Output from $PSVersionTable:
  Name Value

---

PSVersion 5.1.14393.953
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.953
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Issue Description

When I open a file with a recognised 'Powershell' extension (.ps1,.psm1,*.psd1 etc) or having typed in some script I tell 'Code' that the language is 'PowerShell' instead of plain text, I get a notice that says 'Initialization Error' in the bottom right hand corner.
When I click on it I get an error in the Error bar that says "Error: Could not start language service:"
And if I click on the logs I see the following:

[0:2:23] Language server starting...
powershell.exe started --
pid: 928
exe: C:\WINDOWS\Sysnative\WindowsPowerShell\v1.0\powershell.exe
args: C:\Users\myuser\.vscode\extensions\ms-vscode.PowerShell-0.10.1\scripts\Start-EditorServices.ps1 -EditorServicesVersion '0.10.1' -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '0.10.1' -BundledModulesPath 'C:\Users\myuser\.vscode\extensions\ms-vscode.PowerShell-0.10.1\modules' -EnableConsoleRepl -LogLevel 'Verbose' -LogPath 'C:\Users\myuser\.vscode\extensions\ms-vscode.PowerShell-0.10.1\logs\1490227343-bdec66a5-f1e8-4d56-9ce5-5e057642a56f1490227309017\EditorServices.log' -SessionDetailsPath 'C:\Users\myuser\.vscode\extensions\ms-vscode.PowerShell-0.10.1\sessions\PSES-VSCode-10944'

powershell.exe terminated or terminal UI was closed

[0:3:23] Language server startup failed.
Could not start language service:
Timed out waiting for session file to appear.

Now... I'm in a Domain environment where our Security Policy forced down from 'on high' by Group Policy is that we're in an allsigned environment. I have tried Code and the Powershell Extension on a number of machines now and I always get the same experience.

Incidentally, it appears that the module files:
modules\Plaster\Templates\NewPowerShellManifestModule\Module.psm1
modules\Plaster\Templates\NewPowerShellManifestModule\test\Module.T.ps1
are not signed - I don't know if this is related.

Attached Logs

logs.zip

[rkeithhill]

Looks like we might also have a logging bug where we are not appending a \ between the home dir and the .vscode dir e.g. C:\Users\myuser.vscode should really be C:\Users\myuser\.vscode

[cmcknz77]

Oooop. No Keith, that's my bad - I manually edited that output to obfuscate my username in this publicly visible post...

[cmcknz77]

New version of VSCode installed - March 2017 (version 1.11)
Powershell Extension upgraded to 0.12.2
Problem remains as described above - new logs attached.

System Details
Operating system name and version: Windows 10 - x64 - 10.0.14393
VS Code version: 1.11.0
PowerShell extension version: 0.12.2
Output from $PSVersionTable:
PSVersion 5.1.14393.953
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.953
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

logs-1.11.0.zip

[cmcknz77]

New version of VSCode installed - May 2017 (version 1.12.2)
Powershell Extension upgraded to 1.1.0
Problem remains as described above - new logs attached.
System Details
Operating system name and version: Windows 10 - x64 - 10.0.14393
VS Code version: 1.12.2
PowerShell extension version: 1.1.0
Output from $PSVersionTable:
PSVersion 5.1.14393.953
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.953
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

New logs attached
logs.zip

[daviwil]

Thanks @cmcknz77! There's definitely an exception happening during initialization that we're not capturing in a way that you can observe. Can you try these steps:

1. Open the file C:\Users\cmckenzie\.vscode\extensions\ms-vscode.powershell-1.1.0\scripts\Start-EditorServices.ps1 in the editor
2. Replace its contents entirely with the contents of this script: https://raw.githubusercontent.com/daviwil/vscode-powershell/eb8b2d31d2fafe5e2e09cdfed7f811c74d9d1bcf/scripts/Start-EditorServices.ps1
3. Restart VS Code and open a PowerShell script.
4. Copy the error that gets printed to the PowerShell Integrated Console when it starts up

Hopefully an error will be printed so that we can see what exception you're getting. This improvement to the Start-EditorServices script will be included with the next extension update.

Thanks @daviwil . I had same issue with VScode on linux. That did the trick for me!

[daviwil]

@Ghoshnik interesting, this script shouldn't have fixed anything, it just prints out more diagnostic information. Can you tell me what version of PowerShell Core you're using on Linux?

Weird.

Name Value

---

PSVersion 6.0.0-beta
PSEdition Core
BuildVersion 3.0.0.0

[daviwil]

Thanks! That's the right version to use for now. What was happening before, the Integrated Console just wouldn't start? I'll have to look at my script change a little more closely to see if there's an explanation for why it might have resolved that.