Troubleshooting Common Problems

Here are some common technical problems players encounter with VASSAL, and how to troubleshoot them.

Nothing Happens When I Open Vassal
Are you running some antivirus software? We've had some reports of AV software swiping files VASSAL needs to run.

In particular, please check the jre\bin directory under the directory in which VASSAL is installed. Do you see files called javaw and java there? (Or, if your file browser isn't hiding extensions for known file types, javaw.exe and java.exe?) If those files are missing it means that your anti-virus software has blocked or quarantined the bundled Java JVM that VASSAL uses to run. Open your Anti-Virus program and white list those files.

Beginning with VASSAL 3.3.0, Java is "bundled" with VASSAL on Windows and Mac (not on Linux). This means that on those platforms it no longer matters what version of VASSAL you have installed - indeed you don't have to separately install Java any more on Windows and Mac. However, some antivirus software does not trust the Java JVM executables which we provide. Thus it must be told to allow them.

Another possible cause if Vassal worked before but has stopped opening is that you have a corrupted global preferences file. Look for the file prefs/V_Global (the prefs directory is in the same directory as the Error Logs), move it somewhere else, and try to start Vassal.

(Windows) "Tearing" on maps, Corrupted Graphics, or Map Not Fully Updating
If you run on Microsoft Windows and your map is not updating correctly (e.g. "tearing" or not fully updating), go to Vassal's preferences and check the box for Disable DirectX D3D Pipeline.

Some combinations of video drivers and versions of Java don't work well together. If you have rendering problems with Direct3D turned on and they go away when you turn it off, then you have one of those bad combinations. This preference (and potential problem) exists only on Windows machines.



(All Platforms) "Tearing" on maps, Corrupted Graphics, or Map Not Fully Updating
If you are having tearing on maps, and are not running on Windows (or if you have already tried the Windows-specific solution above):

After the first time you run one of these builds, there will be a file called  in VASSAL's config directory where you can add VM flags for the Player, one per line.

Try these two lines, in order, one at a time:



(Mac) "VASSAL cannot be opened because the developer cannot be verified. MacOS cannot verify that this app is free from malware."


If you have the current or a recent version of MacOS, Gatekeeper is probably active--MacOS will block VASSAL from running on the first attempt (because this isn't what Apple considers a code-signed app).

''You'll have to go into System Preferences -> Security & Privacy to allow it to run. This only needs to be done once.''

Alternatively you can open a Finder window, type VASSAL into the search field, and double click on your new VASSAL install to open it for the first time - this will give you an "are you sure?" type dialog, and once you are past that then you will be able to open VASSAL normally in the future.

Alternative solution
Use the web-client  which is part of MacOS. Follow the steps below:

  Go to the GitHub Release page   Find the version of VASSAL you are interested in. For example  for VASSAL version 3.6.17 on Apple M1 chips. Right click the link and select Copy link address (or similar).   Open a terminal via Finder&rarr;Applications&rarr;Utilities&rarr;Terminal (If you have not used a terminal before, perhaps this solution is not for you. The terminal is a very powerful tool to interact with the operating system in ways you've never imagined.)  In the terminal, change directory to your desktop directory cd Desktop  In the terminal, type curl -LO &lt;paste copied link&gt; where  is the link you copied above pasted into the terminal, and press enter.</li>  The file will start downloading showing you a nice progress bar</li> </ol> </li> Once downloaded, double-click the VASSAL DMG now on your desktop, and install per usual instructions. </li> </ol>

Explanation
MacOS attaches a quarantine attribute to files downloaded by web browsers, which prompts intervention by the Gatekeeper feature. Downloads performed by command line tools like  and   do not have this attribute set.

<br style="clear:both" />

(Windows) Browsers give a "this file isn't commonly downloaded" warning when downloading installer


When downloading a newly-released version of VASSAL with Edge, Chrome, and other browsers, Microsoft SmartScreen may intervene with a warning that the file isn't commonly downloaded. Respond to these prompts by choosing to keep the file anyway.

<br style="clear:both" />

(Windows) "Windows protected your PC" when running the installer


Windows Defender sometimes blocks VASSAL's installer from running: "Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk."

Windows checks whether executables downloaded from the internet are signed and how often they've been downloaded (globally). Our installer is not presently signed, so you may see this message if you try installing VASSAL shortly after a new release. It does not indicate a problem with the installer.

Click More info in the dialog to reveal the Run anyway button to run the installer.

<br style="clear:both" />

Antivirus scanner quarantines the installer




Some antivirus scanners (AVG and Avast in particular) mistdetect Vassal's Windows installers as a threat. The way to fix this problem, both for yourself and for others, is to report the false positives to your AV vendor. (E.g., there is a "Report as false positive" link in the screenshot from AVG shown here.)

If you want to verify that your installer is the installer we released, you can check the SHA256 hash of your installer file against the list we publish. (If you need a tool for computing the SHA256 hash of the installer file you have, a simple solution is to try uploading the file to VirusTotal, which will compute the file's SHA256 hash and display it.)