Debugger for Java, "javaExec": "java.bat", spawn EINVAL

Java debugger cannot launch with "javaExec": "java.bat" option.

Environment

• Operating System: Windows 10
• JDK version: openjdk 11.0.19 2023-04-18
• Visual Studio Code version: 1.92.0
• Java extension version: -
• Java Debugger extension version: v0.58.2024072207 (pre-release)

Steps To Reproduce

1. make custom java.bat for javaExec

"%JAVA_HOME%\bin\java.exe" %*

2. make .vscode/launch.json with "javaExec" option

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "java",
      "name": "Test",
      "request": "launch",
      "mainClass": "Test",
      "javaExec": "${workspaceFolder}/java.bat"
    }
  ]
}

3. Launch Debugger

• sample project - java-report.zip

• error logs, but it seems it does not helpful.

notificationsAlerts.ts:42 spawn EINVAL
c	@	notificationsAlerts.ts:42
(anonymous)	@	notificationsAlerts.ts:28
B	@	event.ts:1230
C	@	event.ts:1241
fire	@	event.ts:1265
addNotification	@	notifications.ts:228
notify	@	notificationService.ts:253
(anonymous)	@	mainThreadMessageService.ts:86
f	@	mainThreadMessageService.ts:51
$showMessage	@	mainThreadMessageService.ts:45
S	@	rpcProtocol.ts:458
Q	@	rpcProtocol.ts:443
M	@	rpcProtocol.ts:373
L	@	rpcProtocol.ts:299
(anonymous)	@	rpcProtocol.ts:161
B	@	event.ts:1230
fire	@	event.ts:1261
fire	@	ipc.net.ts:652
K.onmessage	@	localProcessExtensionHost.ts:378

Current Result

Expected Result

No error.

Additional Informations

it worked yesterday but it failed today.

Start with the supplied .vscode/launch.json and custom java.bat on Windows 10, then reproduce the launch using the javaExec setting and inspect the reported spawn EINVAL failure. Done means the Java debugger launches successfully with the batch-file executable and no spawn error appears.