It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi,

After the updating to 1.7, Age of Wonders 3 crashes at start. I get the error "aow3.exe has stopped working"

Has anyone else had this issue?

Thanks
I got the game to work by running the AoW3_debug.exe if anyone else has this issue.
avatar
Sogin: Hi,

After the updating to 1.7, Age of Wonders 3 crashes at start. I get the error "aow3.exe has stopped working"

Has anyone else had this issue?

Thanks
Are you by chance using Windows 10? There is a small patch fixing crashes with Windows 10 today for Steam users, but I haven't checked whether it is out for GOG users.
Same problem, build number 16952, dated September 17th. I can start AoW3 in debug mode, with occasional error messages (with no visible impact so far).

I saw a message on the Steam forum, written by one of the developers and dated September 21st, that they have "dropped a patch that fixes the crash" and that debug mode is not required anymore. In another post I saw a note saying that the build number of the Steam version is 16980 or so, i.e. higher than that of the GOG version.
How comes that GOG doesn't offer the newest version to their customers? Are there quality issues with the patch, or are you trying to give your customers a reason to prefer Steam?

Don't get me wrong: I know that the update philosophies and systems of GOG and Steam are different, and a delay of 2 weeks may well be caused by this difference. Moreover, a workaround is available that seems to work, and it's embarrassing that a relatively new game like AoW3 isn't W10-compatible.
Nevertheless, a liitle note by GOG here saying that a patch of this problem has been received and will be published in the next two weeks (or so) would be a costumer-friendly gesture. And besides, to be honest, I don't like to see that Steam is better than GOG in certain areas. :-)
I have the same problem. It works only in debug mode on Win 10. I hope they release a patch on GOG soon.
Hello guys,

I also had this problem after exiting the game using alt+f4; before that I had not the problem in windows 10.

edit: I understand what happened. I installed 1.7 but today was the first day I played using it. I guess after exiting the game (no matter alt+f4 or normal) it made something - either to the profile file or something else - and a second attempt to run it resulted in the error. But here is a workaround:

SOLUTION: start your aow3 launcher in win 8 compatibility mode. I read that from the official forum, some guy suggested it. For me it fixed the crash.
Post edited October 04, 2015 by Arcador
avatar
Arcador: SOLUTION: start your aow3 launcher in win 8 compatibility mode. I read that from the official forum, some guy suggested it. For me it fixed the crash.
Yea! It works, and i think it is better workaround than just start game in debug mode.
avatar
Arcador: SOLUTION: start your aow3 launcher in win 8 compatibility mode. I read that from the official forum, some guy suggested it. For me it fixed the crash.
avatar
gklochkov: Yea! It works, and i think it is better workaround than just start game in debug mode.
Agreed. Thanks Arcador.