C:\Users\steve\AppData\Roaming\VASSAL\errorLog-3.7.17

[cholmcc]

Did you mean to attach C:\Users\steve\AppData\Roaming\VASSAL\errorLog-3.7.17 - in that case, see How to report problems

@SteveRowe

• Windows 11
• Vassal 3.7.17
• Module Afrika II

Do you mean Afrika 2nd Ed?

@SteveRowe

Initial start screen comes up with “Uncaught Exception, Help us fix this Bug, Vassal had an internal error”.

Does not occur with Guadalajara, Fallschirmjeager or Afrika modules

This is because the module in question does not define a splash image, and in the recent release (3.7.17), this causes an issue (my fault). The problem has been identified and has been fixed. An imminent release will fix it for you. For now, roll back your Vassal installation to 3.7.16.

Please consider to change the title of your post to be more pertinent - e.g., Afrika 2nd Ed. fail on load with Uncaught Exception. Also remember to check the Solved flag when the problem is fixed - only you can do that.

Yours,
Christian