https://bugs.winehq.org/show_bug.cgi?id=45927
--- Comment #29 from Freigeist m4ng4n@gmx.de --- (In reply to Anthony Jagers from comment #23)
Now I can only tell you about my prefixes and how I put them together.
I installed all the verbs/dlls that you have installed one by one in my division prefix and it did not work.
Also, to exclude that it could be possibly DE related (I have Plasma 5.15 installed), I did a test installation of openSUSE Tumbleweed and tested with the following DEs: i3wm, LXQT, XFCE and Gnome.
The result is the same as with Plasma 5: err:seh:setup_exception stack overflow 1760 bytes.
I also tried in a new prefix to set all api-ms-win-*.dlls which are present in the The Division game directory manually to native, builtin, with the same result.
But I finally found a workaround but I did not log it yet.
The fact that The Division demo starts but the uplay installation doesn't does not make sense. So I thought it could be related to the fact that the demo version is started by the steam client which then starts uplay and it is!
My workaround for those of you that own the uplay version of The Division:
1. Make a separate prefix for The Division only. I called it wine-division-64
2. From now on do every step below pointing wine to this prefix with WINEPREFIX=$HOME/.wine-division-64 (or whatever you called your prefix)
3. Install corefonts and dxvk96 with winetricks
4. Install the uplay client, start it and point it to your existing The Division installation, otherwise download and install The Division. When finished close the uplay client
5. Install Steam for windows in the same prefix and let it run
6. In the Steam client goto "Games" -> "Add a non-steam game to my library" and choose the uplay client
7. Start the uplay client with steam
8. Disable the in-game overlay in the uplay client and in steam. Otherwise the game might crash when it tries to login on the Ubisoft servers
9. Start The Division from the uplay client
10. Play The Division
Andreas