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

[Bug 55405] New: FreeCommander crashing immediately after it starts, when Windows version is set above Windows XP
by WineHQ Bugzilla Oct. 22, 2026

Oct. 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=55405 Bug ID: 55405 Summary: FreeCommander crashing immediately after it starts, when Windows version is set above Windows XP Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mywine(a)schiermeier-it.de Distribution: --- Created attachment 74965 --> https://bugs.winehq.org/attachment.cgi?id=74965 Console log from start of FreeCommander with Windows version set to v10 Installation of FreeCommander 32bit is working without any error. When it should start it crashes. Depending on the version Windows is set to, it behaves like this: Windows XP: works Windows 7: crash at the start with a stack overflow error, show in a message box Windows 10: a window came up and disappears immediately without any message (box) Console output for Windows 10 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.

2 5

[Bug 27559] New: ImgBurn crash at startup when Wine's 'Windows Version' is set to 'Vista' (or newer)
by wine-bugs＠winehq.org Oct. 22, 2026

Oct. 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=27559 Summary: ImgBurn crash at startup when Wine's 'Windows Version' is set to 'Vista' (or newer) Product: Wine Version: 1.3.22 Platform: x86 URL: http://www.imgburn.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lightning_uk(a)imgburn.com I've had a bunch of crash logs sent to me over the past year where ImgBurn crashes unrecoverably on startup when users are running it under Wine but was never able to reproduce the error until today. It turns out that if Wine's 'Windows Version' is set to 'XP' (default and what I'd always been using) everything works fine. The second it's changed to 'Vista' (or newer), the app crashes at startup. I've managed to get a crash call stack via madExcept / Eurekalog and have now traced the problem back to the 'Explorer' style component it uses in the 'Disc Layout Editor' window ('TVirtualExplorerTree' by MustangPeak). It looks like it's related to namespace stuff and therefore the shell? I've made/attached a Delphi demo app with a single form and single instance of 'TVirtualExplorerTree' to hopefully make testing and debugging this issue a little easier. Without fail, it'll crash when Wine's 'Windows Version' is set to 'Vista' but it's fine as 'XP'. I'm using Wine in Ubuntu 11.04 for testing. The programs (ImgBurn and demo app) work fine on a real Windows XP, Vista or 7 installation. -- 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 35

[Bug 44985] New: BIAS FX: Blank window when running the app
by wine-bugs＠winehq.org Oct. 22, 2026

Oct. 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=44985 Bug ID: 44985 Summary: BIAS FX: Blank window when running the app Product: Wine Version: 3.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: oxez911(a)gmail.com Distribution: --- Created attachment 61119 --> https://bugs.winehq.org/attachment.cgi?id=61119 term output Distribution: Debian sid Wine version: 3.6.0~sid (Using the wine-devel package from winehq.org) Description: Trying the BIAS FX standalone app (both in 32 and 64bit) result in a blank window (black or white, seems random..) Note: the trial can be downloaded free of change at https://www.positivegrid.com/bias-fx/ I attached a trace of what I saw in the terminal, I can provide more info if needed (I'm not sure what WINEDEBUG needed to be set at, I didn't tweak 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.

3 67

[Bug 53501] New: Test Drive Unlimited not working
by WineHQ Bugzilla Oct. 21, 2026

Oct. 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=53501 Bug ID: 53501 Summary: Test Drive Unlimited not working Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ds000001(a)outlook.de Distribution: --- Created attachment 72860 --> https://bugs.winehq.org/attachment.cgi?id=72860 Lutris and Wine Hello, I try to run Test Drive Unlimited DVD 1.66 version with Wine. My system: CPU: 3700X GPU: 6700XT RAM: 32 GB Wine: 7.15 installed through pacman and using Lutris 0.5.10.1-2 for easier management of all WINEPREFIX's WINEPREFIX: - 32 Bit and complete new - Through winecfg set as Win XP - No additional packages installed - ESync, Fsync and DXVK not enabled - Virtual window mode enabled with 1080p resolution, that way it is easier for me to see, if something happens or not - no additional modules installed with Winetricks If I try to start the game, the configured Wine desktop appears, the disc drive starts to spin and after that nothing happens. Output from "lutris -d" and enabled diagnostics for the WINEPREFIX gave me the output from tdudebug1.txt. Enabled debug with "WINEDEBUG=warn+all" and tried to start the game through the wine command. Got the log tdudebug2.txt out of this. Any ideas what I am doing wrong? -- 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 57993] New: winedevice.exe Hangs After Exiting Games
by WineHQ Bugzilla Oct. 20, 2026

Oct. 20, 2026

https://bugs.winehq.org/show_bug.cgi?id=57993 Bug ID: 57993 Summary: winedevice.exe Hangs After Exiting Games Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nekoNexus(a)protonmail.ch Distribution: --- Created attachment 78253 --> https://bugs.winehq.org/attachment.cgi?id=78253 Vanilla Wine version 10.3 Log Distro: Gentoo Linux (x86_64) DXVK Version: 2.6 Gamescope Version: 3.16.2 Desktop Environment: KDE Plasma 6.2.5 (Wayland) CPU: Ryzen 3700X @ 4.98 GHz RAM: 32GBs @ 3600 MHz GPU: AMD RX 7800 XT Mesa Version: 25.0.1 Explanation: ------------- When launching games like Sherlock Holmes: Crimes and Punishments (GOG), exiting the game (even just launching the game and closing via the main menu not long after) causes winedevice.exe to just hang (and this causes a zombie window to remain open) and I'm forced to run "pkill -9 winedevice.exe" (this problem is consistent) It doesn't seem to show up at the end of my log, either, for some reason. I'll still share my log (although, this specific log exhibits a separate issue I'm about to file) for reference, however -- 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 57890] New: 3DMark11 is not working
by WineHQ Bugzilla Oct. 20, 2026

Oct. 20, 2026

https://bugs.winehq.org/show_bug.cgi?id=57890 Bug ID: 57890 Summary: 3DMark11 is not working Product: Wine Version: 10.0 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 78118 --> https://bugs.winehq.org/attachment.cgi?id=78118 Log of the fail Unlike bug 42119 I can't start this DirectX11 benchmark in the same wine. The application started with empty windows. The last line in the log ~~~~ 0024:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0000000001233510, format DXGI_FORMAT_R8G8B8A8_UNORM_SRGB, flags 0x3, mode_count 000000000011FC58, modes 00000000009908F0 partial stub! ~~~~ So the problem is in dxgi? -- 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 58706] New: Blood Fresh Supply / Doom 64 (KEX engine games) fail to start when OpenGl API is selected (EGL backend)
by WineHQ Bugzilla Oct. 19, 2026

Oct. 19, 2026

http://bugs.winehq.org/show_bug.cgi?id=58706 Bug ID: 58706 Summary: Blood Fresh Supply / Doom 64 (KEX engine games) fail to start when OpenGl API is selected (EGL backend) Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Distribution: --- Those games using the Kex Engine that support the Opengl renderer API fail to start when the new experimental EGL opengl backend is used. Such games are: Blood - Fresh Supply Doom 64 System Shock: Enhanced Edition The error message that is shown on start: kexPlatformApp::InitVideo: Failed to create window (No matching GL pixel format available). Other available renderers in those games (Vulkan and D3d11) work properly with the new EGL backend. wine-10.15-28-g7d26649f637 NVIDIA 580.82.09 X.Org X Server 1.21.1.18 -- 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 46697] New: ntQueryDirectoryFileEx needed
by wine-bugs＠winehq.org Oct. 19, 2026

Oct. 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=46697 Bug ID: 46697 Summary: ntQueryDirectoryFileEx needed Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: springrat(a)protonmail.com Distribution: --- Mod Organizer 2 fails to load the userspace virtual file system (USVFS) .dll due to a lack of the function, "ntQueryDirectoryFileEx" in ntdll.dll. As a result, the program itself cannot be used for its intended purposes of organizing and loading mods directly, and some critical features such as using tools within the virtual environment break. -- 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 24

[Bug 57222] New: Installation of Konami games fails (Bombergirl, Beatmania IIDX Infinitas) with error 1603
by WineHQ Bugzilla Oct. 19, 2026

Oct. 19, 2026

https://bugs.winehq.org/show_bug.cgi?id=57222 Bug ID: 57222 Summary: Installation of Konami games fails (Bombergirl, Beatmania IIDX Infinitas) with error 1603 Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: sraamar.psplus(a)gmail.com Distribution: --- Created attachment 77139 --> https://bugs.winehq.org/attachment.cgi?id=77139 Trace The installation process for certain Konami games, such as Bombergirl and Beatmania IIDX Infinitas, fails when run through Wine. The setup halts with error code 1603. These are the relevant lines I think of the trace: 0120:err:msi:execute_script Execution of script 0 halted; action L"[C:\\users\\vince\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\KONAMI\\BomberGirl.url\0080http://eagate.573.jp/game/konasteapp/API/login/login.html?game_id=bomber-girl\00801\0080C:\\Games\\BomberGirl\\BomberGirl.ico\00800\0080C:\\users\\vince\\Desktop\\BomberGirl.url\0080h"... returned 1603 0120:err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned 1603 Bombergirl installer: https://p.eagate.573.jp/game/eacbg/bg/download/installer.html Beatmania IIDX INFINITAS installer : https://d1rc4pwxnc0pe0.cloudfront.net/v2/installer/infinitas_installer_2022… Tested on Arch Linux with wine 9.18 in a clean prefix. -- 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 59682] New: Windrose server: UDP bind to specific IPv4 behaves like 0.0.0.0%iface, causing wrong source IP and multihoming conflicts
by WineHQ Bugzilla Oct. 18, 2026

Oct. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=59682 Bug ID: 59682 Summary: Windrose server: UDP bind to specific IPv4 behaves like 0.0.0.0%iface, causing wrong source IP and multihoming conflicts Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)list.winehq.org Reporter: koekdendeniz(a)gmail.com Distribution: --- A Windows dedicated server application (WindroseServer-Win64-Shipping.exe) works correctly on native Windows, where binding to a specific IP via -Multihome=<IP> results in UDP sockets bound to that IP:PORT. Under Wine on Linux, the same server appears to bind correctly in Wine debug logs, but the resulting Linux UDP socket shows up as 0.0.0.0%iface:PORT instead of IP:PORT. This causes two problems: 1. Outgoing UDP replies use the wrong source IP (the host's main IP instead of the IP passed to -Multihome). 2. Multiple instances cannot use the same UDP port on different local IPs, because the socket effectively behaves like 0.0.0.0:PORT instead of IP_A:PORT and IP_B:PORT. Tested with: * host networking * multiple public IPv4 addresses assigned on the same host * command line using -Multihome=<IP> Expected result: UDP socket is bound to the specific IPv4 address, replies use that source IP, and multiple instances can bind the same UDP port on different local IPs. Actual result: UDP socket appears as 0.0.0.0%iface:PORT, replies use the wrong source IP, and same-port multi-IP hosting fails. -- 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