https://bugs.winehq.org/show_bug.cgi?id=52821
--- Comment #4 from C. Leu kle@bluewin.ch --- Awesome, - I found out an even simpler manual workaround! :-)
A new short HowTo:
- simply copy the original msvcp140_atomic_wait.dll into the affected program folder.
So in my case, the 32bit msvcp140_atomic_wait.dll goes into the CXBX folder because it is effectively a 32bit application. The 64bit msvcp140_atomic_wait.dll comes into the PCSX-Redux folder because PCSX-Redux is a 64bit application.
- start up winecfg from the CLI and select "Libraries", add here a new one called msvcp140_atomic_wait (without the dll extension)
As in the previous HowTo, there should be now a new entry "msvcp140_atomic_wait (Native, Builtin)".
You should be able to start the affected program normally. I can confirm that this works again perfectly well for me. This is also the better solution for the case that the wine-prefix gets updated. And in contrast to the vcrun2019 winetricks argument this solution is easy reversible (especially for simply "knitted" end-users) and doesn't install the whole native MS Visual C++ 2019 "ballast" when it is effectively not needed. ;-)