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

[Bug 51004] New: Dead Rising 2 crashes on launch with Vulkan renderer
by WineHQ Bugzilla Jan. 9, 2026

Jan. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=51004 Bug ID: 51004 Summary: Dead Rising 2 crashes on launch with Vulkan renderer Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 04cc:fixme:d3d_shader:shader_spirv_compile Shader log: 04cc:fixme:d3d_shader:shader_spirv_compile <anonymous>: E0002: Invalid DXBC magic. 04cc:fixme:d3d_shader:shader_spirv_compile 04cc:err:d3d_shader:shader_spirv_compile Failed to compile DXBC, ret -3. 04cc:err:d3d:wined3d_context_vk_apply_draw_state No pipeline layout set. 04cc:err:d3d:adapter_vk_draw_primitive Failed to apply draw state. 0490:err:winediag:wined3d_texture_init The application tried to create a DXTn texture, but the driver does not support them. wine-6.6-115-g092c7a09a5a -- 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 1

[Bug 58878] New: Norwegian version of "Who Wants To Be A Millionaire" did not works
by WineHQ Bugzilla Jan. 8, 2026

Jan. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=58878 Bug ID: 58878 Summary: Norwegian version of "Who Wants To Be A Millionaire" did not works Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lars_martin4(a)hotmail.com Distribution: --- larsmartinhambro(a)fedora-linux:~/.wine/drive_c/Program Files (x86)/Eidos Interactive/HotHouse Creations/Vil Du Bli Millionær$ dir BINKW32.DLL Data Game.exe SMACKW32.DLL Viktig.rtf larsmartinhambro(a)fedora-linux:~/.wine/drive_c/Program Files (x86)/Eidos Interactive/HotHouse Creations/Vil Du Bli Millionær$ wine Game.exe 002c:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0090:err:environ:init_peb starting L"C:\\Program Files (x86)\\HDD Health\\HDDHealthService.exe" in experimental wow64 mode 0090:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented! 00c8:err:environ:init_peb starting L"C:\\Program Files (x86)\\ASUS\\AXSP\\4.00.38\\atkexComSvc.exe" in experimental wow64 mode 00c8:fixme:ole:CoInitializeSecurity 00000000, -1, 00000000, 00000000, 6, 3, 00000000, 2, 00000000 stub 00c8:fixme:wbemprox:client_security_SetBlanket 79273934, 00C145B8, 10, 0, (null), 4, 3, 00000000, 0 00c8:fixme:wbemprox:client_security_Release 79273934 00c8:fixme:wbemprox:client_security_Release 79273934 00c8:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x10 wine: Unhandled page fault on read access to 00000000 at address 793A43CD (thread 00c8), starting debugger... 00d0:err:environ:init_peb starting L"C:\\windows\\syswow64\\winedbg.exe" in experimental wow64 mode 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0070:err:ole:start_rpcss Failed to start RpcSs service 00e4:err:ole:start_rpcss Failed to start RpcSs service 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0070:err:ole:start_rpcss Failed to start RpcSs service 003c:err:service:process_send_start_message service L"asComSvc" failed to start 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"asComSvc" failed to start: 1053 0100:err:environ:init_peb starting L"C:\\windows\\syswow64\\winedevice.exe" in experimental wow64 mode 010c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys" 010c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys" 010c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys" 0108:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 014c:err:environ:init_peb starting L"C:\\Program Files (x86)\\Electronic Arts\\Medal of Honor Airborne\\UnrealEngine3\\MOHAGame\\pb\\PnkBstrA.exe" in experimental wow64 mode 0024:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 01e4:err:environ:init_peb starting L"C:\\Program Files (x86)\\Eidos Interactive\\HotHouse Creations\\Vil Du Bli Million\00e6r\\Game.exe" in experimental wow64 mode 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0204:err:environ:init_peb starting L"C:\\users\\larsmartinhambro\\AppData\\Local\\Temp\\~ef7194.tmp" in experimental wow64 mode 0210:err:environ:init_peb starting L"C:\\windows\\syswow64\\winedevice.exe" in experimental wow64 mode 021c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys" 021c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys" 021c:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys" 0218:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\SecDrv": c0000142 larsmartinhambro(a)fedora-linux:~/.wine/drive_c/Program Files (x86)/Eidos Interactive/HotHouse Creations/Vil Du Bli Millionær$ 0224:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 0224:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. -- 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 28

[Bug 59161] New: Back to the future the game: Mouse cursor flickers on main menu screen
by WineHQ Bugzilla Jan. 8, 2026

Jan. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=59161 Bug ID: 59161 Summary: Back to the future the game: Mouse cursor flickers on main menu screen Product: Wine Version: 11.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: johan.gill(a)bahnhof.se Distribution: --- After launching any episode from "Back to the Future: The Game" (GOG.com release) and reaching the main menu screen, the mouse cursor that looks like a flux capacitor flickers. Arch Linux with KDE on Wayland with driver nvidia-open 580.105.08-6 I'm happy to provide logs if anybody suggests what logs are interesting. -- 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 58863] New: old games xtreme board games EG chess windows 95 to 2000 show china name?
by WineHQ Bugzilla Jan. 8, 2026

Jan. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=58863 Bug ID: 58863 Summary: old games xtreme board games EG chess windows 95 to 2000 show china name? Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lars_martin4(a)hotmail.com Distribution: --- wine 䅂䅌低縱⹅塅㬱 02d0:err:environ:init_peb starting L"C:\\windows\\syswow64\\winevdm.exe" in experimental wow64 mode 02d0:fixme:wow:wow64_NtSetLdtEntries 0107 0488323f 0000f39a 0000 00000000 00000000: stub 02d0:err:module:loader_init "krnl386.exe16" failed to initialize, aborting 02d0:err:module:loader_init Initializing dlls for L"C:\\windows\\syswow64\\winevdm.exe" failed, status c0000005 -- 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 15

[Bug 58385] New: Regression in Wine 9.22 causes plugin windows in Acrobat XI (e.g. PitStop Pro) to remain visible after closing
by WineHQ Bugzilla Jan. 8, 2026

Jan. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=58385 Bug ID: 58385 Summary: Regression in Wine 9.22 causes plugin windows in Acrobat XI (e.g. PitStop Pro) to remain visible after closing Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: edwardjameswells(a)gmail.com Distribution: --- Starting with Wine 9.22, plugin windows in Adobe Acrobat Pro XI — such as those provided by Enfocus PitStop Pro (e.g. the “Action Lists” window) — fail to disappear after being closed. This behavior did *not* occur in Wine 9.21 and earlier. ### Behavior: When the plugin window is closed (e.g. via the PitStop GUI), it disappears from Acrobat’s internal state — but remains *visibly open* on screen, frozen, and unresponsive. It is not redrawn or refreshed, and cannot be interacted with. Wine appears to believe the window has been destroyed, but the X11 window remains mapped. This affects usability severely. The bug affects both 32-bit and WOW64 installations. It occurs whether or not a window manager is used. ### Regression Confirmation: - Works in Wine 9.21: PitStop windows close cleanly and disappear from screen. - Broken in Wine 9.22 through 10.9 (latest tested): PitStop windows persist after close. ### Notes: This is *not* specific to WOW64 or any DPI configuration. I suspect the following commit introduced the regression: > `user32: Reimplement WIN_ListChildren() using NtUserBuildHwndList().` The bug appears to be that Wine no longer propagates child window teardown (e.g. `DestroyWindow` or `UnmapNotify`) to X11 for plugin-type windows that are marked as `WS_POPUP`, `WS_CHILD`, or transient. These windows may be missed by the new child enumeration logic. I can provide detailed logs with `WINEDEBUG=+win,+x11drv` if needed. ### System Details: - Arch Linux (current) - X11 (EXWM, but bug occurs without WM as well) - Wine 64-bit and 32-bit tested - Affected App: Adobe Acrobat Pro XI with PitStop Pro plugin -- 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 59109] New: Final Fantasy XI Online: White flash upon game client launch.
by WineHQ Bugzilla Jan. 8, 2026

Jan. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=59109 Bug ID: 59109 Summary: Final Fantasy XI Online: White flash upon game client launch. Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 18339eb0f5048500efb668e6a9b679ed2f62d7a3 Distribution: Gentoo After 18339eb0f50 [1], when transitioning from the launcher, PlayOnline Viewer, to the Final Fantasy XI Online game client, there is a brief white flash where it used to remain black. This also causes white flashes when switching away and/or back to the game window when running in windowed mode, but it seems to be more a symptom of the commit blamed in 58491 [2]. Using the open-source amdgpu/mesa drivers, and KWin-X11. Last tested at d60f8286056 [3]. Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/18339eb0f5048500efb668e6a9b679… 2. https://bugs.winehq.org/show_bug.cgi?id=58491 3. https://gitlab.winehq.org/wine/wine/-/commit/d60f8286056559233e992c4084f319… -- 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 7

[Bug 50772] New: SetFileAttributesA(FILE_ATTRIBUTE_READONLY) on a directory doesn't have any effect
by WineHQ Bugzilla Jan. 7, 2026

Jan. 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=50772 Bug ID: 50772 Summary: SetFileAttributesA(FILE_ATTRIBUTE_READONLY) on a directory doesn't have any effect Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st Distribution: --- Created attachment 69564 --> https://bugs.winehq.org/attachment.cgi?id=69564 Testcase Making a directory readonly by doing SetFileAttributesA(FILE_ATTRIBUTE_READONLY) doesn't seem to have any effect (at least, reading back the attributes with GetFileAttributesA doesn't reflect it). -- 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 7

[Bug 57807] New: Regression : Warcraft 3 crashes during cinematic, when wine-7.0.1 not
by WineHQ Bugzilla Jan. 7, 2026

Jan. 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=57807 Bug ID: 57807 Summary: Regression : Warcraft 3 crashes during cinematic, when wine-7.0.1 not Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: d(a)delpiroux.fr Distribution: --- Created attachment 78015 --> https://bugs.winehq.org/attachment.cgi?id=78015 terminal output 64 bits (phenom II), gtx770 and ubuntu 20.04. Warcraft 3 v-1.25 (with frozen throne). wine-7.0.1 don't crashes during cinematic, but display black screen (and it's ok for me, I can watch cinematic in "movie" fodler). On same setup, wine10.0 crashes during cinematic, for example the very first one (if I test with a new profile), so the game is not playable. -- 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 7

[Bug 57639] New: Nine Witches Family Disruption (GOG) cannot launch due to missing .donet hostfxr.dll
by WineHQ Bugzilla Jan. 6, 2026

Jan. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=57639 Bug ID: 57639 Summary: Nine Witches Family Disruption (GOG) cannot launch due to missing .donet hostfxr.dll Product: Wine Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Console log: 00f0:err:eventlog:ReportEventW L"Description: A .NET Core application failed.\n" 00f0:err:eventlog:ReportEventW L"Application: NineWitches.exe\n" 00f0:err:eventlog:ReportEventW L"Path: C:\\GOG Games\\Nine Witches Family Disruption\\NineWitches.exe\n" 00f0:err:eventlog:ReportEventW L"Message: A fatal error occurred. The required library hostfxr.dll could not be found.\n" 00f0:err:eventlog:ReportEventW L"If this is a self-contained application, that library should exist in [C:\\GOG Games\\Nine Witches Family Disruption\\].\n" 00f0:err:eventlog:ReportEventW L"If this is a framework-dependent application, install the runtime in the global location [C:\\Program Files\\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\\SOFTWARE\\dotnet\\Setup\\InstalledVersions\\x64\\Inst"... 00f0:err:eventlog:ReportEventW L"\n" 00f0:err:eventlog:ReportEventW L"The .NET Core runtime can be found at:\n" 00f0:err:eventlog:ReportEventW L" - https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win1…" 00f0:err:eventlog:ReportEventW L"\n" 00f0:fixme:advapi:DeregisterEventSource (00000000CAFE4242) stub -- 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 29354] New: Microsoft Virtual PC 2007 SP1 installer fails to get past the "Product Key" dialog
by wine-bugs＠winehq.org Jan. 6, 2026

Jan. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=29354 Bug #: 29354 Summary: Microsoft Virtual PC 2007 SP1 installer fails to get past the "Product Key" dialog Product: Wine Version: 1.3.34 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, split off bug mentioned in http://bugs.winehq.org/show_bug.cgi?id=17512#c3 to track what is most likely a regression ... --- quote --- Tested in 1.3.19 Didn't crash but I couldn't get past the "Product Key" screen. The "Next" button didn't seem to do anything. --- quote --- The problem in Microsoft Virtual PC 2007 SP1 installer is the "ValidateProductID" standard action. Dump using ORCA: --- snip --- CustomerInformationDialog NextButton NewDialog ReadyToInstallDialog PIDRET = 0 4 CustomerInformationDialog NextButton DoAction CA_ValidatePID NOT ProductID AND PIDKEY AND PIDKEY<>" " 1 CustomerInformationDialog NextButton DoAction CA_InstallForAllUsers NOT VPC2004INSTALLED 2 CustomerInformationDialog NextButton DoAction CA_SetTargetPathOnUpgrade VPC2004INSTALLED 3 --- snip --- First condition, if true -> CA_ValidatePID gets executed. --- snip --- 0023:trace:msi:MSI_EvaluateConditionW L"NOT ProductID AND PIDKEY AND PIDKEY<>\" \"" ... 0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for property L"ProductID" ... 0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for property L"PIDKEY" ... 0023:trace:msi:MSI_EvaluateConditionW 0 <- L"NOT ProductID AND PIDKEY AND PIDKEY<>\" \"" --- snip --- (not fulfilled) Another condition to reach "ReadyToInstallDialog" is "PIDRET = 0". --- snip --- 0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action start 18:26:06: ValidateProductID." 0023:trace:msi:msi_get_property returning L"74216<````=````=````=````=`````>@@@@@" for property L"PIDTemplate" 0023:fixme:msi:ACTION_ValidateProductID partial stub: template L"74216<````=````=````=````=`````>@@@@@" key L"PWCVDGDPM7P23VYG6QM4R8Y8T" 0023:trace:msi:msi_set_property 0x13ce60 L"ProductID" L"PWCVDGDPM7P23VYG6QM4R8Y8T" 0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action ended 18:26:06: ValidateProductID. Return value 0." ... 0023:trace:msi:MSI_EvaluateConditionW L"PIDRET = 0" 0023:trace:msi:msi_get_property property L"PIDRET" not found 0023:trace:msi:MSI_EvaluateConditionW 0 <- L"PIDRET = 0" --- snip --- The "PIDRET" property never exists hence the installation is stuck in "CustomerInformationDialog". If you google for "Adding PIDRET property" you will find many similar looking msi logs, suggesting that this property is added during ValidatePID custom action: --- snip --- MSI (c) (DC:20) [17:55:05:750]: Doing action: ValidatePID MSI (c) (DC:20) [17:55:05:750]: Note: 1: 2205 2: 3: ActionText Action 17:55:05: ValidatePID. Action start 17:55:05: ValidatePID. ... MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PID property. Its value is '58730-000-0000007-05734'. MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding ProductID property. Its value is '58730-000-0000007-05734'. ... MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PIDRET property. Its value is '0'. Action ended 17:55:05: ValidatePID. Return value 1. --- snip --- Because ProductID was set earlier during ValidateProductID standard action, CA_ValidatePID is never executed. http://source.winehq.org/git/wine.git/blob/8cc5561fbf9f3250fbd2d986390e4013… If you remove line 6891 the installer executes the custom action which allows to proceed and let the installation finally succeed. You need 'winetricks mfc42' for CA_ValidatePID. Regards -- 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 23