It seems, that if java.exe is not "known to Windows", means not in PATH or whereever, it appears that during the NSIS installing process, in a call like
Windows somehow replace the standalone java.exe against a complete path like c:\Windows\java.exe, which is unfortunately pure fantasy and causes a "file not found" error when trying to start OOBD
As workaround java is replaced by cmd.exe, and the java call itself moves as parameter into the the cmd call.
It seems, that if java.exe is not "known to Windows", means not in PATH or whereever, it appears that during the NSIS installing process, in a call like
Windows somehow replace the standalone java.exe against a complete path like c:\Windows\java.exe, which is unfortunately pure fantasy and causes a "file not found" error when trying to start OOBD
As workaround java is replaced by cmd.exe, and the java call itself moves as parameter into the the cmd call.