Cannot open VASSAL after updating Java

ASUS X555L
Windows 10 Home
Intel Core i3-5005U
6GB - 64 bit Operating system
VASSAL 3.1.16
Java: Version 8 Update 111 build 1.8.0_111-b14

After having just updated Java, when trying to open VASSAL I get the following message:

The registry refers to a nonexistent Java Runtime Environment installation or the runtime is corrupted.

The system cannot find the path specified.

Thus spake jonfel14:

ASUS X555L
Windows 10 Home
Intel Core i3-5005U
6GB - 64 bit Operating system
VASSAL 3.1.16
Java: Version 8 Update 111 build 1.8.0_111-b14

After having just updated Java, when trying to open VASSAL I get the
following message:

The registry refers to a nonexistent Java Runtime Environment
installation or the runtime is corrupted.

The system cannot find the path specified.

Have you rebooted since updating Java?


J.

Hello there.
Same OS (albeit being the Pro version) and Java version.
Same error message…

Yes, I have rebooted several times. I have also tried to re-install VASSAL.

Thus spake Aradiel:

Hello there.
Same OS (albeit being the Pro version) and Java version.
Same error message…

All of you who are having this problem: How for have you gotten
through these tests?

vassalengine.org/wiki/VASSAL_Does_Not_Start


J.

Thus spake jonfel14:

Yes, I have rebooted several times. I have also tried to re-install
VASSAL.

Reinstalling VASSAL is not going to help with this problem, because
the problem you’re having is with Java, not VASSAL.

Try going through the steps in the link I posted above and report what
you find.

J.

This error happened after the previous Java update as well, a few months ago, and was discussed/resolved in the downforum thread entitled Java update won’t let VASSAL launch, from 21 July 2016.
For me, running Win7, the fix was simple:

  1. Go to Control Panel and remove Java.
  2. Download and install new Java version.

(My layman’s interpretation is that there is an issue with the automatic Java update/install thingie, wherein it leaves remnants of the old Java version in the registry, which is what causes the problem. Removing and installing Java manually seems to fix it, in my case.)

So did my solution work for anyone?

I uninstalled Java and re-installed it, and now VASSAL opens. Thank you.

Good, thank you.
It helps to give this kind of feedback, so that others know what works.

It works for me too in windows8.1 Pro,
thank you