I can also confirm for 2.2.3201 on Windows 10, trying to use Java JDK 16.0.1 to play Optifine 1.16.5, which I had been doing successfully since the Java 16 requirement for 1.17 was announced. I signed up for an account here to report this, but will instead throw in with this issue report.
EDIT to add: I applied the workaround by renaming JavaCheck.jar to JavaCheck.jar.disabled, and that's got it working again.
I then wondered if creating an empty folder named JavaCheck.jar would block updates from re-breaking it, or if that would cause errors, so I tried it. I got an "Unable to access jarfile" error complaining about it when I click Play, but the game launched fine otherwise. I decided it was too annoying so I deleted the empty folder. No idea if it would have blocked updates of the jar file. I'm just going to hope this issue is fixed by the next Launcher update.
I am seeing the same. The launcher is overriding the selected Java executable even if it is a later version than what comes with Minecraft. Currently it is insisting on running Minecraft 1.19.2 with Java 17.0.3, even though I have it configured to run with Java 17.0.5.
I tried replacing the contents of "C:\Program Files (x86)\Minecraft Launcher\runtime\java-runtime-gamma\windows-x64\java-runtime-gamma" with that of Java 17.0.5, and edited the .version file to suit, but it just redownloads 17.0.3.
Deleting C:\Program Files (x86)\Minecraft Launcher\game\JavaCheck.jar does nothing to fix the problem.
Considering this is overriding us switching to a more fully-patched Java, this is a potential security issue.
I looked at the command line (it's huge) for the Java it runs (with Sysinternals Process Explorer), copied it into a .bat file, and changed the executable path to "C:\Program Files\Java\jdk-17.0.5\bin\javaw.exe".
It launched. No errors. I was able to connect to a server. The debug screen shows Java 17.0.5 64bit.
Selection of the Java runtime is a feature of the launcher.
New Java patch releases are often available for separate download and installation before they make it into what Minecraft redistributes. As noted, the current security baseline for Java 17 is 17.0.5, but currently the launcher distributed 17.0.3.
Also some mods have historically had their own Java version requirements.
The folder content replacement was an attempt at a work-around for the problem of the launcher ignoring that setting. It didn't work. Bypassing the launcher altogether by putting the command line it uses to launch the game into a batch file and modifying it to use the up to date Java version appears to work so far, launching successfully at least, though further testing would be good.
Good news everyone! I just launched the launcher and after a very slow 'update' it has reverted to 2.3.462, and is properly honoring the java executable setting in installations!
It worked! The protest song (I never got around to writing, much less recording) worked!
BCowcorn Idk why your launcher rolledback but mine didn't, it's still in 2.3.481 and I still have this issue
Thinking of this, it would be cool if it was possible to set the Java path globally to Java 8 and 17, I wonder if there is a feedback, i'll look for it
BCowcorn
I can also confirm for 2.2.3201 on Windows 10, trying to use Java JDK 16.0.1 to play Optifine 1.16.5, which I had been doing successfully since the Java 16 requirement for 1.17 was announced. I signed up for an account here to report this, but will instead throw in with this issue report.
EDIT to add: I applied the workaround by renaming JavaCheck.jar to JavaCheck.jar.disabled, and that's got it working again.
I then wondered if creating an empty folder named JavaCheck.jar would block updates from re-breaking it, or if that would cause errors, so I tried it. I got an "Unable to access jarfile" error complaining about it when I click Play, but the game launched fine otherwise. I decided it was too annoying so I deleted the empty folder. No idea if it would have blocked updates of the jar file. I'm just going to hope this issue is fixed by the next Launcher update.
Launcher version 2.2.3555 just got pushed to me on Windows 10, and reverted the work-around (as expected). Re-applying the work-around worked.
Issue present in...
Windows 10.0 2.2.7265
Tuesday, November 2, 2021, 2:47:51 PM
Also affected version 10.0 2.2.7447 just now. Work-around still working.
I am seeing the same. The launcher is overriding the selected Java executable even if it is a later version than what comes with Minecraft. Currently it is insisting on running Minecraft 1.19.2 with Java 17.0.3, even though I have it configured to run with Java 17.0.5.
I tried replacing the contents of "C:\Program Files (x86)\Minecraft Launcher\runtime\java-runtime-gamma\windows-x64\java-runtime-gamma" with that of Java 17.0.5, and edited the .version file to suit, but it just redownloads 17.0.3.
Deleting C:\Program Files (x86)\Minecraft Launcher\game\JavaCheck.jar does nothing to fix the problem.
Considering this is overriding us switching to a more fully-patched Java, this is a potential security issue.
I looked at the command line (it's huge) for the Java it runs (with Sysinternals Process Explorer), copied it into a .bat file, and changed the executable path to "C:\Program Files\Java\jdk-17.0.5\bin\javaw.exe".
It launched. No errors. I was able to connect to a server. The debug screen shows Java 17.0.5 64bit.
We'll see how it goes.
Selection of the Java runtime is a feature of the launcher.
New Java patch releases are often available for separate download and installation before they make it into what Minecraft redistributes. As noted, the current security baseline for Java 17 is 17.0.5, but currently the launcher distributed 17.0.3.
Also some mods have historically had their own Java version requirements.
The folder content replacement was an attempt at a work-around for the problem of the launcher ignoring that setting. It didn't work. Bypassing the launcher altogether by putting the command line it uses to launch the game into a batch file and modifying it to use the up to date Java version appears to work so far, launching successfully at least, though further testing would be good.
Good news everyone! I just launched the launcher and after a very slow 'update' it has reverted to 2.3.462, and is properly honoring the java executable setting in installations!
It worked! The protest song (I never got around to writing, much less recording) worked!