Attach to Node Process not working with PowerShell on Windows 10

[tsalinger]

Testing #46582

Windows 10, NodeJS: v8.9.4

1. Create a simple script like:

setInterval(() => {
    console.log('a');
}, 500)

2. Launch the script in PowerShell: node --inspect=1500 foo.js
3. Use the 'Attach to Node Process' command or use the following launch.json:

    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
       {
        "type": "node",
        "request": "attach",
        "name": "Attach to Process via pid or port",
        "processId": "${command:PickProcess}"
    }
    ]
}

Expected: Picker shows my process
Actual: Picker shows "There are no entries to pick from"

Note that it works with fine with cmd. This is a Powershell specific issue.

[weinand]

problem is: PowerShell launches programs with a full path whereas command prompt uses a relative path:

PowerShell:

Command.exe:

[weinand]

No, the analysis from above is wrong. I'm handling the full path correctly.

The issue is in fact another duplicate of #46672

[tsalinger]

Tested on latest insiders and works fine.

[weinand]

@tsalinger thanks!

Till confirmed (and showed me) that both the "Attach Process Picker" and the "Auto Attach" work for him on Windows.

@sbatten @RMacfarlane so for some (in ZRH) it seems to work on Windows. What is difference in Redmond?