Cannot attach to process on Windows 11 due to missing wmic.exe (using extension bisect and --disable-extensions makes no difference) #244139
Description
Does this issue occur when all extensions are disabled?: Yes/No
YES
- VS Code Version:
Version: 1.98.2 (user setup)
Commit: ddc367e
Date: 2025-03-12T13:32:45.399Z
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Windows_NT x64 10.0.26100
- OS Version:
Edition Windows 11 Home
Version 24H2
Installed on 07/02/2025
OS build 26100.3476
Experience Windows Feature Experience Pack 1000.26100.54.0
Steps to Reproduce:
- Launch VS code using
code --disable-extensions(or use extension bisect) - Add "Attach by Process ID" & attempt to attach to process
What I see:
When i press F5 or click play for "Attach by Process ID", the process picker momentarily appears then I get an error in VSCode...
Extra Info
This is the configuration I added (I used the "Add configuration button"):
{
"name": "Attach by Process ID",
"processId": "${command:PickProcess}",
"request": "attach",
"skipFiles": [
"<node_internals>/**"
],
"type": "node"
},
In an attempt to understand what is trying to launch wmic I disabled all extensions but the issue persisted.
To see what is trying to run wmic, I copied nodepad.exe to c:\Windows\System32\wbem\wmic.exe and used process explorer to see if it could help me identify what causes this but it is unclear.
Notes
It seems windows has depreciated wmic.exe and since latest update, it appears to have been removed (not 100% sure on timing or accuracy - this laptop is only 1m old and this is the first time, on this laptop, that I have used "Attach by Process ID")
