AzureRM Tools extension prevents PowerShell extension from loading

[brandubh]

System Details

• Operating system name and version: Windows 10 (1703) 15063.540
• VS Code version: 1.16.0-insider
• PowerShell extension version: 1.4.1
• Output from $PSVersionTable:
  Name Value

---

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

Copy / paste the following commands into the PowerShell Integrated Console, and paste the output here:

 code -v
code : The term 'code' 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:1
+ code -v
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (code:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS> $pseditor.EditorServicesVersion
PS> code --list-extensions --show-versions
code : The term 'code' 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:1
+ code --list-extensions --show-versions
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (code:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.15063.502
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.502
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
[logs.zip](https://github.com/PowerShell/vscode-powershell/files/1270431/logs.zip)

SerializationVersion           1.1.0.1

Issue Description

Basically the extension after the latest insider updates doesn't work anymore (no F8, no auto complete, and so on), in the output window I can read:
[8:58:45] Language server starting...
[8:58:45] Language server startup failed.

Attached Logs

I attach the logs, but they're empty

[brandubh]

Still present with extension 1.4.2

2017-9-8 12:09:12 [NORMAL] - Visual Studio Code v1.17.0-insider 64-bit
2017-9-8 12:09:12 [NORMAL] - PowerShell Extension v1.4.2
2017-9-8 12:09:12 [NORMAL] - Operating System: Windows 64-bit

2017-9-8 12:09:12 [NORMAL] - Language server starting...
2017-9-8 12:09:12 [NORMAL] - Language server startup failed.

[reg-c]

Hi, I am having the same problem here:

Windows 10 (1703) 15063.540

$PSVersionTable:
PSVersion 5.1.15063.502
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.502
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

2017-9-8 14:03:35 [NORMAL] - Visual Studio Code v1.16.0 64-bit
2017-9-8 14:03:35 [NORMAL] - PowerShell Extension v1.4.2
2017-9-8 14:03:35 [NORMAL] - Operating System: Windows 64-bit

2017-9-8 14:03:35 [NORMAL] - Language server starting...
2017-9-8 14:03:35 [NORMAL] - Language server startup failed.

[MarvTheRobot]

Me too:

I'd upload the logs, but they are empty. I've changed the logging level to Verbose, still empty.

Name Value

---

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

2017-9-8 09:58:50 [NORMAL] - Visual Studio Code v1.17.0-insider 64-bit
2017-9-8 09:58:50 [NORMAL] - PowerShell Extension v1.4.2
2017-9-8 09:58:50 [NORMAL] - Operating System: Windows 64-bit

2017-9-8 09:58:50 [NORMAL] - Language server starting...
2017-9-8 09:58:50 [NORMAL] - Language server startup failed.
2017-9-8 12:07:00 [NORMAL] -

Shutting down language client...
2017-9-8 12:09:13 [NORMAL] -

Shutting down language client...
2017-9-8 12:09:40 [NORMAL] -

Shutting down language client...

[daviwil]

Thanks all! @Jaykul also reported this issue to me recently but I haven't yet figured out why it's happening. The logs you've all pasted are a good starting point for investigation so I'll take a look today.

[daviwil]

By the way, does this problem occur for you when using VS Code Stable 1.16.0 which was released yesterday, or only in the latest Insiders builds?

[MarvTheRobot]

For me it happens on both Stable and Insiders. Fully removed extension and re-installed, same issue. Just fails to load Editor Services and doesn't seem to create any log files.

[daviwil]

Damn, not sure what happened there. Seems like it's not launching PowerShell at all. Can you try adding this setting to see if it makes any difference?

"powershell.powerShellExePath": "C:/Windows/System32/WindowsPowerShell/v1.0/powershell.exe"

[MarvTheRobot]

@daviwil , thats seems to have worked for me. The default is just "" (I can't remember if it was that normally. Adding the direct path has put everything back to how it was prior to 1.4.2

[daviwil]

Thanks a lot for confirming! I'll see if I can get a fix out for that today.

[reg-c]

@daviwil adding the powerShellExePath doesn't work for me in the 1.16.0 build, however the extension works with the latest insider build without any changes

[richardrobberse]

@daviwil adding the powerShellExePath didn't work for me either, I'm on the 1.16 build.

[aydeisen]

@daviwil ditto for me. I'm running VSCode 1.16 on Windows 10 1703, and adding powershell.powerShellExePath. I was hoping it was from switching VSCode from x86 to x64, but neither enabling the x86 PowerShell nor switching back to 32-bit VSCode resolved the issue