# Can't run any versions past 3.6.16
**URL:** https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286
**Category:** Technical Support & Bugs
**Created:** [June 11, 2023, 9:55pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286 "2023-06-11T21:55:40Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 1:52pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/21 "2023-06-17T13:52:32Z")
This one also failed
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 2:04pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/22 "2023-06-17T14:04:13Z")
Next one: [https://vassalengine.org/~uckelman/VASSAL-7b6ba53e.exe](https://vassalengine.org/~uckelman/VASSAL-7b6ba53e.exe)
(I suspect this one will work. The bad commit is probably fa9a7cbd. Once we’ve confirmed that, I’ll stare at it a bit to see if I can spot what’s wrong, and then I’ll have a fix for you to test.)
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 2:45pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/23 "2023-06-17T14:45:19Z")
Yes, this one did work. Might not get to your next one for an hour or so
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 3:00pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/24 "2023-06-17T15:00:36Z")
Next one: [https://vassalengine.org/~uckelman/VASSAL-revert.exe](https://vassalengine.org/~uckelman/VASSAL-revert.exe)
This one is produced by launch4j 3.50 with commit fa9a7cbd reverted. I suspect it will work. The next step after this one is to figure out what’s wrong with that commit. I don’t quite see it yet.
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 3:33pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/25 "2023-06-17T15:33:43Z")
Yes, this one worked
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 8:44pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/26 "2023-06-17T20:44:46Z")
Try running the original VASSAL.exe from 3.6.17 with the command line option `--l4j-debug-all`, so like this:
```auto
VASSAL.exe --l4j-debug-all
```
That should produce a file named `launch4j.log`. Please post the contents of that file.
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 10:03pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/27 "2023-06-17T22:03:02Z")
> [@uckelman](#):
>
> –l4j-debug-all
I didn’t find the log file anywhere, I looked in the user profile path and the vassal directory.
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 10:05pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/28 "2023-06-17T22:05:31Z")
I expect the log would be written in the directory from which you’re launching `VASSAL.exe`. Can you run it from your user directory? Say, as `C:\Program Files\VASSAL-3.6.17\VASSAL.exe --l4j-debug-all`?
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 10:22pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/29 "2023-06-17T22:22:46Z")
Here’s where I found one:
C:\Users\XXXXXX\AppData\Local\VirtualStore\Program Files\VASSAL-3.6.17
But it is a zero byte file.
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 10:23pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/30 "2023-06-17T22:23:33Z")
Does the timestamp for that file match when you ran `VASSAL.exe`?
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 10:25pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/31 "2023-06-17T22:25:14Z")
Yes, it matched 17:55 EST
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 10:37pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/32 "2023-06-17T22:37:59Z")
Let’s see if we can figure out how far it gets before crashing.
Try this one: [https://vassalengine.org/~uckelman/VASSAL-1.exe](https://vassalengine.org/~uckelman/VASSAL-1.exe)
(This one might work. If it works, that means it got at least up to the bail-out point I inserted.)
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 10:55pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/33 "2023-06-17T22:55:42Z")
Actually it didn’t get through. I also tried it with the log switch and it didn’t create one.
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 10:59pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/34 "2023-06-17T22:59:18Z")
Just to make sure, I ran VASSAL-7b6ba53e.exe again with the log switch and it did create one, so I know it can work 🙂
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 11:05pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/35 "2023-06-17T23:05:32Z")
Thank you for checking that—I was about to ask. This means VASSAL-1.exe is failing sooner than I thought it would.
Next one: [https://vassalengine.org/~uckelman/VASSAL-2.exe](https://vassalengine.org/~uckelman/VASSAL-2.exe)
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 11:25pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/36 "2023-06-17T23:25:12Z")
No run on that one and no log
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 11:36pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/37 "2023-06-17T23:36:42Z")
How about this one? [https://vassalengine.org/~uckelman/VASSAL-3.exe](https://vassalengine.org/~uckelman/VASSAL-3.exe)
---
### Author:  [@TheChin](https://forum.vassalengine.org/u/TheChin)
#### Post date: [June 17, 2023, 11:50pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/38 "2023-06-17T23:50:00Z")
Same result, no run and no log
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 17, 2023, 11:51pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/39 "2023-06-17T23:51:36Z")
It’s obnoxious that it doesn’t flush the log on each write… That’s something you’d really like to have when you’re doing debug logging.
I’ll stare at this more tomorrow. Thanks for testing.
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 18, 2023, 4:07pm UTC](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286/40 "2023-06-18T16:07:38Z")
I’ve hit a wall. In order to debug further, I need to be able to recompile `head.c` in Launch4j, but Launch4j doesn’t provide any instructions for doing that correctly. (I’ve spent about four hours now trying.)
I’m going to file a bug report with Launch4j, but it could be a long time (or never) before it gets acted on. I might switch us back to Launch4j 3.14, which doesn’t have this problem. In the meantime, you can use a VASSAL.exe from 3.6.16 as your launcher instead.
[Previous page](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286.md?page=1)
[Next page](https://forum.vassalengine.org/t/cant-run-any-versions-past-3-6-16/77286.md?page=3)