"Command 'cmd' not found" when running Java code with WSL as the default profile

When running/debugging Java programs using the extension(s), while having WSL as the default terminal profile, the program can't be run and exits with the following error:

Command 'cmd' not found, but there are 17 similar ones.

fish:        
 cmd /C "c:\Users\<Username>\.vscode\extensions\vscjava.vscode-java-debug-0.32.1\scripts\launcher.bat "C:\Program Files\AdoptOpenJDK\jdk-11.0.10.9-hotspot\bin\java.exe" -Dfile.encoding=UTF-8 -cp C:\Users\<Username>\AppData\Roaming\Code\User\workspaceStorage\f2ff3effae7386c130fa74d8c23d1e02\redhat.java\jdt_ws\Izzivi_163d1b63\bin Izziv5 "

The error occurs on multiple shells (both Bash and Fish tested), so this is not a Fish-specific issue.

Calling cmd.exe instead of cmd might fix the issue, since cmd.exe is available from WSL, while just cmd isn't.

Environment

• Operating System: Windows 10
• JDK version: 11 (AdoptOpenJDK)
• Visual Studio Code version: 1.55.1
• Java extension version: (Java Extension Pack?) v0.13.0
• Java Debugger extension version: v0.32.1

Steps To Reproduce

1. Use Ubuntu (WSL) as the default shell
2. Try to Run or Debug a Java project
3. The runner/debugger fails with the above error

El fallo se muestra en scripts/launcher.bat y ocurre cuando Run o Debug se inicia con Ubuntu o WSL como shell predeterminado. Reproduce esos pasos en Windows 10, inspecciona cómo se forma el comando del launcher y verifica el resultado tanto en Bash como en Fish; se considera terminado cuando los programas Java se ejecutan y depuran sin el error “Command 'cmd' not found”.