Cant create the win32 prefix in wow64 mode

[fuzzyfresh]

I'm trying to run the script for sm18 (after also failing to get it working on lutris as well) and im getting the following error below. At first glance it looks like a simple thing to fix, just gotta turn off wow64, but after googling and googling, I cant find a single answer more helpful than "you cant disable wow64"

warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.

warning: You appear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this.

WINEPREFIX INFO:
Drive C: total 28
drwxr-xr-x  7 loathsome loathsome 4096 Sep 29 13:14 .
drwxr-xr-x  4 loathsome loathsome 4096 Oct  7 16:38 ..
drwxr-xr-x  3 loathsome loathsome 4096 Sep 29 13:14 ProgramData
drwxr-xr-x  6 loathsome loathsome 4096 Sep 29 13:14 Program Files
drwxr-xr-x  6 loathsome loathsome 4096 Oct  6 20:02 Program Files (x86)
drwxr-xr-x  4 loathsome loathsome 4096 Sep 29 13:14 users
drwxr-xr-x 22 loathsome loathsome 4096 Oct  6 20:02 windows

Registry info:
/home/loathsome/.wine/system.reg:#arch=win64
/home/loathsome/.wine/userdef.reg:#arch=win64
/home/loathsome/.wine/user.reg:#arch=win64

warning: wine cmd.exe /c echo '%AppData%' returned empty string, error message "wine: WINEARCH is set to 'win32' but this is not supported in wow64 mode." 

Executing cd .

warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.

warning: You appear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this.

warning: winetricks is not a regular file, not checking sha256sum

Using winetricks 20250102 - sha256sum:  with wine-10.16 and WINEARCH=win64

[alessivs]

I'll have a look at this Wine development.

[alessivs]

[Hi. I was locked out due to 2FA requirements.]

After Wine 9, many distributions have adopted the build of Wine that enforces WoW64. The obvious solution is fixing the Wine version and edition.

In the meantime, you can build Wine yourself without this WoW64, enforcement, or rely on a alternative package provided by your distribution that keeps the 32bit pieces. It may be called wine32, lib32-wine or similar. It may also pull many 32 bit related libraries.

Regarding Lutris, the setup isn't thoroughly tested nor used by me for daily operation. It is something of an experiment that I didn't oversee (for example, the Wine runner specified in the recipe is no longer provided by Lutris). I glance from a distance, and notice that the more layers of abstraction over Wine, the more moving parts and reliance on less stable projects. For example, the suitable Lutris runner for SuperMemo Wine supported by Lutris right now is Wine-GE, which is available, but is no longer maintained and superseded by some other runner which more tightly integrates even more game-oriented patches.

The gaming focus of recent Wine developments, plus game-oriented patches, modify the behavior of Wine (beginning with skinning the classic UI theme, which often makes SM operation buggy and displeasing). In general, Wine after these game-oriented changes don't get much testing on application software, and when one does find and describe a problem with application software in a report, the Wine version is already no longer the current development version, or even not the current-stable.