Attach using Process ID, process picker not working

[monmartymon]

In the past, when I have attempted to debug by attaching to a process, the "process picker" has presented me with a list of running processes to attach to.

This no longer happens - in fact, nothing appears to happen.

A workaround has been to hardcode the process ID, but this is undesirable in the long-term.

My launch.json is:

{
// 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": [
{
"name": "Python Debugger: Attach using Process Id",
"type": "debugpy",
"request": "attach",
"processId": "${command:pickProcess}"
},
{
"name": "Python Debugger: Current File",
"type": "debugpy",
"request": "launch",
"program": "${file}",
"console": "integratedTerminal"
}
]
}

[ZA139]

You might be having the same issue as #744, which could be due to a missing WMIC.

Possible solutions:

• Install the WMIC component on your PC.
• Use a pre-fixed version: Alternatively, you can use the version from my fork, which already includes the fix proposed in PR Due to wmic has been deprecated. Replace wmic command in attach process with powershell command. #858. You can find it here: ZA139 / vscode-python-debugger (fixed fork)

[eleanorjboyd]

Thanks for the comment @ZA139 - did that work @monmartymon?

[monmartymon]

Thanks for the comment @ZA139 - did that work @monmartymon?

My organisation is quite restrictive on what I can install, so have not tried this. I was trying to work out what I could be doing locally to fix this, but could not figure it out.

[ZA139]

Thanks for the comment @ZA139 - did that work @monmartymon?

My organisation is quite restrictive on what I can install, so have not tried this. I was trying to work out what I could be doing locally to fix this, but could not figure it out.

There is a simple way to verify wmic has been installed or not by the follow steps:

1. Open CMD
2. Type the wmic command like: "wmic"

If there are "not found" message,it's means same issue with #744 . You can solve it with two ways in my pervious comment.
BTW, WMIC is pretty safe component which been microsoft windows preinstalled component in the old days. Install WMIC is the first solusion that I recommanded.

[monmartymon]

Thanks for the comment @ZA139 - did that work @monmartymon?

My organisation is quite restrictive on what I can install, so have not tried this. I was trying to work out what I could be doing locally to fix this, but could not figure it out.

There is a simple way to verify wmic has been installed or not by the follow steps:

1. Open CMD
2. Type the wmic command like: "wmic"

If there are "not found" message,it's means same issue with #744 . You can solve it with two ways in my pervious comment. BTW, WMIC is pretty safe component which been microsoft windows preinstalled component in the old days. Install WMIC is the first solusion that I recommanded.

@ZA139 Firstly, I forgot to thank you for your initial reply to my query and for your attention to this matter - thank you! I can confirm that I don't have wmic. I will look into solving it