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

[Bug 49013] New: League of Legends: Exception code c0000005
by WineHQ Bugzilla Jan. 9, 2026

Jan. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=49013 Bug ID: 49013 Summary: League of Legends: Exception code c0000005 Product: Wine Version: 5.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: harry+winehq(a)unheit.net Distribution: --- Created attachment 66992 --> https://bugs.winehq.org/attachment.cgi?id=66992 Logs for PID with WINEDEBUG=+seh,+pid,+tid,+loaddll,+kernelbase,+relay When starting the Riot Launcher for League of Legends I often, but not always, get Unhandled exception code c0000005. Attached is a log file with WINEDEBUG=+seh,+pid,+tid,+loaddll,+kernelbase,+relay. The log only contains entries for the PID that raises the exception. I've tried to log even more, but then the exception does not occur. It seems timing sensitive. If other debug channels are required, I can try to enable them, but I don't know which ones are useful. -- 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 53422] New: Bully: Scholarship Edition fails to play intros
by WineHQ Bugzilla Jan. 9, 2026

Jan. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=53422 Bug ID: 53422 Summary: Bully: Scholarship Edition fails to play intros Product: Wine Version: 7.13 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: --- Created attachment 72812 --> https://bugs.winehq.org/attachment.cgi?id=72812 +quartz Disabling quartz or renaming Movies folder helps with getting to main menu. wine-7.13-188-g1d65bc06b30 -- 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 2

[Bug 50724] New: Tomb Raider (2013) enabling tessellation leads to crash with Vulkan renderer
by WineHQ Bugzilla Jan. 9, 2026

Jan. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=50724 Bug ID: 50724 Summary: Tomb Raider (2013) enabling tessellation leads to crash with Vulkan renderer Product: Wine Version: 6.2 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: --- err:vkd3d_dxbc_compiler_put_symbol: Failed to insert symbol entry (register 0x6, 0). err:vkd3d_dxbc_compiler_put_symbol: Failed to insert symbol entry (register 0x6, 1). err:vkd3d_dxbc_compiler_put_symbol: Failed to insert symbol entry (register 0x6, 2). err:vkd3d_dxbc_compiler_put_symbol: Failed to insert symbol entry (register 0x6, 3). err:vkd3d_dxbc_compiler_put_symbol: Failed to insert symbol entry (register 0x6, 7). wine-6.2-320-gee4e33ed9ac vkd3d-1.2-180-g87a3712 -- 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 2

[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 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 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

[Bug 58290] New: eMule 0.50a: Toolbar icons show with black background when in context menu
by WineHQ Bugzilla Jan. 5, 2026

Jan. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=58290 Bug ID: 58290 Summary: eMule 0.50a: Toolbar icons show with black background when in context menu Product: Wine Version: 10.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 78640 --> http://bugs.winehq.org/attachment.cgi?id=78640 Back background eMule 0.50a: Toolbar icons show with black background when in context menu -- 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 7