EASteamProxy.exe breaks VScode "command:pickProcess"

Environment

• OS and version: Windows 11 Pro
• VS Code: 1.88.1 (user setup)
• C/C++ extension: v1.19.9

Bug Summary and Steps to Reproduce

Steps to Reproduce:

1. Open any EA game like Titanfall 2 from Steam (game must also use EA app proxy), make sure you have EASteamProxy.exe in task manager.
2. Create launch.js file that should attach a debugger to process you can choose

{
    // 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": "(Windows) Attach",
            "type": "cppvsdbg",
            "request": "attach",
            "processId":"${command:pickProcess}"
        }

    ]
}

3. Execute lauch.js
   

Debugger Configurations

{
    // 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": "(Windows) Attach",
            "type": "cppvsdbg",
            "request": "attach",
            "processId":"${command:pickProcess}"
        }

    ]
}

Debugger Logs

N/A

Other Extensions

Only C/C++ extension

Additional Information

PS:
It could be fixed if VS code will rather used this command:
wmic process get name,processid /format:list
instead of that, to get process id
wmic process get name,processid,commandline /format:list

If you close EASteamProxy.exe this error disappeares

Start by reproducing the Windows attach flow with EASteamProxy.exe running and compare the two WMIC process queries shown in the issue. Trace the implementation behind ${command:pickProcess}; done means the process picker can attach successfully while EASteamProxy.exe is present, without breaking the normal process list.