https://bugs.winehq.org/show_bug.cgi?id=54317
--- Comment #2 from Patrick Hibbs hibbsncc1701@gmail.com --- (In reply to Alexandre Julliard from comment #1)
Is there anything peculiar about your setup? How are you building and running Wine?
I build wine as per the Shared WoW64 section of the wiki. I don't need to use a chroot nor container, but I do wind up building wine three times to get a functional build. (wine64 -> winetools -> wine32) I also have configure set to use a custom installation prefix under /opt.
After that I use update-alternatives for wine's main binaries (wine, wine32/64, wine-preloader/64, winecfg, explorer, msiexec, etc.) so that they can be found on the local $PATH, and so that I can switch them out seamlessly if I need to. (Makes testing regressions or other things easier for me.) This winds up putting about two layers of symlinks between where ever the $PATH search found wine and the actual installation directory, but I haven't had an issue with wine loading before now.
Normally, If I'm testing something, I do so manually from the shell prompt. I.e. "WINEPREFIX=/path/to/some/new/prefix winecfg" but once things are stable and I know the prefix to be functional it gets moved to using a shell script I wrote to manage things. (Mostly save game / user data management, but it's also used by .desktop files and the other end users I have to manage wine for. (Copying the prefixes to their own directories.)) That said if something breaks I will try to test and re-create the prefix manually before coming here with it.