SAB 6.0 does not Open

SAB 6.0 does not Open
If I uninstall Java (Corretto) and double click SAB, Windows asks how to open.
If I install Java (Corretto), the cursor goes to the busy symbol, and then stops.
Is there a way to get more information? The event viewer shows no errors.

This is happening on 2 different laptops, but other laptops are fine.

On Windows JAVA_HOME environment variable should point to the location of a Java JRE or Java JDK. Then in the Path environment variable you should add the path to javaw.exe.
On my machine this could be one of three places:

  • C:\Program Files\Amazon Corretto\jre8\bin
  • C:\Program Files\Amazon Corretto\jdk1.8.0_212\jre\bin
  • C:\Program Files\Amazon Corretto\jdk1.8.0_212\bin

You only need one of the above. Do not have two different places, that will cause you problems.
If that is not enough then something will have hijacked the file association for .jar.

  • Go to the file C:\Program Files (x86)\SIL\Scripture App Builder\bin\scripture-app-builder.jar
  • Right click and choose Open with . . .
  • If it says the default is OpenJDK Platform binary that is good.
  • If not then choose More apps to look for that one
  • Also check the box Always use this app to open .jar files
  • If no OpenJDK in the list go to the bottom and choose Look for another app on this PC
  • Now navigate to the location of your javaw.exe.
    SAB after a bit of time should open.

I also use the registry to fix problems but that is more complicated.

I have seen .jar files associated with Adobe Acrobat, WinRar, Zip Extractor.

Resetting Win10, and reinstalling everything did not fix the problem.

I checked the path, JAVA_HOME and and the default app for *.jar files. Everything looks good.

I even created a new Profile on one system, nothing opens when double-clicked.

A/V is removed and Windows Defender and Firewall are Disabled.

java -version gives the expected answer.

Same thing with SAB 6.02, and RAB 6.01.

Removing Corretto 8.212.04.2.1, installing 8.222.10.3 fixed the issues. No idea why?

Thanks for keeping us all in the loop. So glad it is fixed now.