0xc0000142 error on powershell (running "cmd.exe /b /c start /b /min powershell.exe" inside WSL)

[emdns]

Version

10.0.22000.1455

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.15.79.1

Distro Version

Debian and Ubuntu

Other Software

Powershell 5.1.22000.1335

Repro Steps

Launch wsl
Inside wsl bash shell type the command:
cmd.exe /b /c start /b /min powershell.exe

Expected Behavior

A powershell running

Actual Behavior

Powershell either silently fails to run or fails to run with the following popup:

Diagnostic Logs

WslLogs-2023-01-26_11-27-25.zip

[emdns]

@DHowett
(for vis)

[DHowett]

@emdns Thanks for the tag. I think that this was fixed by a recent change we've made in Windows and will need some time to propagate out to all of our API consumers.

The specific issue:

cmd.exe is launched in a console session. cmd.exe /c start /b xyz launches application xyz inside the same console session and then immediately exits.

This means that depending on how quickly xyz starts up, it might not have a console any more. Because the session leader, cmd, just exited... which took down the console. :)

[emdns]

@DHowett thanks for the explanation
Just in case: I forgot to mention that the same code always works fine when launched outside WSL (in a regular cmd) but maybe WSL is just favoring the race condition?

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!