March 2026 - Wine-Bugs - list.winehq.org

[Bug 59384] New: Legacy Family Tree random crash
by WineHQ Bugzilla March 7, 2026

March 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=59384 Bug ID: 59384 Summary: Legacy Family Tree random crash Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: mice(a)duck.com Distribution: --- Created attachment 80337 --> http://bugs.winehq.org/attachment.cgi?id=80337 Crash backtrace file This crash happens at random times when using the application. Unable to reproduce as many operations work normally for most of the time. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 39766] New: StarMoney: problem with XML HTTP 4.0 in msxml4
by wine-bugs＠winehq.org March 7, 2026

March 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=39766 Bug ID: 39766 Summary: StarMoney: problem with XML HTTP 4.0 in msxml4 Product: Wine Version: 1.1.34 Hardware: x86 URL: http://www.starmoney.de/index.php?id=starmoney_testen OS: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- Created attachment 53046 --> https://bugs.winehq.org/attachment.cgi?id=53046 terminal output I tried the latest version of the app from bug 21053: austin(a)austin1:~$ sha1sum smoney.exe f35721a185b0d9d6a93826a2ba92cf0da6780b43 smoney.exe austin(a)austin1:~$ du -h smoney.exe 228M smoney.exe But I do not get the bug that Alistair mentions. Instead, the installer runs for me and I evntually get a MSVC error dialog and an msi error in the terminal: err:msi:ACTION_CallDllFunction GetProcAddress(L"GetWebInfo") failed Before installation, I'm running winetricks dotnet40 win7 There's a winediag error about missing odbc drivers, but jet40 and mdac28 don't help. Terminal output has a ton of fixme:ole:NdrCorrelation* FIXMEs removed to reduce size from 10MB -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 57536] New: Windows program "Starmoney" cant be installed
by WineHQ Bugzilla March 7, 2026

March 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=57536 Bug ID: 57536 Summary: Windows program "Starmoney" cant be installed Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ps1304(a)fn.de Distribution: --- Created attachment 77604 --> https://bugs.winehq.org/attachment.cgi?id=77604 log created by wine during installation of a required component for Starmony "Microsoft Edge Webview2 Runtime" wine is creating an error; see file for details. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 17

[Bug 49686] New: StarMoney 12 Basic doesn't start up
by WineHQ Bugzilla March 7, 2026

March 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=49686 Bug ID: 49686 Summary: StarMoney 12 Basic doesn't start up Product: Wine Version: 5.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 67926 --> https://bugs.winehq.org/attachment.cgi?id=67926 Console Output (wine 5.14 - Staging) Hello everyone, as somebody on the ubuntuusers.de requested some help for the application I gave "StarMoney12 Basic" a try which can be downloaded from: https://hilfe.starmoney.de/hc/de/articles/360018689873-StarMoney-herunterla… I used the 5.14 staging version of wine but with no luck as it seems to hang in a deadlock. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 36686] New: CodeGear RAD Studio 2009 fails on startup (ISAXXMLReader::putFeature method needs to support 'normalize line breaks' feature)
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=36686 Bug ID: 36686 Summary: CodeGear RAD Studio 2009 fails on startup (ISAXXMLReader::putFeature method needs to support 'normalize line breaks' feature) Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says ... Prerequisite: 'winetricks -q mdac28' .NET Framework 2.0 will be automatically installed if required. --- snip --- $ WINEDEBUG=+tid,+seh,+loadll,+process,+msxml,+msgbox wine ./bds.exe ... 0009:trace:msxml:DllGetClassObject {079aa557-4a18-424a-8eee-e39f0a8d41b9} {00000001-0000-0000-c000-000000000046} 0x33f6c8 0009:trace:msxml:DOMClassFactory_AddRef (0x525df98) ref = 1 0009:trace:msxml:DOMClassFactory_CreateInstance (nil) {a4f96ed0-f829-476e-81c0-cdc7bd2a0802} 0x7cd5f4 0009:trace:msxml:SAXXMLReader_create (0x33f64c) 0009:trace:msxml:SAXXMLReader_create returning iface 0x52542b4 0009:trace:msxml:saxxmlreader_QueryInterface 0x52542a8 {a4f96ed0-f829-476e-81c0-cdc7bd2a0802} 0x7cd5f4 0009:trace:msxml:saxxmlreader_AddRef 0x52542a8 0009:trace:msxml:saxxmlreader_Release 0x52542a8 0009:trace:msxml:DOMClassFactory_Release (0x525df98) ref = 0 0009:trace:msxml:isaxxmlreader_putFeature (0x52542a8)->(L"http://xml.org/sax/features/namespaces" 1) 0009:trace:msxml:isaxxmlreader_putFeature (0x52542a8)->(L"http://xml.org/sax/features/namespace-prefixes" 1) 0009:trace:msxml:isaxxmlreader_putFeature (0x52542a8)->(L"http://xml.org/sax/features/external-general-entities" 0) 0009:trace:msxml:isaxxmlreader_putFeature (0x52542a8)->(L"http://xml.org/sax/features/external-parameter-entities" 0) 0009:trace:msxml:isaxxmlreader_putFeature (0x52542a8)->(L"normalize-line-breaks" 1) 0009:fixme:msxml:isaxxmlreader_putFeature (0x52542a8)->(L"normalize-line-breaks" 1) stub 0009:trace:seh:raise_exception code=eedfade flags=1 addr=0x7b83ac57 ip=7b83ac57 tid=0009 0009:trace:seh:raise_exception info[0]=5005eb21 0009:trace:seh:raise_exception info[1]=00e77898 0009:trace:seh:raise_exception info[2]=80004001 0009:trace:seh:raise_exception info[3]=208e3a14 0009:trace:seh:raise_exception info[4]=007cd5f0 0009:trace:seh:raise_exception info[5]=0033f71c 0009:trace:seh:raise_exception info[6]=0033f6e8 0009:trace:seh:raise_exception eax=7b826c7d ebx=7b8bb000 ecx=0033f6e8 edx=0033f660 esi=00000001 edi=00000007 0009:trace:seh:raise_exception ebp=0033f688 esp=0033f624 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000283 --- snip --- 'winetricks -q msxml3' works around. $ wine --version wine-1.7.19-70-gd6a59f7 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

3 8

[Bug 59449] New: FormatMessageW fails for well-formed function call and crashes application
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59449 Bug ID: 59449 Summary: FormatMessageW fails for well-formed function call and crashes application Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: and44more(a)gmail.com Distribution: --- Created attachment 80433 --> http://bugs.winehq.org/attachment.cgi?id=80433 C++ code to demonstrate it This isn't really a bug, but more a missing error message. The FormatMessageW (winbase.h) function fails if given the valid error code CRYPT_E_NO_MATCH as an argument (see attached code snippet). It returns 0 indicating an error and does not modify the lpBuffer pointer argument. Applications that assume that FormatMessageW will allocate the error message at the memory address lpBuffer is pointing to will crash (like in my case) if they initalized lpBuffer with 0 before. Technically, this is the fault of the application since it assumed that FormatMessageW will not return an error if given a well-formed function call, but wine is missing the error message in the first place and that should be fixed. I'd also like to propose setting lpBuffer to a pointer to an empty string (null character) instead of not modifying it when FormatMessageW fails. (Create a global empty string variable instead of allocating memory each time). This behavior would adhere to the FormatMessageW documentation and would make applications with missing error checks more fail safe in this case. I'm using linux mint 22.1 with wine 9.0, but I also tested the attached code snippet in linux arch with wine 11.1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 59329] New: Erratic behavior of std::rethrow_exception() with DLL runtime
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59329 Bug ID: 59329 Summary: Erratic behavior of std::rethrow_exception() with DLL runtime Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ucrtbase Assignee: wine-bugs(a)list.winehq.org Reporter: p(a)perkele.cc Distribution: --- Created attachment 80262 --> http://bugs.winehq.org/attachment.cgi?id=80262 Minimal repro code I have observed various erratic behaviors after use of std::rethrow_exception() in my programs - either crashing or incorrect exception caught. Using DLL or static runtime seems to be a factor - using static runtime instead results in correct behavior for me. Compile and run attached program to test - verified with all Visual Studio versions from 2017 up. Live repro using mainstream software: Install any recent version of foobar2000, switch audio output to any of [exclusive] options, try playing anything - should say "Exclusive mode not allowed", says "Unknown exception" instead. Confirmed on: Fedora 43 / x86_64 / Wine 11.1 macOS 26.2 / ARM host running emulated x86_64 code / Wine 11.0 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 55739] New: Native Access 2: permanent loading circle after entering credentials
by WineHQ Bugzilla March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=55739 Bug ID: 55739 Summary: Native Access 2: permanent loading circle after entering credentials Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dominikgx(a)gmail.com Distribution: --- Downloaded latest Native Access and entering credentials https://appdb.winehq.org/objectManager.php?sClass=version&iId=41061 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 59462] New: wine-staging fails to build due to unable to find -lvkd3d
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59462 Bug ID: 59462 Summary: wine-staging fails to build due to unable to find -lvkd3d Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: neotheuser(a)ymail.com Distribution: --- Using the llvm-mingw64 toolchain, I am unable to build Wine using the wine-staging patches. Short build log: tools/winegcc/winegcc -o dlls/wined3d/i386-windows/wined3d.dll --wine-objdir . --cc-cmd="i686-w64-mingw32-clang" -b i686-w64-mingw32 \ -Wl,--wine-builtin -shared ../dlls/wined3d/wined3d.spec dlls/wined3d/i386-windows/adapter_gl.o \ ... [ cut ] ... -lvkd3d libs/dxguid/i386-windows/libdxguid.a dlls/opengl32/i386-windows/libopengl32.a \ tools/winegcc/winegcc -o dlls/wined3d/x86_64-windows/wined3d.dll --wine-objdir . --cc-cmd="x86_64-w64-mingw32-clang" -b \ ... [ cut ] ... dlls/wined3d/resource.res dlls/wined3d/version.res -lvkd3d libs/dxguid/x86_64-windows/libdxguid.a \ ... [ cut ] ... lld: error: unable to find library -lvkd3d clang: error: linker command failed with exit code 1 (use -v to see invocation) ... [ cut ] ... lld: error: unable to find library -lvkd3d winegcc: /home/fedora/dev/llvm-mingw-20251216-ucrt-ubuntu-22.04-x86_64/bin/i686-w64-mingw32-clang failed clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [Makefile:176705: dlls/wined3d/i386-windows/wined3d.dll] Error 2 make: *** Waiting for unfinished jobs.... winegcc: /home/fedora/dev/llvm-mingw-20251216-ucrt-ubuntu-22.04-x86_64/bin/x86_64-w64-mingw32-clang failed make: *** [Makefile:176754: dlls/wined3d/x86_64-windows/wined3d.dll] Error 2 I noticed the following: fedora@fedora:~/dev/wine$ ld.lld -lvkd3d ld.lld: error: unable to find library -lvkd3d fedora@fedora:~/dev/wine$ ld.lld -L/usr/lib64 -lvkd3d ld.lld: warning: cannot find entry symbol _start; not setting start address However, adding -L/usr/lib64 to LDFLAGS and even modifying the Makefile within the build directory and forcefully adding it behind `-lvkd3d` the issue still persists and I have no idea how to fix this. Wine from latest `master` branch compiles fine, however Wine with wine-staging (--all specified, all staging patches, fails, not sure which patch yet is the culprit) Toolchain location: https://github.com/mstorsjo/llvm-mingw/releases/tag/20251216 configure line: ../configure CC="clang" CXX="clang++" CPP="clang-cpp" i386_CC="i686-w64-mingw32-clang" i386_CXX="i686-w64-mingw32-clang++" x86_64_CC="x86_64-w64-mingw32-clang" x86_64_CXX="x86_64-w64-mingw32-clang++" --enable-archs=i386,x86_64 --disable-tests --prefix=/home/fedora/wine-out I have not yet tried to build wine-staging with GCC+BFD linker yet. This is Fedora 43. Package relevant files installed from libvkd3d-devel (installed both 32-bit and 64-bit devel packages): /usr/include/vkd3d/vkd3d.h /usr/lib64/libvkd3d.so /usr/lib64/pkgconfig/libvkd3d.pc /usr/lib/libvkd3d.so /usr/lib/pkgconfig/libvkd3d.pc -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 59342] New: Roblox Studio crashes when typing ASCII symbols in search bar of "Find in Place" window when RegEx is enabled
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59342 Bug ID: 59342 Summary: Roblox Studio crashes when typing ASCII symbols in search bar of "Find in Place" window when RegEx is enabled Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: eff3ctsb0t(a)gmail.com Distribution: --- Created attachment 80281 --> http://bugs.winehq.org/attachment.cgi?id=80281 Wine debugging log When typing symbols like brackets or question marks inside of the search bar of the "Find in Place" window while having RegEx enabled, Roblox Studio crashes. Wine complains about an unimplemented function within the msvcp140.dll library inside of the debugging log. It is also noteworthy that some ASCII symbols like exclamation marks do not cause a crash. Steps to reproduce: 1. Open a Baseplate template inside of Roblox Studio. 2. Enable the "Find in Place" window by going through the "Window" menu at the top, then through "Script" and then click on "Find in Place". 3. Enable RegEx (.*) inside of the newly spawned window and then type ")" into the search bar of said window. A Wine wrapper program called "Vinegar" can be used to make the process of setting up Roblox Studio a lot easier. Logging into Roblox Studio (and by extension opening a Baseplate) requires a Roblox account though. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 11