Getting a very similar to Issue #15864 on MU4 Command-line Usage

Issue & Scope
MuseScore 4.0.1, in the command-line for Windows 11 CMD. I'm having some trouble with the -j | --job, & -o | --export-to args. I followed the docs to the letter of: MuseScore4.exe [options] [filename …] (Windows) (example syntax). I followed the example json, and wrote it on Notepad++.
However, when I execute command: MuseScore4.exe -j batch.json or MuseScore4.exe --job batch.json, nothing happened (curiously enough), not even an error thrown to the command-line or any new process or uptick usage in my Task Manager.
So, I checked to see if version 4.0.1 had command-line functioning (hoping it was simple user error) by using some of the other commands: MuseScore4.exe -v works & MuseScore4.exe -h works.
Went to try out single case usage: MuseScore4.exe -o "in_file.mid" "out_file.wav" and MuseScore4.exe --export-to "in_file.mid" "out_file.wav" nothing again (either in error or uptick in Task Manager).
I thought maybe my usage was wrong: the docs says: mscore -o 'My Score.pdf' 'My Score.mscz'.
Seems to be no, but I tried a different way anyways: MuseScore4.exe "in_file.mid" -o "out_file.wav" and MuseScore4.exe "in_file.mid" --export-to "out_file.wav" with again, no errors & no uptick in Task Manager.
I can only conclude with evidence & limited understanding (I maybe wrong) of MuseScore4, it seems to be passing errors silently or at the very least not recognizing|parsing job or export commands to internal handler for some reason.

Possibly Related ...
Curiously, when I downgraded to MuseScore3 (Ver: 3.6.2) everything worked, except -o | --export-to. That did work when I used the incorrect: MuseScore4.exe "in_file.mid" -o "out_file.wav" and MuseScore4.exe "in_file.mid" --export-to "out_file.wav"
instead of (suggested): MuseScore4.exe -o "in_file.mid" "out_file.wav". This makes me wonder if it could be related with Version 4.0.1 issue, stated above in code & help|usage doc error|bugs.