Vassal startup failure

Unable to launch siege of jerusalem. Below is the text in the log file:

2026-11-18 20:36:05,028 [4648-main] INFO VASSAL.launch.StartUp - Starting
2026-11-18 20:36:05,044 [4648-main] INFO VASSAL.launch.StartUp - OS Windows 11 10.0 amd64
2026-11-18 20:36:05,045 [4648-main] INFO VASSAL.launch.StartUp - Java version 26.0.2.1
2026-11-18 20:36:05,045 [4648-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.7.30\jre
2026-11-18 20:36:05,045 [4648-main] INFO VASSAL.launch.StartUp - VASSAL version 3.7.30
2026-11-18 20:36:05,188 [4648-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2026-11-18 20:36:07,713 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\ftarz\Downloads\Bx-GOSS_Atlantic Wall_V2.5.0.pre3 (1).vmod
2026-11-18 20:36:09,224 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2026-11-18 20:36:09,226 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module AW2 module
2026-11-18 20:36:09,230 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - JVM maximum heap size: 1024 MB
2026-11-18 20:36:09,241 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -Xms1024M -Xmx1024M -Duser.home=C:\Users\ftarz -Duser.dir=C:\Program Files\VASSAL-3.7.30 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\ftarz\Downloads\Bx-GOSS_Atlantic Wall_V2.5.0.pre3 (1).vmod
2026-11-18 20:36:09,874 [35632-main] INFO VASSAL.launch.StartUp - Starting
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - OS Windows 11 10.0 amd64
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - Java version 26.0.2.1
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.7.30\jre
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - VASSAL version 3.7.30
2026-11-18 20:36:09,886 [35632-main] INFO VASSAL.launch.Launcher - Player
2026-11-18 20:36:12,894 [35632-AWT-EventQueue-0] INFO VASSAL.build.GameModule - AW2 module version 2.5.0
2026-11-18 20:41:27,668 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:43:27,670 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:45:27,672 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:47:27,674 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:49:27,675 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:51:27,676 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:53:35,370 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:55:35,372 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:57:35,374 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 20:59:35,376 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:01:35,377 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:03:35,377 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:05:35,379 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:07:35,380 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:09:35,380 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:12:02,844 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:14:02,845 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:16:02,847 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:18:02,848 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:18:39,443 [35632-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.7.30 VASSAL.launch.ModuleManager --update-game C:\Users\ftarz\OneDrive\Documents\Vassal Games\Siege of Jerusalem\Start Turn 1.vsav
2026-11-18 21:28:24,850 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:30:24,852 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:32:24,853 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:34:24,855 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:36:24,858 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:38:24,859 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:40:24,861 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:42:24,862 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:44:24,865 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:46:24,866 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:48:24,868 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:50:24,870 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:52:24,871 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:54:24,872 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:56:24,874 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 21:58:24,877 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 22:00:24,891 [35632-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2026-11-18 22:00:47,912 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\ftarz\OneDrive\Documents\Vassal Modules\Ancients\Siege Of JErusalem 3_0_0.vmod
2026-11-18 22:00:48,409 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.TilingHandler - No images to tile.
2026-11-18 22:00:48,410 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.AbstractLaunchAction - Loading module Siege of Jerusalem - AH (1989)
2026-11-18 22:00:48,415 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.AbstractLaunchAction - JVM maximum heap size: 1024 MB
2026-11-18 22:00:48,417 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -Xms1024M -Xmx1024M -Duser.home=C:\Users\ftarz -Duser.dir=C:\Program Files\VASSAL-3.7.30 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\ftarz\OneDrive\Documents\Vassal Modules\Ancients\Siege Of JErusalem 3_0_0.vmod
2026-11-18 22:00:48,475 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream - Error: could not open `C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg’
2026-11-18 22:00:48,476 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream -

2026-11-18 22:00:48,479 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -Xms128M -Xmx128M -Duser.home=C:\Users\ftarz -Duser.dir=C:\Program Files\VASSAL-3.7.30 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\ftarz\OneDrive\Documents\Vassal Modules\Ancients\Siege Of JErusalem 3_0_0.vmod
2026-11-18 22:00:48,525 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream - Error: could not open `C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg’
2026-11-18 22:00:48,525 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream -

2026-11-18 22:00:48,566 [4648-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog -
java.util.concurrent.ExecutionException: java.io.IOException: failed to start child process
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:124)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:193)
at java.desktop/javax.swing.SwingWorker.get(SwingWorker.java:610)
at VASSAL.launch.AbstractLaunchAction$LaunchTask.done(AbstractLaunchAction.java:510)
at VASSAL.launch.Player$LaunchAction$1.done(Player.java:187)
at java.desktop/javax.swing.SwingWorker$4.run(SwingWorker.java:747)
at java.desktop/javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(SwingWorker.java:837)
at java.desktop/sun.swing.AccumulativeRunnable.run(AccumulativeRunnable.java:112)
at java.desktop/javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(SwingWorker.java:847)
at java.desktop/javax.swing.Timer.fireActionPerformed(Timer.java:289)
at java.desktop/javax.swing.Timer$DoPostEvent.run(Timer.java:221)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:323)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:714)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:693)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: java.io.IOException: failed to start child process
at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:458)
at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:257)
at java.desktop/javax.swing.SwingWorker$1.call(SwingWorker.java:303)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:330)
at java.desktop/javax.swing.SwingWorker.run(SwingWorker.java:340)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at java.base/java.lang.Thread.run(Thread.java:1516)

I assume you are referring to this version. Can you confirm?

Siege of Jerusalem 3.0.0

FYI, I just updated the module to version 4.0.0. The only thing I updated was to update (finally) the oblique Avalon Hill grid numbering system, now that Vassal Engine permits it. (Thanks Vassal Team).

Make sure you have updated Vassal to the latest version Vassal 3.8.2. Download the Siege of Jerusalem module version 4.0.0 and let me know if that loads. My suspicion is that because you are still on Vassal 3.7.30, you need to update for the Siege of Jerusalem module to load.

The easiest way to get the updated Vassal Version is to close your Vassal Module Library window and reopen it. When you do, it will inform you that there is a new update and ask if you want to update. Choose OK or Yes, whichever is appropriate to go to the downloads page and download the version appropriate for your operating system.

Rob

This line from the error log points to the cause. It could be that your Vassal install is corrupt, or it could be that something is blocking that file from being read (e.g., some antivirus program).

Updating the module won’t help with this problem, though you’re certainly welcome to do that. The first thing I would try is upgrading to the current version of Vassal, which is 3.8.2 right now. If this problem still occurs after upgrading, post the new error log from that run.

When you quote the errorLog, please put the quoted text between pairs of ``` to make it come out in “code” mode. Also, remove lines that are not really relevant to the problem at hand. For example

2026-11-18 20:36:05,028 [4648-main] INFO VASSAL.launch.StartUp - Starting
2026-11-18 20:36:05,044 [4648-main] INFO VASSAL.launch.StartUp - OS Windows 11 10.0 amd64
2026-11-18 20:36:05,045 [4648-main] INFO VASSAL.launch.StartUp - Java version 26.0.2.1
2026-11-18 20:36:05,045 [4648-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.7.30\jre
2026-11-18 20:36:05,045 [4648-main] INFO VASSAL.launch.StartUp - VASSAL version 3.7.30
2026-11-18 20:36:05,188 [4648-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2026-11-18 20:36:07,713 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\ftarz\Downloads\Bx-GOSS_Atlantic Wall_V2.5.0.pre3 (1).vmod
2026-11-18 20:36:09,224 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2026-11-18 20:36:09,226 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module AW2 module
2026-11-18 20:36:09,230 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - JVM maximum heap size: 1024 MB
2026-11-18 20:36:09,241 [4648-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -Xms1024M -Xmx1024M -Duser.home=C:\Users\ftarz -Duser.dir=C:\Program Files\VASSAL-3.7.30 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\ftarz\Downloads\Bx-GOSS_Atlantic Wall_V2.5.0.pre3 (1).vmod
2026-11-18 20:36:09,874 [35632-main] INFO VASSAL.launch.StartUp - Starting
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - OS Windows 11 10.0 amd64
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - Java version 26.0.2.1
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.7.30\jre
2026-11-18 20:36:09,885 [35632-main] INFO VASSAL.launch.StartUp - VASSAL version 3.7.30
2026-11-18 20:36:09,886 [35632-main] INFO VASSAL.launch.Launcher - Player
2026-11-18 20:36:12,894 [35632-AWT-EventQueue-0] INFO VASSAL.build.GameModule - AW2 module version 2.5.0
...
2026-11-18 21:18:39,443 [35632-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.7.30 VASSAL.launch.ModuleManager --update-game C:\Users\ftarz\OneDrive\Documents\Vassal Games\Siege of Jerusalem\Start Turn 1.vsav
...
2026-11-18 22:00:47,912 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\ftarz\OneDrive\Documents\Vassal Modules\Ancients\Siege Of JErusalem 3_0_0.vmod
2026-11-18 22:00:48,409 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.TilingHandler - No images to tile.
2026-11-18 22:00:48,410 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.AbstractLaunchAction - Loading module Siege of Jerusalem - AH (1989)
2026-11-18 22:00:48,415 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.launch.AbstractLaunchAction - JVM maximum heap size: 1024 MB
2026-11-18 22:00:48,417 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -Xms1024M -Xmx1024M -Duser.home=C:\Users\ftarz -Duser.dir=C:\Program Files\VASSAL-3.7.30 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\ftarz\OneDrive\Documents\Vassal Modules\Ancients\Siege Of JErusalem 3_0_0.vmod
2026-11-18 22:00:48,475 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream - Error: could not open `C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg’
2026-11-18 22:00:48,476 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream -

2026-11-18 22:00:48,479 [4648-SwingWorker-pool-2-thread-2] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.7.30\jre\bin\java -Xms128M -Xmx128M -Duser.home=C:\Users\ftarz -Duser.dir=C:\Program Files\VASSAL-3.7.30 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\ftarz\OneDrive\Documents\Vassal Modules\Ancients\Siege Of JErusalem 3_0_0.vmod
2026-11-18 22:00:48,525 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream - Error: could not open `C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg’
2026-11-18 22:00:48,525 [4648-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream -

2026-11-18 22:00:48,566 [4648-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog -
	java.util.concurrent.ExecutionException: java.io.IOException: failed to start child process
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:124)
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:193)
	at java.desktop/javax.swing.SwingWorker.get(SwingWorker.java:610)
	at VASSAL.launch.AbstractLaunchAction$LaunchTask.done(AbstractLaunchAction.java:510)
	at VASSAL.launch.Player$LaunchAction$1.done(Player.java:187)
	at java.desktop/javax.swing.SwingWorker$4.run(SwingWorker.java:747)
	at java.desktop/javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(SwingWorker.java:837)
	at java.desktop/sun.swing.AccumulativeRunnable.run(AccumulativeRunnable.java:112)
	at java.desktop/javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(SwingWorker.java:847)
	at java.desktop/javax.swing.Timer.fireActionPerformed(Timer.java:289)
	at java.desktop/javax.swing.Timer$DoPostEvent.run(Timer.java:221)
	at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:323)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:714)
	at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:693)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: java.io.IOException: failed to start child process
	at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:458)
	at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:257)
	at java.desktop/javax.swing.SwingWorker$1.call(SwingWorker.java:303)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:330)
	at java.desktop/javax.swing.SwingWorker.run(SwingWorker.java:340)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
	at java.base/java.lang.Thread.run(Thread.java:1516)

What we can see in the above log

  • 2026-11-18 20:36:05,045 Vassal 3.7.30
  • 2026-11-18 20:36:05,044 Windows 11 on amd64
  • 2026-11-18 20:36:09,241 module Bx-GOSS_Atlantic Wall_V2.5.0.pre3 (1).vmod loaded without problem (2026-11-18 20:36:12,894)
  • 2026-11-18 21:18:39,443 updating the save Start Turn 1.vsav of presumably Siege of Jerusalem without problems
  • 2026-11-18 22:00:47,912 loading module Siege Of JErusalem 3_0_0.vmod gives
    • 2026-11-18 22:00:48,475 WARN VASSAL.tools.logging.LoggedOutputStream - Error: could not open \C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg’`, but that does not cause the crash.
  • 2026-11-18 22:00:48,479 loading module Siege Of JErusalem 3_0_0.vmod gives
    • 2026-11-18 22:00:48,475 WARN VASSAL.tools.logging.LoggedOutputStream - Error: could not open C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg’ which doesn’t seem to cause the crash - though it is not good.
  • Your module and save are sitting on OneDrive
    • C:\\Users\\ftarz\\OneDrive\\Documents\\Vassal Modules\\Ancients\\Siege Of JErusalem 3_0_0.vmod
    • C:\Users\ftarz\OneDrive\Documents\Vassal Games\Siege of Jerusalem\Start Turn 1.vsav
    • We’ve seen that storing data on OneDrive can be problematic.

@clanmacrae - @ftarzanin is presumably loading version 3.0.0 of The Siege of Jerusalem which is compatible with Vassal 3.7.30. It is only version 4.0.0 of the module that requires Vassal 3.8.2, so I guess @uckelman is right that it has nothing to do with the module.

But, I don’t think that C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg cannot be opened is the root cause, since at 20:36:09 one module is loaded just fine, but at 22:00:48 - a little under an hour and a half later - there’s a problem.

I would suggest the following course of action

  1. Move the module and saves away from OneDrive, and see if that makes a difference.
  2. Reinstall Vassal 3.7.30, to possibly fix the missing C:\Program Files\VASSAL-3.7.30\jre\lib\jvm.cfg
  3. Install Vassal 3.8.2 to see if a newer Vassal fixes the problem.

Yours,
Christian

True. The update of the module is coincidental to the issue, but I thought it best to get him working with the latest version of the module since it’s out there to save some frustration down the line. Updating his Vassal Version was the actual advice given to cure the issue but that may have gotten lost in the explanation that included the module update.

In my case, Smart App Control in Windows is blocking the app and there’s now no way to let VASSAL through individually.

Is this related to the Siege of Jerusalem module or Vassal in general?