Beware: In Windows 10 Home edition, the current Minecraft Launcher that has no visible EXE in the file system, and launches the newest Minecraft Java Edition which is currently 1.8.1, seems to have no JavaCheck.jar to be deleted, according to Windows Search on "This PC" (because I believe I deleted it along with the rest of the old exe-based version of the Launcher), and yet I'm getting the very similar "jni error has occurred" error message, which took the place of the error message in this ticket, after I updated to newest jdk and jre – at present jdk-17.0.1 and jre1.8.0_311. Even so, I can launch Minecraft 1.6.2 fine when selecting that in the Launcher's dropdown.
In other words, beware that there is something in the details of (how this workaround is done, or the newest Minecraft Launcher, or related to how PATH is set up, or related to updating jdk and jre separately, I don't know yet) that seemed to cause the workaround to create another (very similar) jni-related crash problem, when launching Minecraft 1.8.1.
I figure this can be solved by uninstalling the newer jdk and/or jre and installing the exact version(s) that Minecraft 1.8.1 expects, whatever that might be.
Nathan Peirce
Beware: In Windows 10 Home edition, the current Minecraft Launcher that has no visible EXE in the file system, and launches the newest Minecraft Java Edition which is currently 1.8.1, seems to have no JavaCheck.jar to be deleted, according to Windows Search on "This PC" (because I believe I deleted it along with the rest of the old exe-based version of the Launcher), and yet I'm getting the very similar "jni error has occurred" error message, which took the place of the error message in this ticket, after I updated to newest jdk and jre – at present jdk-17.0.1 and jre1.8.0_311. Even so, I can launch Minecraft 1.6.2 fine when selecting that in the Launcher's dropdown.
In other words, beware that there is something in the details of (how this workaround is done, or the newest Minecraft Launcher, or related to how PATH is set up, or related to updating jdk and jre separately, I don't know yet) that seemed to cause the workaround to create another (very similar) jni-related crash problem, when launching Minecraft 1.8.1.
I figure this can be solved by uninstalling the newer jdk and/or jre and installing the exact version(s) that Minecraft 1.8.1 expects, whatever that might be.