https://bugs.winehq.org/show_bug.cgi?id=46146
--- Comment #12 from Gregor Münch greg87@online.de --- Hello Mr. Focht, as you probably seen, the problem is Proton. This log was actually indeed from a "clean" wineprefix, at least as clean as a proton prefix can be.
I tested again with a custom Proton 5.5 and the issue is still there. But as you said, running winetricks -q dotnet40 is all needed. So while this is an acceptable solution, it would be nice if wine mono would be actually enough to run this.
So just to clarify, I read the backtrace the initial reporter posted and seen a lot of dotnet stuff and while not understanding those things, I assumed he had the same problem like me. I also understand that you dont want to see that proton stuff here. But I was thinking that it was allowed in this case, as this is still the same problem for everyone.
So the thing is, if its the preferred solution to install dotnet40 and things wont get fixed in wine mono, then we should probably close this. Otherwise we should leave this open, or open a new one with a more detailed description.
Just saying, that a lot of games are currently not playable because of launchers requiring dotnet and wine / proton silently fails to execute.
Sorry for this lengthy response and thanks for looking into this.