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

[Bug 52607] New: build on Cygwin fails, error: undefined references to _alldiv, _allmul, _allrem, _aulldiv, _aullrem (etc.) in dlls/ntdll
by WineHQ Bugzilla April 17, 2026

April 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=52607 Bug ID: 52607 Summary: build on Cygwin fails, error: undefined references to _alldiv, _allmul, _allrem, _aulldiv, _aullrem (etc.) in dlls/ntdll Product: Wine Version: 7.3 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: blocker Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: saulius2(a)gmail.com (This is continuation from the bug 52606) After faking msxml3.dll, make then fails in dlls/ntdll: --- snip --- tools/winegcc/winegcc.exe -o dlls/ntdll/ntdll.dll --wine-objdir . -Wl,--disable-stdcall-fixup \ -fasynchronous-unwind-tables -shared dlls/ntdll/ntdll.spec -nodefaultlibs \ -Wl,--image-base,0x7bc00000 -mno-cygwin dlls/ntdll/actctx.o dlls/ntdll/atom.o dlls/ntdll/crypt.o \ dlls/ntdll/debugbuffer.o dlls/ntdll/env.o dlls/ntdll/error.o dlls/ntdll/exception.o \ dlls/ntdll/handletable.o dlls/ntdll/heap.o dlls/ntdll/large_int.o dlls/ntdll/loader.o \ dlls/ntdll/locale.o dlls/ntdll/math.o dlls/ntdll/misc.o dlls/ntdll/path.o dlls/ntdll/printf.o \ dlls/ntdll/process.o dlls/ntdll/reg.o dlls/ntdll/relay.o dlls/ntdll/resource.o dlls/ntdll/rtl.o \ dlls/ntdll/rtlbitmap.o dlls/ntdll/rtlstr.o dlls/ntdll/sec.o dlls/ntdll/signal_arm.o \ dlls/ntdll/signal_arm64.o dlls/ntdll/signal_i386.o dlls/ntdll/signal_x86_64.o dlls/ntdll/string.o \ dlls/ntdll/sync.o dlls/ntdll/thread.o dlls/ntdll/threadpool.o dlls/ntdll/time.o \ dlls/ntdll/version.o dlls/ntdll/wcstring.o dlls/ntdll/version.res dlls/winecrt0/libwinecrt0.a \ /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: ntdll.dll-621e0b58.spec.o:fake:(.edata+0x1270): undefined reference to `_alldiv' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: ntdll.dll-621e0b58.spec.o:fake:(.edata+0x1278): undefined reference to `_allmul' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: ntdll.dll-621e0b58.spec.o:fake:(.edata+0x1280): undefined reference to `_allrem' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: ntdll.dll-621e0b58.spec.o:fake:(.edata+0x1290): undefined reference to `_aulldiv' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: ntdll.dll-621e0b58.spec.o:fake:(.edata+0x1298): undefined reference to `_aullrem' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: dlls/ntdll/large_int.o:/home/saukrs/src/wine/dlls/ntdll/large_int.c:23: undefined reference to `_allrem' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: dlls/ntdll/large_int.o:/home/saukrs/src/wine/dlls/ntdll/large_int.c:30: undefined reference to `_alldiv' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: dlls/ntdll/large_int.o:/home/saukrs/src/wine/dlls/ntdll/large_int.c:55: undefined reference to `_aullrem' /usr/lib/gcc/i686-pc-cygwin/11/../../../../i686-pc-cygwin/bin/ld: dlls/ntdll/large_int.o:/home/saukrs/src/wine/dlls/ntdll/large_int.c:62: undefined reference to `_aulldiv' collect2: error: ld returned 1 exit status winegcc: /usr/bin/gcc.exe failed make: *** [Makefile:92389: dlls/ntdll/ntdll.dll] Error 2 --- snip --- -- 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 26226] New: msxml3 emits too much xmlns attributes
by wine-bugs＠winehq.org April 17, 2026

April 17, 2026

http://bugs.winehq.org/show_bug.cgi?id=26226 Summary: msxml3 emits too much xmlns attributes Product: Wine Version: 1.3.14 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msxml3 AssignedTo: wine-bugs(a)winehq.org ReportedBy: marcus(a)jet.franken.de When using www.wiso-kassenbuch.de initial registration checking fails (free download: http://update.buhl-finance.com/ESD/EUER%20und%20Kasse/WISO%20EUER%20und%20K… trial code is: EUR2011TRY ) reproduce: Start the installer, enter EUR2011TRY in the field below "Ihr AKtions-Code) and press "Weiter". It will then report a "400" error in a messagebox. The program sends a SOAP request to the on4u3.buhl.de server which is not accepted by the server (likely not validating against a stylesheet). I debugged this and using native MSXML3 it works, just our msxml3 will not. I tooked a debug dump of the XML sent of both, will attach both versions. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 54

[Bug 58673] New: Kinco Dtools fails to start: err:msxml:doparse Unsupported encoding: gb2312
by WineHQ Bugzilla April 17, 2026

April 17, 2026

http://bugs.winehq.org/show_bug.cgi?id=58673 Bug ID: 58673 Summary: Kinco Dtools fails to start: err:msxml:doparse Unsupported encoding: gb2312 Product: Wine Version: 10.14 Hardware: x86-64 URL: https://en.kinco.cn/download/download.html OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian This was program reported on the forum: https://forum.winehq.org/viewtopic.php?t=41565 It needs mfc42.dll and mfc140u.dll (via winetricks vcrun2019) but even after that installed, it fails to start with a vague error messagebox. After multiple "Unsupported encoding: gb2312" in the console The hack below allows it to start; might be easy to solve (???) for someone familiar with msxml? diff --git a/dlls/msxml3/main.c b/dlls/msxml3/main.c index 16e0b38b185..733a707cd31 100644 --- a/dlls/msxml3/main.c +++ b/dlls/msxml3/main.c @@ -322,6 +322,7 @@ static void init_char_encoders(void) } encoder[] = { { "gbk", gbk_to_utf8, utf8_to_gbk }, + { "gb2312", gbk_to_utf8, utf8_to_gbk }, { "iso8859-1", iso8859_1_to_utf8, utf8_to_iso8859_1 }, { "windows-1250", win1250_to_utf8, utf8_to_win1250 }, { "windows-1251", win1251_to_utf8, utf8_to_win1251 }, -- 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 13

[Bug 58392] New: Can't display background and characters in MapleStory World.
by WineHQ Bugzilla April 17, 2026

April 17, 2026

http://bugs.winehq.org/show_bug.cgi?id=58392 Bug ID: 58392 Summary: Can't display background and characters in MapleStory World. Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: s9209122222(a)gmail.com Distribution: --- If I upgrade to WINE10.9, the game can't display its background and characters. I have to downgrade to WINE10.8 to make it work again. -- 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 5

[Bug 58802] New: Inserting XML document fragment adds the fragment instead of its content.
by WineHQ Bugzilla April 17, 2026

April 17, 2026

http://bugs.winehq.org/show_bug.cgi?id=58802 Bug ID: 58802 Summary: Inserting XML document fragment adds the fragment instead of its content. Product: Wine Version: 9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: nerbs.dev(a)gmail.com Distribution: --- When MSXML's IXMLDOMDocumentFragment is inserted into the children of another node, the fragment's content should be inserted rather than the fragment node itself. When using Wine's MSXML3 implementation though, the fragment is inserted into the XML DOM hierarchy. As an example, inserting a fragment (represented here as an element with no name) like this: <> <child2 /> </> At the end of an element's children: <root> <child1 /> </root> Should produce this XML: <root> <child1 /> <child2 /> </root> But instead produces: <root> <child1 /> <> <child2 /> </> </root> I first noticed this while diagnosing some test failures for HexEdit while running under Wine 9.0, and then created a smaller reproduction of the issue. - Reproduction code: https://github.com/the-nerbs/wine-repros/tree/5f36fc0f493caf9972836f9630aae… - Built 32-bit repro exe: https://github.com/the-nerbs/wine-repros/blob/5f36fc0f493caf9972836f9630aae… - Original application code: https://github.com/the-nerbs/HexEdit The reproduction code exhibits the same issue when built as both 32 and 64 bit, running under Wine 9.0. I have also reproduced the issue on a 32-bit build of a fresh pull of the Wine sources. -- 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 5

[Bug 59415] New: In Falsus demo cannot be interacted with
by WineHQ Bugzilla April 17, 2026

April 17, 2026

http://bugs.winehq.org/show_bug.cgi?id=59415 Bug ID: 59415 Summary: In Falsus demo cannot be interacted with Product: Wine Version: 11.2 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: afifsworld132(a)gmail.com Created attachment 80384 --> http://bugs.winehq.org/attachment.cgi?id=80384 Game run with logging +win,+cursor,+event System: MacBook Pro M1 (2020), macOS 14.1.1, Wine Staging 11.2, DXMT 0.71 (I downgraded from 0.73 due to it having Shared Handle/Video issues) After the "Press any Key" part, the game cannot be interacted with at all. It is a UE6 game, so seeing the Player.log, only relevant lines seem to be: "<RI> Initializing input. EnableMouseInPointer failed with the following error: Call not implemented. Using Windows.Gaming.Input" Log is attached. -- 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 38350] New: FTDI Vinculum II IDE V2.0.2-SP2 gets OLE Error 80020006 on startup and exits
by wine-bugs＠winehq.org April 17, 2026

April 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=38350 Bug ID: 38350 Summary: FTDI Vinculum II IDE V2.0.2-SP2 gets OLE Error 80020006 on startup and exits Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skenton(a)ou.edu Distribution: --- The FTDI Vinculum II IDE for firmware development pops up an OLE error dialog and exits immediately after the splash screen is loaded at startup. Works fine on WindowsXP-SP3. Below is everything I thought might help. VinIDE (current version as of 2015Apr03) Download Vinculum II Toolchain V2.0.2-SP2 http://www.ftdichip.com/Firmware/vnc2toolchain/Vinculum%20II%20Installer%20… (popup) Vinculum II IDE OLE error 80020006 OK $ wine --version wine-1.7.38 $ wineconsole fixme:wincodecs:PngDecoder_Block_GetCount stub fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:msxml:domelem_setAttributeNode (0x14aaf0)->(0x14ac98 0x33f774): semi-stub $ uname -a Linux Cube 3.16.0-33-generic #44-Ubuntu SMP Thu Mar 12 12:19:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- 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 21

[Bug 58051] New: vbscript: Dictionary direct Keys/Items access causes parse error
by WineHQ Bugzilla April 17, 2026

April 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=58051 Bug ID: 58051 Summary: vbscript: Dictionary direct Keys/Items access causes parse error Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: francisdb(a)gmail.com Distribution: --- Example below Dim dict Set dict = CreateObject("Scripting.Dictionary") dict.Add "key1", 1 dict.Add "key2", 2 Dim i Dim keys: keys = dict.Keys() For i=0 To UBound(dict.Keys) Wscript.Echo i Wscript.Echo keys(i) Wscript.Echo dict.Keys()(i) '<- parser error 'Same for Items Next /opt/wine-devel/bin/wine cscript test.vbs 0138:fixme:vbscript:parser_error L"(i) '<- parser error\r\n 'Same for Items\r\nNext": "syntax error" 0138:fixme:wscript:ActiveScriptSite_OnScriptError () 0138:fixme:wscript:run_script ParseScriptText failed: 80004005 -- 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 54291] New: vbscript stuck in endless for loop when UBound on Empty and On Error Resume Next
by WineHQ Bugzilla April 17, 2026

April 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=54291 Bug ID: 54291 Summary: vbscript stuck in endless for loop when UBound on Empty and On Error Resume Next Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: jsm174(a)gmail.com Distribution: --- I ran across some code similar to the following: WScript.echo "Start" Dim ii Dim tmp Dim vpmMultiLights() : ReDim vpmMultiLights(0) On Error Resume Next For Each tmp In vpmMultiLights For ii = 1 To UBound(tmp) : tmp(ii).State = tmp(0).State : Next Next On Error Goto 0 WScript.echo "Done" In real vbscript, the result is: Start Done In wine vbscript, this code will get stuck in an endless loop. To work around this I hacked UBound to return 0 with VT_EMPTY, but I think real vbscript treats this differently. -- 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 9

[Bug 54344] New: simtower (setup.exe) says could not open the file name "h:\wine64....."
by WineHQ Bugzilla April 17, 2026

April 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=54344 Bug ID: 54344 Summary: simtower (setup.exe) says could not open the file name "h:\wine64....." Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: elias_0000_0000(a)yahoo.com Distribution: --- simtower (setup.exe) says could not open the file name "h:\wine64....." setup.exe tries to expand the files, but it says the above message. What i must do? I downloaded expand.exe to expand files in dosbox by hand but it takes 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.

2 8