PDA

View Full Version : Both Check For Updates and Settings are crashing my client



jonesdaadi
June 16th, 2026, 23:09
Windows 10. I was able to update earlier today, but since this afternoon, when i click either check for updates or settings the entire client crashes. i attempted to restart, i have made no changes in my security, and nothing else seems wrong. i can join my campaigns if i so choose, but not update and not change settings. any thoughts on something i could try?

Death from Below
June 17th, 2026, 00:44
I have a player right now who is having the exact same problem. He is also on windows 10. He was able to update earlier today to the second most recent version but not the very newest version which must have come out late this afternoon.

pindercarl
June 17th, 2026, 00:58
I have a player right now who is having the exact same problem. He is also on windows 10. He was able to update earlier today to the second most recent version but not the very newest version which must have come out late this afternoon.

There was an update this morning for the new Launcher/Updater. There has not been an additional update.

Officially, Fantasy Grounds does not support Windows 10 (https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1136984087/System+Requirements). I mention this as we do not test on Windows 10, nor do we have the facility to do so. For technical reasons, the latest version of the Updater is built using Unity 6.4, while the Launcher is currently still on Unity 6.0. While I'm not aware of any differences between the two versions that should result in a crash, that is the only functional difference that I can imagine might be at issue. I'll do some research to see if I can find any other reported crashes with Unity 6.4 on Windows 10.

pindercarl
June 17th, 2026, 01:02
There was an update this morning for the new Launcher/Updater. There has not been an additional update.

Officially, Fantasy Grounds does not support Windows 10 (https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1136984087/System+Requirements). I mention this as we do not test on Windows 10, nor do we have the facility to do so. For technical reasons, the latest version of the Updater is built using Unity 6.4, while the Launcher is currently still on Unity 6.0. While I'm not aware of any differences between the two versions that should result in a crash, that is the only functional difference that I can imagine might be at issue. I'll do some research to see if I can find any other reported crashes with Unity 6.4 on Windows 10.

I was able to turn up this post on the Steam Community forums: https://steamcommunity.com/sharedfiles/filedetails/?id=2916307652

It may be worth checking to see if you have Windows scaling turned on.

k4071c0
June 17th, 2026, 04:16
Not sure if related but my issue was that after updating, the app didn't reboot itself as it usually does and now everytime that I open FGU, it's bricked (I only see the background image with the FGU logo and the launcher doesn't appear). I'll try this solution later when I'm home to see if it does the trick anyway.

pindercarl
June 17th, 2026, 06:54
Not sure if related but my issue was that after updating, the app didn't reboot itself as it usually does and now everytime that I open FGU, it's bricked (I only see the background image with the FGU logo and the launcher doesn't appear). I'll try this solution later when I'm home to see if it does the trick anyway.

If you are still having issues, try running the installer from the main Fantasy Grounds webpage.

jonesdaadi
June 17th, 2026, 11:06
Reporting back. I actually had reinstalled win 10 a few weeks back. When i did it seems, some parts of the windows updater were not working and i was stuck on an older version of Win10. when i fully updated windows manually to 22H2, the FGUupdater worked. Everything is as normal now. so my situation is an edge case, which if some others are having this issue, make certain that win10 is fully updated. my apologies for the confusion, i did not realize windows update was quietly failing. Thanks for leading me in the correct direction for the solution.