VSCODE- Insiders: Timed out waiting for the PowerShell extension to start

[iricigor]

System Details

• Operating system name and version: Windows 10
• VS Code version: 1.18.0 Insiders (commit date 2017-10-06T05:26:16.770Z)
• PowerShell extension version: 1.4.3
• Output from $PSVersionTable: 5.1.15063.632

Issue Description

Error: Timed out waiting for the PowerShell extension to start.

This seems to be specific for latest 1.18 insiders build. All works normally on 1.17 public version.
I tried multiple computers and its the same behaviour.
PowerShell extension is timing out when pressing F5, or trying to start any script.

Steps to reproduce

• On clean Windows 10 machine install VS Code Insiders 1.18.0.
• Install PowerShell extension v.1.4.3
• Wirite simple script (something as Write-Host 1)
• Press F5

Expected behaviour is to diplay 1 in console. But, nothing actually happens. After some time, time out error will appear.

Attached Logs

logs.zip

[rkeithhill]

If you set script analysis to false (in your settings):

"powershell.scriptAnalysis.enable": false,

and reload VSCode Insiders, does it still timeout?

[iricigor]

Just tried it, and yes, still the same behavior.

[kborowinski]

I have the same behavior in VS Code 1.18.0. The PowerShell extension does not start.

[iricigor]

Build from 10-10-2017 has the same issue.

[jamestupper]

I'm seeing the same issue.

• Visual Studio Code version: 1.18.0-insider (Date 2017-10-13T08:55:13.465Z)
• PowerShell extension version: v1.4.3

[DarkLite1]

Insiders build from 16/10/2017 with extension 1.4.3 has the same issue.

Settings on user level:

{
    "editor.formatOnType": true,
    "editor.formatOnPaste": true,
    "editor.wordWrap": "on",
    "terminal.integrated.shell.windows": "C:\\Windows\\sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
    "workbench.editor.enablePreview":false,
    "window.zoomLevel": 0,
    "workbench.colorTheme": "Default High Contrast"
    // "powershell.developer.editorServicesLogLevel": "Verbose"
}

Launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "PowerShell",
            "request": "launch",
            "name": "PowerShell Launch Current File",
            "script": "${file}",
            "args": [],
            "cwd": "${file}"
        },
        {
            "type": "PowerShell",
            "request": "launch",
            "name": "PowerShell Launch Current File in Temporary Console",
            "script": "${file}",
            "args": [],
            "cwd": "${file}",
            "createTemporaryIntegratedConsole": true
        },
        {
            "type": "PowerShell",
            "request": "launch",
            "name": "PowerShell Launch Current File w/Args Prompt",
            "script": "${file}",
            "args": [
                "${command:SpecifyScriptArgs}"
            ],
            "cwd": "${file}"
        },
        {
            "type": "PowerShell",
            "request": "attach",
            "name": "PowerShell Attach to Host Process",
            "processId": "${command:PickPSHostProcess}",
            "runspaceId": 1
        },
        {
            "type": "PowerShell",
            "request": "launch",
            "name": "PowerShell Interactive Session",
            "cwd": "${workspaceRoot}"
        }
    ]
}

I don't think this deserves a smiley ;)

[iricigor]

This issue was reported in VS Code repo also, but as per explanation there, it is a PowerShell issue: "VSCode has deprecated some API that Powershell is using. Powershell needs to update to this."

[rkeithhill]

I plan to look into this tonight.

[rkeithhill]

Been looking at this for several hours. In the past, debug protocol changes have been minimal and simple to implement. However, the required changes for this change are bit more extensive than I was hoping they would be. It's going to take a little while. I'm hopeful we'll get this implemented before VSCode 1.18 drops.

[DarkLite1]

#36268

[rkeithhill]

Some progress tonight. Finally got to the point where the PowerShell debugger is started. No breakpoints are being hit but this is better than last night. :-)

[DarkLite1]

Awesome Keith, one step at a time. The most important thing is, it's not broken in the stable version. Only for us, the beta guinea pigs 😃

[rkeithhill]

Woohoo. Basic debugging is working. Now just need to test the various (and numerous) debug configurations.

[carlocardella]

Great news, thanks :-)

[rkeithhill]

PR for the fix has been submitted - pending review.

[rkeithhill]

BTW there is still an issue with "Attach to process" debugging. Separate issue that has me scratching my head. Might need @daviwil help on that one.

[kborowinski]

@rkeithhill @daviwil: I second that. It would be super great if you guys could fix "attach to process" bug. It's really making my d2d work hard.

[rkeithhill]

The original issue should be fixed with the 1.5.0 release. We are tracking the attach to process issue in the PSES repo - PowerShell/PowerShellEditorServices#551

[gdwnet]

I get this on the v1.17 release as well, it seems very hit and miss.

[Bummibaer]

I'm using V1.19.3 and Windows 7 Professional.
When I run VS as Admin, I get the same error.
It seems, when I resume after some minutes.

[rkeithhill]

Can you give this a try and let me know how it goes? #1048 (comment)