# Saving game or creating log closes Vassal

**URL:** <https://forum.vassalengine.org/t/saving-game-or-creating-log-closes-vassal/90405>\
**Category:** Technical Support & Bugs\
**Created:** [August 11, 2026, 5:41pm UTC](https://forum.vassalengine.org/t/saving-game-or-creating-log-closes-vassal/90405 "2026-08-11T17:41:01Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![dsulsberger](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/d/ce73a5/32.png) [@dsulsberger](https://forum.vassalengine.org/u/dsulsberger)\
**Post date:** [August 15, 2026, 7:19pm UTC](https://forum.vassalengine.org/t/saving-game-or-creating-log-closes-vassal/90405/16 "2026-08-15T19:19:24Z")

</div>

So I started Vassal using your instructions to do it from a command terminal. I opened a new game from the module manager, and I was able to start a log file and save the game without a crash! Next I tried starting Vassal from the desktop. Again everything worked normally. I restarted the computer, started Vassal from the desktop and had no problems starting a logfile or saving a game. The only other change I had made was to clear out some space on my OneDrive. However all Vassal files should now be stored locally.

So I’m a little baffled on what actually fixed the problem, but very happy to apparently have it solved. I’m sure it was a Microsoft/Windows issue of some kind.

Thanks so much for the help, and the patience to explain things.

---

_[View the full topic](https://forum.vassalengine.org/t/saving-game-or-creating-log-closes-vassal/90405)._