September 2025 - Wine-Bugs - list.winehq.org

[Bug 50418] New: ArcGIS Pro fails to launch with wine-mono
by WineHQ Bugzilla Nov. 27, 2025

Nov. 27, 2025

https://bugs.winehq.org/show_bug.cgi?id=50418 Bug ID: 50418 Summary: ArcGIS Pro fails to launch with wine-mono Product: Wine Version: 6.0-rc4 Hardware: x86-64 URL: http://data.wvgis.wvu.edu/SecureFTP/securedownload/arc /ArcGIS%20Pro/ArcGISPro_22_163783.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Unhandled Exception: System.InvalidProgramException: Invalid IL code in ActiproSoftware.Windows.Controls.Ribbon.UI.RibbonMeasurements:set_BackstageTabWidth (double): IL_0002: stsfld 0x04000137 at ArcGIS.Desktop.Framework.FrameworkApplication..ctor () [0x00169] in <a27482abd44f4054a15c91c81cd4a531>:0 at ArcGIS.Desktop.Core.ProApp..ctor () [0x00012] in <5f84b0450bdb4a808e04ab6ef46dd283>:0 at <Module>.main (System.String[] args) [0x00000] in <bb19de946d75458385874ec2b780dbb5>:0 I haven't tried debugging yet. -- 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 1

[Bug 24963] New: Okad2: Unhandled page fault at address 0x00007f8a during startup
by wine-bugs＠winehq.org Nov. 26, 2025

Nov. 26, 2025

http://bugs.winehq.org/show_bug.cgi?id=24963 Summary: Okad2: Unhandled page fault at address 0x00007f8a during startup Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: pandolfo(a)gis.net Created an attachment (id=31617) --> (http://bugs.winehq.org/attachment.cgi?id=31617) a description of the page fault plus an annotated backtrace During program startup, Okad2-xx-pd (xx = version) generates an unhandled page fault when loading an icon. The page fault is caused by CreateFileW as it processes the name of the file from the parameter list. The name pointer is 0x00007f8a, which is an address in an unmapped page. This value is also an index into Windows resources, selecting the hourglass icon. What has happened is that the application was attempting to load the hourglass icon and passed in BOTH the Windows resource index and a flag indicating LOADFROMFILE. Wine attempted to load-from-file and looked for the file name through the "name" parameter (0x00007f8a) generating the page fault. Native Windows appears to give the value of the "name" pointer precedence and determines that the "name" parameter is actually a resource number; hence it does not page fault and runs Okad2 normally. Wine *DOES* check the "name" parameter to see if it is a resource index, but several subroutine calls later it forgets this fact and branches based on the LOADFROMFILE bit. The backtrace has been annotated to provide both a description and source lines involved in the decision. This behavior was found in the latest version of Wine for Debian (.1.42) and in a MacOS X version. -- 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.

2 17

[Bug 57838] New: it just wont load the app
by WineHQ Bugzilla Nov. 26, 2025

Nov. 26, 2025

https://bugs.winehq.org/show_bug.cgi?id=57838 Bug ID: 57838 Summary: it just wont load the app Product: Wine Version: unspecified Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sifato6092(a)owlny.com Created attachment 78053 --> https://bugs.winehq.org/attachment.cgi?id=78053 backtrace it just wont load the app i useing -- 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 54352] New: Performance tanks when looking at occluded part of the level
by WineHQ Bugzilla Nov. 25, 2025

Nov. 25, 2025

https://bugs.winehq.org/show_bug.cgi?id=54352 Bug ID: 54352 Summary: Performance tanks when looking at occluded part of the level Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: mirh(a)protonmail.ch https://github.com/doitsujin/dxvk/issues/1845 This is basically the equivalent of the missed optimization I had already reported to dxvk (except wined3d had like half the framerate to begin with). With the native nvidia d3d9 driver, you barely can spot a difference in the Mass Effect comm room between looking at the emptiest wall in human history, or the closed door behind that gives access to the rest of the ship. With wined3d, I go from like 220fps to ~70. Btw there's an apitrace in the thread above, if it can help. -- 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 2

[Bug 53819] New: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog
by WineHQ Bugzilla Nov. 25, 2025

Nov. 25, 2025

https://bugs.winehq.org/show_bug.cgi?id=53819 Bug ID: 53819 Summary: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- So, I've stumbled upon a Unity engine game that crashes every now and then due to what seems to be virtual mapping space exhaustion. Not sure about the crash itself - it's more likely to be graphics related that winegstreamer, but that's just a guess. Anyway, once the crash happens, console is flooded by: 03b0:err:module:DelayLoadFailureHook failed to delay load uxtheme.dll.GetWindowTheme wine: Call from 7B0123C6 to unimplemented function uxtheme.dll.GetWindowTheme, aborting 03b0:err:seh:KiUserCallbackDispatcher ignoring exception and the Unity crash dialog doesn't display properly. -- 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 56447] New: PlayOnline Viewer: The "splash screen" is blank/grey without its image.
by WineHQ Bugzilla Nov. 23, 2025

Nov. 23, 2025

https://bugs.winehq.org/show_bug.cgi?id=56447 Bug ID: 56447 Summary: PlayOnline Viewer: The "splash screen" is blank/grey without its image. Product: Wine Version: 9.4 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Distribution: Gentoo This is a very old one, but as far as I can tell, not reported until now (aside from some side-mentions). PlayOnline Viewer, which is used to launch Final Fantasy XI Online, has a blank/grey window for its "splash screen". It has been working in Wine Staging for some time. Not sure if related, but comparing the logging between runs, each of these show up twice with Vanilla but only once with Staging: err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x1, ret 0x4. err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x2, ret 0x4. -- 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 3

[Bug 46568] New: 64-bit msxml6.dll from Microsoft Core XML Services 6.0 redist package fails to load (Wine doesn't respect 44-bit user-mode VA limitation from Windows < 8.1)
by wine-bugs＠winehq.org Nov. 22, 2025

Nov. 22, 2025

https://bugs.winehq.org/show_bug.cgi?id=46568 Bug ID: 46568 Summary: 64-bit msxml6.dll from Microsoft Core XML Services 6.0 redist package fails to load (Wine doesn't respect 44-bit user-mode VA limitation from Windows < 8.1) Product: Wine Version: 4.0 Hardware: x86-64 URL: https://download.microsoft.com/download/2/e/0/2e01308a -e17f-4bf9-bf48-161356cf9c81/msxml6_x64.msi OS: Linux Status: NEW Keywords: download, win64 Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, reported by Louis in https://bugs.winehq.org/show_bug.cgi?id=46107#c2 --- quote --- I tried winetricks msxml3 and msxml6, but somehow it didn`t work out in 64-bit wineprefix; i get errors that msxml is not registered etc, Does anyone know a workaround to use native msxml on 64-bit prefix? --- quote --- Relevant part of trace log: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Altium/AD18 $ WINEDEBUG=+seh,+relay,+loaddll,+virtual wine64 ./X2.EXE >>log.txt 2>&1 ... 002a:Call KERNEL32.LoadLibraryExW(0053f2b0 L"C:\\windows\\system32\\msxml6.dll",00000000,00000008) ret=7fbe435d7558 ... 002a:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\msxml6.dll" at 0x7ff79e00000: native 002a:Call PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_ATTACH,res=(nil)) ... 002a:Call KERNEL32.HeapCreate(00000001,00000000,00000000) ret=7ff79e18411 002a:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00110000 2000 00000004 002a:trace:virtual:map_view got mem with anon mmap 0x7fbe39819000-0x7fbe39929000 002a:trace:virtual:VIRTUAL_DumpView View: 0x7fbe39820000 - 0x7fbe3992ffff (valloc) 002a:trace:virtual:VIRTUAL_DumpView 0x7fbe39820000 - 0x7fbe3992ffff --rw- 002a:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff 0x7fbe39820000 00010000 1000 00000004 002a:trace:virtual:mprotect_exec forcing exec permission on 0x7fbe39820000-0x7fbe3982ffff 002a:trace:virtual:VIRTUAL_DumpView View: 0x7fbe39820000 - 0x7fbe3992ffff (valloc) 002a:trace:virtual:VIRTUAL_DumpView 0x7fbe39820000 - 0x7fbe3982ffff c-rw- 002a:trace:virtual:VIRTUAL_DumpView 0x7fbe39830000 - 0x7fbe3992ffff --rw- 002a:Ret KERNEL32.HeapCreate() retval=7fbe39820000 ret=7ff79e18411 ... 002a:Call ntdll.RtlAllocateHeap(7fbe39820000,00000000,00000060) ret=7ff79e03c10 002a:Ret ntdll.RtlAllocateHeap() retval=7fbe39822730 ret=7ff79e03c10 002a:Call msvcrt.memset(7fbe39822740,00000000,00000042) ret=7ff79e03a5a 002a:Ret msvcrt.memset() retval=7fbe39822740 ret=7ff79e03a5a 002a:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x7ff79e03efe ip=7ff79e03efe tid=002a 002a:trace:seh:NtRaiseException info[0]=0000000000000000 002a:trace:seh:NtRaiseException info[1]=ffffffffffffffff 002a:trace:seh:NtRaiseException rax=000000000011b2d0 rbx=6c61567274736270 rcx=0000000000000008 rdx=0000000000000000 002a:trace:seh:NtRaiseException rsi=0000000000007fbe rdi=0000000000000730 rbp=00000ff7c73044e8 rsp=000000000053ea70 002a:trace:seh:NtRaiseException r8=00007fbe39822740 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 002a:trace:seh:NtRaiseException r12=00007fbe39822740 r13=000007ff79f8dc80 r14=00007fbe436c6160 r15=000000000053f708 ... 002a:exception c0000005 in PE entry point (proc=0x7ff79e0101c,module=0x7ff79e00000,reason=PROCESS_ATTACH,res=(nil)) 002a:Ret PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_ATTACH,res=(nil)) retval=0 002a:Call PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_DETACH,res=(nil)) 002a:Ret PE DLL (proc=0x7ff79e0101c,module=0x7ff79e00000 L"msxml6.dll",reason=PROCESS_DETACH,res=(nil)) retval=1 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\msxml6.dll" : native 002a:Ret KERNEL32.LoadLibraryExW() retval=00000000 ret=7fbe435d7558 002a:err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\\windows\\system32\\msxml6.dll" --- snip --- It seems that certain older 64-bit components such as Microsoft XML libs make assumptions about the 64-bit user-mode virtual address space layout. This is different from the usual broken apps a la "I failed at porting my 32-bit app to 64-bit" (pointer truncation). In this case, pointers from certain allocations are broken into multiple parts and used as indices into multi-level lookup tables. Pitfall: there is a 44-bit user-mode VA limitation (8TB) for 64-bit Windows which was lifted starting with Windows 8.1+. Wine doesn't respect the 44-bit pre-Windows 8.1 virtual address space limits, allowing process heaps to be placed in 0000'7Fxx'0000'0000 range (128 TB) which causes out-of-bounds access to lookup tables when indices overflow (derived from pointer bits). The exception occurs in entry point, causing 'msxml6.dll' to be unloaded. One workaround is to move Wine's top-down allocations/heaps into 8 TB VA range (Wine preloader) and impose same user-mode address space bits limits as with all 64-bit Windows versions < 8.1 to stay "compatible". I've tested it and it works for native here. Not sure if it's worth to change though. I don't know if a separate 64-bit MSXML6 re-distributable package exists that has been fixed wrt Windows 8.1+ address space limits. MSXML6 is part of Windows OS for newer versions and automatically kept up-to-date. $ sha1sum msxml6_x64.msi 1eb84eeae7729ea5db7fe79779f4e216114261ba msxml6_x64.msi $ du -sh msxml6_x64.msi 2.6M msxml6_x64.msi $ wine --version wine-4.0-276-g84459ba94b 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.

2 17

[Bug 54455] New: CodeMeterRuntime: Install fails with '00c4:err:service:process_send_command service protocol error - failed to write pipe!'
by WineHQ Bugzilla Nov. 20, 2025

Nov. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=54455 Bug ID: 54455 Summary: CodeMeterRuntime: Install fails with '00c4:err:service:process_send_command service protocol error - failed to write pipe!' Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irmin.okic(a)gmail.com Distribution: --- Created attachment 74012 --> https://bugs.winehq.org/attachment.cgi?id=74012 Terminal output of the installer. Steps to reproduce: * Install dotnet48 into the prefix with winetricks. * Download CodeMeterRuntime 64bit 7.60 (but earlier versions had the same error) for Windows from: https://www.wibu.com/us/support/user/downloads-user-software.html * Execute the installer. * To reduce complexity in the installer on the Custom Setup step select "don't install" for all components except "CodeMeter Runtime Kit". I.e. "don't install" for Network Server, WibuShellExtension, User Help, Automatic server search, Remote access to WebAdmin. * Finish the installation. The installer will state that it ended prematurely. The relevant errors are probably: 00c4:err:service:process_send_command service protocol error - failed to write pipe! 016c:err:msi:ITERATE_StartService failed to start service L"CmWebAdmin.exe" (1053) 016c:err:msi:execute_script Execution of script 0 halted; action L"StartServices" returned 1627 016c:err:msi:ITERATE_Actions Execution halted, action L"InstallExecute" returned 1627 In Wine 7 I ignored the installer error with the following arguments to the installer: /ComponentArgs "*":"/qn ADDLOCAL=Complete,DotNET_Modules,AutomaticServerSearch REMOVE=WibuShellExtension,EnableNetworkServer,AccessToWebAdmin /l*v C:\users\z0rb\Temp\keyinst.log /norestart DISABLEROLLBACK=1 PROP_CMCC=\"none\"" The important argument was DISABLEROLLBACK=1. This meant that I can keep the install even with the failure. Then run CodeMeterCC.exe which started the CodeMeter windows service. With that service I could use further software that uses CodeMeter as their licensing service. In wine 8 even that service (together with CmWebAdmin.exe) started having the "failed to write pipe error!". I am out of workarounds at the moment and asking here for help. If you can instruct me with further debug flags and similar to narrow down the error I am ready to put in the work. -- 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 2

[Bug 56739] New: Alchemy is rotated 90°
by WineHQ Bugzilla Nov. 20, 2025

Nov. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=56739 Bug ID: 56739 Summary: Alchemy is rotated 90° Product: Wine Version: 9.8 Hardware: x86-64 URL: https://alchemy.software.informer.com/download/ OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: zzhang(a)codeweavers.com Regression SHA1: 4a330b29212402b9700828be82939112bd11a786 Distribution: Ubuntu Created attachment 76518 --> https://bugs.winehq.org/attachment.cgi?id=76518 Screenshot The game Alchemy is rotated 90°. A bisect points to: 4a330b29212402b9700828be82939112bd11a786 is the first bad commit commit 4a330b29212402b9700828be82939112bd11a786 Author: Zhiyi Zhang Date: Tue Sep 22 15:02:24 2020 +0800 winex11.drv: Support display orientations for XRandR 1.4 display settings handler. Running in an emulated desktop works around this. https://alchemy.software.informer.com/download/ $ sha1sum alchemysetup-en.exe 2fa2bd427e79b7fb585d090891ae368b0cea0156 alchemysetup-en.exe $ xrandr --version xrandr program version 1.5.1 Server reports RandR version 1.6 -- 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 7

[Bug 58099] New: PKHeX crashing
by WineHQ Bugzilla Nov. 20, 2025

Nov. 20, 2025

http://bugs.winehq.org/show_bug.cgi?id=58099 Bug ID: 58099 Summary: PKHeX crashing Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tw0ali(a)tutanota.com Distribution: --- Created attachment 78355 --> http://bugs.winehq.org/attachment.cgi?id=78355 Crashing logs PKHeX (https://projectpokemon.org/home/files/file/1-pkhex/) used to work fine until version 10.2 of Wine. Starting with version 10.3 (and up until 10.5 as of now) it crashes when launching it. The program needs .NET Desktop Runtime 9. I installed it with Winetricks. -- 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 12