If a user creates the wineprefix, with only 64-bit packages installed, the user gets an empty syswow64 directory inside the prefix. In that situation 64-bit applications are running, but when the user then installs the 32-bit packages the prefix stops to work with this message, even when the application to invoke is a 64-bit application and worked before: ``` wine: could not load kernel32.dll, status c0000135 ``` To help diagnosing this sitution this patch adds some more information which process could not find which kernel32.dll. This would look like this: ``` wine: could not load kernel32.dll, status c0000135, architecture wow64, in L"C:\\windows\\syswow64\\start.exe" ``` This caused probably bug #59043, and it bite me today again, when copying build directories to a ancient machine to save build time. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9794