Skip to content

deprecated wmic still used in debugpy #1117

Description

I recently updated my Windows-System to Win11 25H2 Bild 26200. From this on I cannot attach to any process via debugpy any more. I have my launch.json as this:

{
  "version": "0.2.0",
  "configurations": [
    {
        "name": "Python Debugger: Attach using Process Id",
        "type": "debugpy",
        "request": "attach",
        "processId": "${command:pickProcess}",
        "justMyCode": false
    }
  ]
}

When starting debugging for that configuration, nothing happens, despite the debugging-toolbar changing and hanging indefinitly:

Image

However no log is written to the console. Usually I get the process-picker and once I chose one process to attach to I get this in my debug-console:

Attaching to PID: 5096 (elapsed: 1.00s).
Attaching to PID: 5096 (elapsed: 2.00s).
Attaching to PID: 5096 (elapsed: 3.00s).
Attaching to PID: 5096 (elapsed: 4.00s).
Attaching to PID: 5096 (elapsed: 5.00s).

After the update the process-picker no longer is displayed. Using hard-coded PID in my launch.json (like 5096 in the example above) works, however.

I checked exthost.log and found this, though:

2026-09-30 10:36:07.925 [error] Error: spawn wmic ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:287:19)
at onErrorNT (node:internal/child_process:525:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

Seems like WMIC is causing the issue, which isn't available any more.

I am using VS Code 1.139.1, Win11 25H2 26200

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    triage-neededNeeds assignment to the proper sub-team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions