Hi all…

Alas, I need some guidance here! I’ve just gone through the romance of reinstalling Windows and have been religiously reinstalling my various apps. I reinstalled Java Azul zulu17.50.19-ca-jre17.0.11-win_x64 first, followed by JMRI Decoder Pro 5.9.3 and everything seemed fine…until tonight when the following error message popped up when trying to launch Decoder Pro: “Error: Could not create the Java Virtual Machine, (followed by) A fatal exception occurred, program will exit. [OK]”

I tried deleting and reinstalling Java, and then deleting and reinstalling Decoder Pro but to no avail – anyone have any ideas?

TIA

Jim

?

I subsequently ran the JMRI ‘Install Test’ with the following report:

?

?

Testing for Java working

?

<JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.

.Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

?

Some problem finding/running JAVA.

Need to check for 32-bit JAVA install.

?

Now trying to re-run as a 32-bit process....

?

Testing for 32/64-bit Windows

?

Running on 64-bit Windows

?

Testing for 32/64-bit process

?

Running as a 32-bit process

?

Testing for Java working

?

<JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.

.Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

?

Some problem finding/running JAVA.

You must install JAVA first or fix your JAVA install.

Hi all…

?

The good news is that I seem to have resolved my problem. Further to the ‘InstallTest’ report, I uninstalled Azul zulu17.50.19-ca-jre17.0.11-win_x64 and replaced it with Azul zulu17.52.17-ca-jdk17.0.12-win_x64 which seems to have resolved my launch issue! ?

?

Apologies to all for taking up the bandwidth but perhaps it might help someone else if they encounter a similar issue…(?)

?

Jim

?

Hi all…

WRT the latest inquires:

• As per my initial post, the only Java on my computer was the Azul version so the Java.com Removal tool was not required as no Java.com product had ever been installed.
• The InstallTest tool was great; it identified that the issue was with my Java and the ‘fix’ as I described was to remove my original version and then install a more recent version. The mystery remains though, as why the earlier version worked initially but then apparently became corrupted…(??) Anyway, the latest version that I installed [zulu17.52.17-ca-jdk17.0.12-win_x64] corrected whatever had gone awry.

Jim

?