https://bugs.winehq.org/show_bug.cgi?id=56340
--- Comment #3 from Esme Povirk madewokherd@gmail.com --- OK, I somehow got confused and thought .NET Framework was involved, but I see that's not the case (and now that I'm rereading, I'm not sure where I even got that idea). I didn't know this had worked, so that's cool to find out.
If you run "wine uninstaller", you can see what version of Wine Mono is actually installed in your Wine prefix. You can also uninstall it there and install whatever version you want via MSI (see https://dl.winehq.org/wine/wine-mono/ for the msi downloads). Assuming this is a Wine Mono regression, you should be able to work around it while upgrading your system by keeping 8.1.0 in your Wine prefix (though you may need to redo this step as Wine will update it when it updates your prefix). If it works, that also confirms that it was the Wine Mono upgrade that broke this.
Unfortunately, I wasn't able to reproduce the bug here. Can you get console output from the crash with WINE_MONO_TRACE=x set?