[Alexander Gottwald (ago1024)]

The PR replaces the call to wmic.exe with a call to powershell Get-CimInstance Win32_process.

The output of the script is similar to the old wmic output. CreationDate was omited because it's not used anywhere and the old parsing logic to parse the date does not work with the input from the script.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Alexander Gottwald (ago1024)]

@microsoft-github-policy-service agree

[wenyt (wenytang-ms)]

Alexander Gottwald (@ago1024) Thanks for submitting the PR! I left two inline suggestions for the PowerShell invocation and output encoding. Please take a look when you have a chance.

[Copilot]

🟢 Approval recommended

No active review issues were identified for the switch from WMIC to PowerShell-based Windows process discovery.

No open issues 🎉

What changed in this PR

Replaces Windows process discovery through wmic.exe with PowerShell’s Get-CimInstance Win32_Process, preserving the process information used by the debugger.

Changes:

• Removes the unused creation-date field from Windows process parsing.
• Handles UTF-8 output, restricted PowerShell language modes, and process records split across output chunks.
• Adds tests for PowerShell invocation, Unicode handling, encoding restrictions, and failure reporting.

File	Description
test/​processTree.test.ts	Adds mocked discovery tests and Windows-only PowerShell script tests.
src/​processTree.ts	Switches to PowerShell, enforces UTF-8 output, and corrects chunked-line parsing.

_{Review effort: Balanced}