[Bug 57416] New: xEdit Bethesda Modding Tool Crashes under Wine-9.21

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57416

Bug ID: 57416
           Summary: xEdit Bethesda Modding Tool Crashes under Wine-9.21
           Product: Wine
           Version: 9.21
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 77401
  --> https://bugs.winehq.org/attachment.cgi?id=77401
Wine-9.21 Output Log

Problem:

xEdit crashes under Wine 9.21 and prevents basic usage of the app for use with
Bethesda games.

Download location:
https://github.com/TES5Edit/TES5Edit/releases/tag/xedit-4.1.5f

-----

Reproduction Steps:

1) Install a Bethesda game (in my case, I installed Oblivion from GOG using
Heroic and with the system-installed Wine version)
    2) cd to where xEdit is downloaded (download it, of course)
    3) Depending on the game, change all references to "xEdit" to the specific
game being used by renaming the executables (in this case, it would be
"TES4Edit" instead)
    4) Run: WINEPREFIX="/path/to/prefix" WINEARCH="win64" winecfg (then click
okay / closer the window after adding a wincfg entry for xEdit to run in WinXP
mode)
    5) Run the game launcher once using that prefix, open the game, then close
it (assuming the launcher doesn't have "Play" greyed out; it was for me, so I
closed the launcher then launched the game directly)
    6) Run: WINEPREFIX="/path/to/prefix" WINEARCH="win64" wine start
./TES4Edit64.exe -D "Z:\path\to\game\folder\Data" ("Data" is an actual folder
named that)
    7) xEdit Crashes with a runtime error

Note: If you specifically run the 64-bit executable it'll give a message about
considering using the 32-bit mode for speed, and interacting with that message
box works, but it will proceed to crash afterwards.

Running the program without any arguments instead throws an error about there
being a missing registry entry for the game, but the program doesn't crash if
doing this. Normally, this would be to detect the game location, but xEdit was
made for the Steam version in mind in this regard, which is why this separate
error is thrown.

Performing a similar process using Mod Organizer in conjunction​ makes no
difference as the results are the same.