No versions after 3.4.3 will open

[Monkatronic]

I have Windows 64 bit. Java is up to date, 64 bit. For every Vassal version after 3.4.3 (I have tried them all), Vassal will not open. It works fine for 3.4.3 and earlier versions. Error logs are empty. What should I do?

[uckelman]

Thus spake Monkatronic:
> I have Windows 64 bit. Java is up to date, 64 bit. For every Vassal
> version after 3.4.3 (I have tried them all), Vassal will not open. It
> works fine for 3.4.3 and earlier versions. Error logs are empty. What
> should I do?

Check in the directory jre/bin where you have VASSAL installed. Are
java.exe and javaw.exe there?

--
J.

[Monkatronic]

Yes, both. They are there for 3.4.3 (which works), and in the 3.4.11 folder (which does not work).

[uckelman]

Thus spake Monkatronic:
> Yes, both. They are there for 3.4.3 (which works), and in the 3.4.11
> folder (which does not work).

If you try running VASSAL.exe from 3.4.11 from the command line, what
happens? Is there output in the terminal?

--
J.

[Monkatronic]

I'm not quite sure what that means. I opened a command prompt, changed to the Vassal directory, and tried to run vassal.exe from that. No error message, no anything.

[uckelman]

In your terminal, cd to the directory where 3.4.11 is installed. Then run:

jre\bin\java.exe -version

Does that give you any output?

[Monkatronic]

Yes:
openjdk version "15" 2020-9-15
openjdk Runtime Environment AdoptOpenJDK (build 15+36)
openjdk 64-bit Server VM AdoptOpenJDK (build 15+36, mixed mode)

[uckelman]

Ok. That's good. It demonstrates that the bundled Java works.

In your terminal, cd to the directory where 3.4.11 is installed. Then run:

jre\bin\java.exe -cp lib\Vengine.jar VASSAL.launch.ModuleManager

Does that give you any output? Does the Module Manager open? Is anything written to the errorLog?

[Monkatronic]

Output is "VASSAL: C:\users\Emper\AppData\Roaming\Vassal"
Nothing opened. I can't find any error log.

[Cattlesquat]

Your errorlog would be located in C:\Users\<username>\AppData\Roaming\VASSAL

It would be called errorlog-3.4.11 or something like that.

[Monkatronic]

There is no error log (only error logs from previous installs).

[uckelman]

Please try this test build:

http://www.vassalengine.org/~uckelman/t ... ows-64.exe

Launch it the same way as previously, running

jre\bin\java.exe -cp lib\Vengine.jar VASSAL.launch.ModuleManager

on the command line from the directory where the test build is installed. There should be additional output beyond "VASSAL: C:\users\Emper\AppData\Roaming\Vassal". Please paste that here.

[Monkatronic]

Output is again "VASSAL: C:\users\Emper\AppData\Roaming\Vassal". Only that.
Thank you for your help, much appreciated.

[uckelman]

Are you certain you were running from the directory where the test build is installed?

[coylote]

I'm using 64bit Windows, and I am also having trouble running 3.4.11. When I try to open my computer thinks for a moment and then nothing happens. However, if I log in to the Administrator profile, it will run just fine. It's not a permissions setting that I can find. My named profile has full administrative access.