"autoAttachChildProcesses": true doesn't work in Windows with "type": "extensionHost"

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Create a new VS Code “Extension - TS” project.
2. Modify its “launch.json” to include "autoAttachChildProcesses": true.
3. Add launching a long running node child process via child_process to the extension.
4. The child process won’t be debugged. In fact, any node child process started by the VS Code Extension Development Host won’t be debugged.

Such process are debugged correctly when I do the same in macOS 12.5.1, but doesn’t work in either Windows 10 or 11.

Log File

vscode-debugadapter-e946278c.json.gz

VS Code Version: 1.70.2

Additional context We are using this flag to be able to debug a node server that we spawn from our extension, this also applies to LSP, debug adapters that are implemented in node so that you are able to easily debug them.

[segevfiner]

I’ll try to create one once I have access to a PC where I’m sure this reproduces.

[connor4312]

Indeed. But there’s no a whole lot we can do about that, as far as I know.