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

[Bug 55138] New: msys2: bash.exe is not able to fork/start another process.
by WineHQ Bugzilla Oct. 6, 2026

Oct. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=55138 Bug ID: 55138 Summary: msys2: bash.exe is not able to fork/start another process. Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 74697 --> https://bugs.winehq.org/attachment.cgi?id=74697 allocation stacks in parent and child bash.exe This is a followup to bug 47808. If I understand it right, bug 47808 was primarily about native libraries getting called at a win32 stack which was not yet committed. Those native libraries then jumped over the guard page, therefore the stack got not grown, instead a crash reported. This aspect was fixed by using the syscall interface and therefore bug 47808 was closed. But there is another issue that causes a msys2-forked process crashing, because after the stack was grown it still misses the PAGE_READWRITE flags. For this Zeb Figura included in the first attachement to bug 47808 "always expand the stack if within the stack reserve" a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE" to the page that gets the VPROT_GUARD removed in grow_thread_stack. This modification still enables a forked process to run. The issue can be reproduced with an unmodified wine by just - running msys2 bash.exe interactively - then trying to start e.g. notepad from it. Attached file shows the stack when the stack gets allocated - in a working msys2-parent process and - in a failing msys2-forked child process. Therefore it looks like the forked stack get really setup differently, but it is still not clear if or when this memory gets the READ/WRITE added in native windows. -- 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 59440] New: NTSync doesn't work very well in ONGEKI Re:Fresh.
by WineHQ Bugzilla Oct. 6, 2026

Oct. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59440 Bug ID: 59440 Summary: NTSync doesn't work very well in ONGEKI Re:Fresh. Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: admin(a)uright.icu CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 80422 --> http://bugs.winehq.org/attachment.cgi?id=80422 Kernel: 6.19.2-1-MANJARO I looked at perf.data, and 40% of the time was spent on the function NtWaitForSingleObject, which is obviously abnormal. I checked the locks, and one unnamed lock had an average wait time of 2.33 seconds. Since I can't upload more than two attachments, the lock report for that line is as follows: Name acquired contended avg wait total wait max wait min wait 600487 600487 3.88 us 2.33 s 91.82 us 568 ns 67 67 193.90 us 12.99 ms 480.07 us 2.38 us rcu_state 17 17 2.36 us 40.13 us 2.93 us 1.67 us 13 13 3.13 us 40.67 us 4.61 us 1.80 us rcu_state 3 3 2.52 us 7.57 us 3.02 us 2.24 us 2 2 1.58 us 3.16 us 1.80 us 1.36 us jiffies_lock 2 2 2.24 us 4.47 us 2.33 us 2.15 us 1 1 1.90 us 1.90 us 1.90 us 1.90 us 1 1 1.47 us 1.47 us 1.47 us 1.47 us 1 1 3.23 us 3.23 us 3.23 us 3.23 us 1 1 7.11 us 7.11 us 7.11 us 7.11 us 1 1 7.52 us 7.52 us 7.52 us 7.52 us Each lock was contended once, which seems to be caused by some sort of conflict. -- 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 59134] UFO: Aftershock, UFO: Afterlight - problem starting the games with Nvidia binary drivers (EGL backend)
by WineHQ Bugzilla Oct. 6, 2026

Oct. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59134 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |9bd4580a1bb8bf2da893de9b49e | |80b0957d63ac1 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Béla Gyebrószki <gyebro69(a)gmail.com> --- This was fixed by https://gitlab.winehq.org/wine/wine/-/commit/9bd4580a1bb8bf2da893de9b49e80b… -- 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 0

[Bug 60446] New: MikuMikuDance (MMD) has now some unreachable buttons and unclickable input boxes...
by WineHQ Bugzilla Oct. 6, 2026

Oct. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=60446 Bug ID: 60446 Summary: MikuMikuDance (MMD) has now some unreachable buttons and unclickable input boxes... Product: Wine Version: 11.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: a.s25(a)live.it Target Milestone: --- Distribution: --- Created attachment 82259 --> http://bugs.winehq.org/attachment.cgi?id=82259 Demonstration video I'm using Arch Linux with KDE Plasma 6.7.5 and I have DXVK. Several days ago I updated wine to 11.18 (I'm not sure if I was on 11.17 before) and I opened up MikuMikuDance (a very old studio software used for making anime-style animations). I use MikuMikuDance (or MMD for short) in the separate window mode (one window with the inputs, another window for the render) because of this bug here: https://bugs.winehq.org/show_bug.cgi?id=42666 (the black interface bug) that never got fixed, but it was usable nonetheless. The input boxes flickered and allowed me to barely see them and be able to click & edit them (or click the buttons). Then I updated wine and now when I open MikuMikuDance in the rendering window the input boxes and buttons won't flicker anymore and it doesn't even allow me to click & interact with them... I attached a video of the issue where I showcased me trying to click on the black part of the rendering window trying to click some input boxes or buttons but with no luck; Then activated "view(V)" -> "information display(D)" to show that the program works, it's just that I can't see nor click the "info" button that is located in the black part of the rendering screen; I also disabled "view(V)" -> "separate window(W)" to showcase how the program looks (like the other issue of the black interface bug I linked above) and how the UI element flickers with the black interface but you can still manipulate and interact with them, and this is how it was before the update, however, now, even when not in separate window it still does not allow me to click the buttons above the rendering area and the input boxes below the rendering area. If you're wondering how MikuMikuDance should look, here's a video (on youtube) showing the interface: https://www.youtube.com/watch?v=ugL1y2RkEVQ (check the minute 0:00 where you can see the interface in it's entirety but not in separate window mode). For installing MikuMikuDance you can do it here: https://learnmmd.com/http:/learnmmd.com/wine-mmd-mikumikudance-linux/ (for installing it with DXVK support) If that link is broken, try this: https://learnmmd.com/downloads/ I really hope this bug will be fixed so I can use MikuMikuDance again like I used to and if we're lucky enough for the black interface bug to be fixed too so it will make MikuMikuDance better to use under Linux. Thank you very much of the hard work you put in this big project! I'm really grateful for all the work you've put into it! Keep up the good 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 1

[Bug 60445] New: win32u: vkFreeMemory leaks the host-pointer block of host-visible allocations in WoW64 processes
by WineHQ Bugzilla Oct. 6, 2026

Oct. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=60445 Bug ID: 60445 Summary: win32u: vkFreeMemory leaks the host-pointer block of host-visible allocations in WoW64 processes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: wildart(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 82258 --> http://bugs.winehq.org/attachment.cgi?id=82258 MWE error source Component: vulkan · Version: 11.0 · Keywords: regression, testcase Description In a 32-bit process under the new WoW64 mode, every vkAllocateMemory on a host-visible memory type reserves a NtAllocateVirtualMemory block for VK_EXT_external_memory_host import. vkFreeMemory never releases that block.An application that allocates and frees host-visible memory repeatedly, for example a staging buffer per upload, exhausts its 2 GiB address space even though it frees every allocation. This path is taken when the host driver exposes VK_EXT_external_memory_host but Wine doesn't use placed mapping (map_placed_align == 0). MoltenVK on macOS is one such driver. Steps to reproduce 1. i686-w64-mingw32-gcc -O2 -I<vulkan-headers>/include vk_hostmem_leak.c -o vk_hostmem_leak.exe (source attached) 2. wine vk_hostmem_leak.exe The test allocates a 16 MiB host-visible VkDeviceMemory and frees it, 1000 times. At most one allocation is live at any moment. Actual result wine 11.0 device Apple M5 Pro, driver 0x28a1 memory type 1, allocating and freeing 16 MiB x 1000 FAIL: vkAllocateMemory returned -1 at iteration 125 (2000 MiB allocated and freed); VirtualAlloc(16 MiB) also fails: address space exhausted Expected result PASS: 1000 allocations of 16 MiB Analysis (dlls/win32u/vulkan.c, current master) - allocate_external_host_memory() stores the NtAllocateVirtualMemory result only in its local mapping and passes it on through import_info->pHostPointer. It never returns the pointer to the caller. - win32u_vkAllocateMemory() has its own local void *mapping = NULL, which is never assigned, and does memory->vm_map = mapping. As a result, vm_map stays NULL. - win32u_vkFreeMemory() releases the block only if (memory->vm_map), so it never does. - allocate_external_host_memory() also leaks the block on its own error paths: when vkGetMemoryHostPointerPropertiesEXT fails, and on the failed: path in win32u_vkAllocateMemory. This is a regression. In Wine 10.0, wine_vkAllocateMemory() in dlls/winevulkan/vulkan.c assigns the block to memory->vm_map, and wine_vkFreeMemory() releases it. The leak appears to date from the move of this code to win32u. I haven't bisected the exact commit. Suggested fix Have allocate_external_host_memory() return the block, for example through an out parameter. Store it in memory->vm_map, and release it on the error paths. The existing vm_map handling in win32u_vkFreeMemory() and win32u_vkUnmapMemory2KHR() should then work as intended. Environment macOS 26.6, Apple M5 Pro, MoltenVK 1.4.1, Wine 11.0 (new WoW64) -- 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 60444] New: crypt32: CryptAcquireCertificatePrivateKey ignores the NCrypt flags
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60444 Bug ID: 60444 Summary: crypt32: CryptAcquireCertificatePrivateKey ignores the NCrypt flags Product: Wine Version: 11.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)list.winehq.org Reporter: auzy83(a)gmail.com Target Milestone: --- Distribution: --- Symptom: .NET's `GetRSAPrivateKey()` and `GetECDsaPrivateKey()` call `CryptAcquireCertificatePrivateKey` with `CRYPT_ACQUIRE_ONLY_NCRYPT_KEY_FLAG`. Wine returns a CAPI `HCRYPTPROV`, and the caller then crashes using it as an `NCRYPT_KEY_HANDLE`. Wine today (`dlls/crypt32/cert.c`): - It returns the cached key context only when `CRYPT_ACQUIRE_CACHE_FLAG` is set. - It never consults `CRYPT_ACQUIRE_ALLOW/PREFER/ONLY_NCRYPT_KEY_FLAG`. - A certificate whose only key is an NCrypt handle (`CERT_NCRYPT_KEY_HANDLE_PROP_ID`, with no `CERT_KEY_PROV_INFO`) isn't usable without the cache flag. Should do: - With any of the NCrypt flags, return an existing NCrypt key context with `*pdwKeySpec = CERT_NCRYPT_KEY_SPEC`. - With `ONLY_NCRYPT`, never return a CAPI handle. Confirm on Windows: - With `ONLY_NCRYPT` on a certificate whose key is in a CAPI CSP, Windows may open it through the KSP's legacy-key support and return an NCrypt handle rather than fail. Find out which, and with what error. - What `pfCallerFreeProv` is in each case. Tests (`dlls/crypt32/tests/cert.c`): A certificate with a CAPI key and one with an NCrypt key handle, each acquired with no flag, `ALLOW`, `PREFER` and `ONLY`. Check the returned key spec and the handle type (e.g. `NCryptGetProperty` succeeds on it). Software Affected: Control4 Composer Pro -- 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 0

[Bug 60442] New: crypt32: Store the imported key spec in CRYPT_KEY_PROV_INFO.
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60442 Bug ID: 60442 Summary: crypt32: Store the imported key spec in CRYPT_KEY_PROV_INFO. Product: Wine Version: 11.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)list.winehq.org Reporter: auzy83(a)gmail.com Target Milestone: --- Distribution: --- Symptom: After `PFXImportCertStore` imports an RSA key, .NET's `cert.PrivateKey` fails with `NTE_NO_KEY`. Wine today: In `dlls/crypt32/pfx.c`, `set_key_prov_info()`: - fills `dwKeySpec` from `CryptGetProvParam(PP_KEYSPEC)`. That returns the *mask* of supported specs (3), which isn't a valid key spec. - always sets `dwFlags = 0`, which drops `CRYPT_MACHINE_KEYSET` for imports into the machine store. Should do: - Set `dwKeySpec` to the spec the key was really imported with, `AT_KEYEXCHANGE` for a `CALG_RSA_KEYX` import. - Keep `CRYPT_MACHINE_KEYSET` in `dwFlags` when the import used it. Confirm on Windows: `dwKeySpec`, `dwFlags`, `dwProvType` and the provider name for RSA imports with flags 0, `CRYPT_MACHINE_KEYSET` and `CRYPT_USER_KEYSET`. Tests (`dlls/crypt32/tests/store.c`, `test_PFXImportCertStore`): Read `CERT_KEY_PROV_INFO_PROP_ID` back after the import and check each field. Then check that `CryptAcquireContextW` with the returned container name and `dwKeySpec` opens the key. Software Affected: Control4 Composer Pro -- 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 0

[Bug 60441] New: bcrypt: Check the key algorithm when exporting asymmetric keys
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60441 Bug ID: 60441 Summary: bcrypt: Check the key algorithm when exporting asymmetric keys Product: Wine Version: 11.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)list.winehq.org Reporter: auzy83(a)gmail.com Target Milestone: --- Distribution: --- Symptom: Calling `BCryptExportKey` on an ECDSA key with `BCRYPT_RSAFULLPRIVATE_BLOB` crashes inside SymCrypt instead of returning an error. Any caller that guesses the blob type hits this, and schannel and crypt32 used to guess RSA. Wine today: In `dlls/bcrypt/bcrypt_main.c`, `export_asymmetric_key()` picks the export routine from the blob type alone and never checks the key's algorithm. Should do: Refuse a blob type that doesn't match the key's algorithm, in both directions and for every asymmetric type (RSA, ECC, DSA, DH). Confirm on Windows: The exact status code. `STATUS_INVALID_PARAMETER` is likely, but check it. Tests (`dlls/bcrypt/tests/bcrypt.c`): Export an ECDSA P-256 key as each RSA blob type, and an RSA key as `BCRYPT_ECCPRIVATE_BLOB`. Check the status, and that the size output is left alone. Put these in a commit before the fix; they crash today, so they can't be `todo_wine`. Software Affected: Control4 Composer Pro Patches: I have patches available, however, as they are written by LLM, they do not comply with the submission rules -- 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 0

[Bug 60427] New: Wine does not update or create prefix and sits there instead
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60427 Bug ID: 60427 Summary: Wine does not update or create prefix and sits there instead Product: Wine Version: 11.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: robertyutintat(a)yahoo.com Target Milestone: --- Distribution: --- Created attachment 82236 --> http://bugs.winehq.org/attachment.cgi?id=82236 Terminal Output On 11.19, Wine Development does not update nor create prefix; instead it just sits idly by in the middle. I am not sure that a regression test is possible since it's the base program that is misbehaving and not the program. Would you still prefer that I attempt one nonetheless? Attached is a terminal output. Also, I tried downgrading to the previous version (11.18). The bug is gone. Then when I went back to 11.19, the bug returns. -- 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 28

[Bug 60416] New: Paint.net 5.2 (Build 9767) errant line on the toolbar intersects buttons
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60416 Bug ID: 60416 Summary: Paint.net 5.2 (Build 9767) errant line on the toolbar intersects buttons Product: Wine Version: 11.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: eblumster(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 82221 --> http://bugs.winehq.org/attachment.cgi?id=82221 image of the issue shown on the right (Wine), left is windows a line is being drawn incorrectly somehow causing it to intersect with the tool brush and other top toolbar items -- 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 60440] New: Add option to pull DPI from XSETTINGS
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60440 Bug ID: 60440 Summary: Add option to pull DPI from XSETTINGS Product: Wine Version: 11.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: criteria32(a)gmail.com Target Milestone: --- Distribution: --- Currently, Wine will default to 96 DPI (1x scale) for a wineprefix, but this is suboptimal for environments that need a 2x scale for example. Winecfg allows manually changing DPI, but this can be tedious for lots of wineprefixes. X11 has a mechanism that many clients use for determining DPI: the Xft/DPI setting in the XSETTINGS protocol (https://specifications.freedesktop.org/xsettings/latest/, https://www.freedesktop.org/wiki/Specifications/XSettingsRegistry/) I think winecfg should provide an option to track the X11 DPI using this, so that users don't have to. -- 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 59202] New: FIFA World Cup 98 and FIFA: Road to World Cup 98 freezes during menu transitions
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59202 Bug ID: 59202 Summary: FIFA World Cup 98 and FIFA: Road to World Cup 98 freezes during menu transitions Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: winehq(a)mrpowergamerbr.com Distribution: --- Created attachment 80077 --> http://bugs.winehq.org/attachment.cgi?id=80077 FIFA: Road to World Cup 98 running with WINEDEBUG="+thread,+sync" When running FIFA World Cup 98 or FIFA: Road to World Cup 98, the game freezes during menu transitions. Menu transitions is when the game transitions from "Menu -> Cutscene" or "Menu -> Game", "Game -> Menu", so on and so forth. I'm grouping both games into the same issue because both games, as far as I know, use the same engine, and both exhibit the same bug. While FIFA World Cup 98 does not have a demo version, FIFA: Road to World Cup 98 does: https://archive.org/details/FIFAWC98 FIFA World Cup 98 freezes right after the splash screen of the game (where the game transitions from the splash screen to a cutscene). FIFA: Road to World Cup 98 freezes right after the game tries to start a friendly match. I did try using older Wine versions (the earliest version I tried was Wine 5.15), but it seems that this bug has been present for a long time. The bug can be worked around by using "taskset -c 0 wine ..." when starting the game, using "WINEDEBUG="+thread wine ..." or setting the kernel parameter "maxcpus=1". It isn't a full workaround, the freeze still happens sometimes, but it does work well enough that you can get into a game and play the game. Watch out that the game does NOT run on Windows 11. -- 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 52128] New: Hog4PC 3.17 installer VBScript custom action wants scrrun:filesys_MoveFolder implementation
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=52128 Bug ID: 52128 Summary: Hog4PC 3.17 installer VBScript custom action wants scrrun:filesys_MoveFolder implementation Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. --- snip --- $ wine msiexec -i Hog_4_PC_3.17.0.3327.msi ... 0184:trace:scrrun:filesys_FolderExists 0362A084 L"C:\\users\\focht\\AppData\\Roaming" 02F0F970 ... 0184:fixme:scrrun:filesys_MoveFolder 0362A084 L"C:\\users\\focht\\AppData\\Roaming" L"C:\\users\\focht\\AppData\\Roaming" ... 0184:err:msi:MsiActiveScriptSite_OnScriptError script error: L"Object doesn't support this action" ... 0184:trace:msi:ScriptThread custom action (184) returned 1603 --- snip --- VBScript custom action scriptlet: --- snip --- Function renamePersistentDir() Dim appDataEnv appDataEnv = shell.expandEnvironmentStrings("%APPDATA%") Dim roamingDir roamingDir = appDataEnv + "\Flying Pig Systems" If ( fso.FolderExists(roamingDir) ) Then fso.MoveFolder roamingDir, appDataEnv + "\High End Systems" fso.MoveFolder appDataEnv + "\High End Systems\Hog 4PC", appDataEnv + "\High End Systems\Hog 4 PC" End If End Function --- snip --- Wine source: https://source.winehq.org/git/wine.git/blob/f03933fbb73152c7a54383fba411a61… --- snip --- 3616 static HRESULT WINAPI filesys_MoveFolder(IFileSystem3 *iface,BSTR Source, 3617 BSTR Destination) 3618 { 3619 FIXME("%p %s %s\n", iface, debugstr_w(Source), debugstr_w(Destination)); 3620 3621 return E_NOTIMPL; 3622 } --- snip --- Stable download link via Internet Archive: https://web.archive.org/web/20211128125004/https://cdn.etcconnect.com/Hog_4… $ sha1sum Hog_4_PC_3.17.0.3327.msi.zip f98421bbbb0590df0e65ac18903471dd5fb61b6a Hog_4_PC_3.17.0.3327.msi.zip $ du -sh Hog_4_PC_3.17.0.3327.msi.zip 361M Hog_4_PC_3.17.0.3327.msi.zip $ sha1sum Hog_4_PC_3.17.0.3327.msi 0d22bf13c5a9bb682820ee6f690a866c1b320d9b Hog_4_PC_3.17.0.3327.msi $ wine --version wine-6.22-204-gf03933fbb73 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 9

[Bug 60436] New: Wondershare Filmora crashes on video export: unimplemented function msvcp120.dll._Mtx_timedlock
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60436 Bug ID: 60436 Summary: Wondershare Filmora crashes on video export: unimplemented function msvcp120.dll._Mtx_timedlock Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)list.winehq.org Reporter: italopaesano.shopping(a)gmail.com Target Milestone: --- Distribution: --- Component/version: Wine 11.0 (wow64 build), builtin msvcp120.dll (Visual C++ 2013 runtime). _Mtx_timedlock is the timed-lock primitive behind std::timed_mutex / std::recursive_timed_mutex. Reproducer: Wondershare Filmora (tested on 15.7.25.21914 and 16.0.10.22341, both affected identically). Import any clip with an audio track, drag it to the timeline, start an export with default settings. Shortly after the export starts, Filmora crashes and shows its own bug-report window. Exact error (from Wine's output, one line): wine: Call from ... to unimplemented function msvcp120.dll._Mtx_timedlock, aborting Why this is easy to misattribute: Filmora writes its own crash dump under .../log/FreezeDump_<date>/, with an exit code of 0x80000100 and files named handle_leak_analysis.json / memory_leak_analysis.json - this looks like a resource-leak or performance problem, and Filmora's own application log shows no "Exception Signal" at that point, unlike an ordinary crash. The real cause only shows up in Wine's own log. Note on the builtin DLL: the export table of the builtin msvcp120.dll does list _Mtx_timedlock - so a superficial "does the DLL export this symbol" check looks fine. It is only present as a stub; only actually calling it reveals that. winedump -j export msvcp120.dll (Filmora's own bundled native copy) | grep _Mtx_timedlock -> present, implemented winedump -j export .../system32/msvcp120.dll (builtin) | grep _Mtx_timedlock -> export exists, but it is the unimplemented stub Workaround that works, no installs needed: Filmora bundles Microsoft's native msvcp120.dll in its own install directory, so WINEDLLOVERRIDES="msvcp120=n,b" (native first, builtin fallback) avoids the crash entirely. Verified end-to-end with a real export (ffprobe/ffmpeg integrity check on the output file, zero decode errors). Environment: NixOS 26.05, Wine 11.0 wow64 build, win64 prefix, Windows 10 (build 19045, default, unmodified). -- 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 52527] New: Death Stranding fails to start
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=52527 Bug ID: 52527 Summary: Death Stranding fails to start Product: vkd3d Version: 1.2 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- fixme:debug_vk_memory_property_flags: Unrecognized flag(s) 0xc0. --------- error.txt --------- Your graphics card Radeon RX 5500M does not support DirectX 12 features 0. 0x0001417D2188 ds, 0x417D2188 1. 0x0001417CE263 ds, 0x417CE263 2. 0x0001423EC291 ds, 0x423EC291 3. 0x0001423E94FE ds, 0x423E94FE 4. 0x0001416A5679 ds, 0x416A5679 5. 0x0001416A5A0A ds, 0x416A5A0A 6. 0x0001416A5896 ds, 0x416A5896 7. 0x000143714832 ds, 0x43714832 8. 0x00007B64C371 kernel32, 0x7B64C371 9. 0x7F19D1C389D8 ntdll, 0xD1C389D8 10. 0x000000000000 11. 0x0001437148A4 ds, 0x437148A4 12. 0x000067FF0000 13. 0x000000000000 vkd3d-1.2-764-gdbcf0634 -- 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 48217] New: shadermap crushes with this report
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48217 Bug ID: 48217 Summary: shadermap crushes with this report Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexandrovitchevich(a)gmail.com Distribution: --- Created attachment 65848 --> https://bugs.winehq.org/attachment.cgi?id=65848 this is Log, generated after this error and error message screenshot I can see: Unhandled exception: unimplemented function msvcr120.dll.? I tried to install visual c++ 2013 as a solution but it doesnt help. Prewiosly I used it on windows 8 and 10 with the same hardware, so its OK. This is last update of shadermap software. I really need it to run coz no such good alternative for linux. Thanks for help! PS: I added zip archive coz I added error message screenshot with bug report file. -- 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 60419] New: zsh: bad CPU type in executable: /Applications/Wine Stable.app/Contents/MacOS/wine
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60419 Bug ID: 60419 Summary: zsh: bad CPU type in executable: /Applications/Wine Stable.app/Contents/MacOS/wine Product: Wine Version: 6.2 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: benhassine.anis(a)gmail.com Target Milestone: --- Created attachment 82225 --> http://bugs.winehq.org/attachment.cgi?id=82225 Apple message zsh: bad CPU type in executable: /Applications/Wine Stable.app/Contents/MacOS/wine macOS 26.6.2 (25G83) -- 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 60435] New: A Plague Tale: Requiem shows a black screen with sound after launch
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60435 Bug ID: 60435 Summary: A Plague Tale: Requiem shows a black screen with sound after launch Product: vkd3d Version: 2.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 82248 --> http://bugs.winehq.org/attachment.cgi?id=82248 output With lots of 'vkd3d:0688:fixme:vkd3d:d3d12_pipeline_state_GetCachedBlob iface 00007FFFF975D090, blob 00007FE30477EA98 stub!' vkd3d-2.1-82-g6ee3db29 -- 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 0

[Bug 60034] New: Resource Hacker v5.2.8 crashes on startup with NtRaiseException (Regression in Wine 11.13, worked in 10.6)
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60034 Bug ID: 60034 Summary: Resource Hacker v5.2.8 crashes on startup with NtRaiseException (Regression in Wine 11.13, worked in 10.6) Product: Wine Version: 11.13 Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: ssnffb30(a)gmail.com Target Milestone: --- Created attachment 81469 --> http://bugs.winehq.org/attachment.cgi?id=81469 Terminal output when crashing on startup Resource Hacker v5.2.8 crashes immediately on startup when running on Wine Devel 11.13. This appears to be a regression, as it was working perfectly in Wine Devel 10.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 13

[Bug 60434] New: Borderlands GOTY Enhanced: severe ghosting with anti-aliasing enabled in WineD3D/OpenGL
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60434 Bug ID: 60434 Summary: Borderlands GOTY Enhanced: severe ghosting with anti-aliasing enabled in WineD3D/OpenGL Product: Wine Version: 11.0-rc4 Hardware: x86-64 URL: https://store.steampowered.com/app/729040/Borderlands_ Game_of_the_Year_Enhanced/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: gyebro69(a)gmail.com CC: matteo.mystral(a)gmail.com Target Milestone: --- Regression SHA1: 3d9b48bc5e443f83653faf48653573da880d9008 Distribution: --- Created attachment 82247 --> http://bugs.winehq.org/attachment.cgi?id=82247 screencast demonstrating the issue Borderlands GOTY Enhanced (64-bit, Direct3D 11) exhibits severe ghosting and persistent image trails when using the WineD3D OpenGL renderer with in-game anti-aliasing enabled. When moving the camera, displaced copies of object outlines and scene details remain visible, producing overlapping contours and smeared trails. Similar artifacts appear around moving or animated objects even when the camera is stationary. After stopping camera movement, the artifacts in stationary parts of the scene gradually disappear within approximately 1–2 seconds. They reappear when the camera moves again. Please see the attached video. Disabling in-game anti-aliasing eliminates the issue. The issue is reproducible with: - Both legacy shared-WoW64 and new WoW64 builds. - NVIDIA proprietary driver 615.71.09 and Nouveau with Mesa 26.2.4. - X11, XWayland, and native Wayland. - Both EGL and GLX OpenGL backends. The regression is caused by commit 3d9b48bc5e443f83653faf48653573da880d9008 wined3d/gl: Split UBOs to separate chunks The commit still reverts cleanly on Wine 11.19. Reverting it eliminates the ghosting artifacts with in-game anti-aliasing enabled. Wine 11.19 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 615.71.09 -- 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 0

[Bug 60426] New: PC Pup installer freezes under new WoW64
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60426 Bug ID: 60426 Summary: PC Pup installer freezes under new WoW64 Product: Wine Version: 11.19 Hardware: x86-64 URL: https://archive.org/details/pc-pup OS: Linux Status: UNCONFIRMED Keywords: download, Installer, win16, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: lingm+winebz(a)posteo.org Target Milestone: --- Distribution: ArchLinux Running the SETUP.EXE under new WoW64 shows a small, empty, all-black window with the title "Setup". Nothing further happens and the window has to be killed since closing it normally does not work. Not a single line of console output is printed. With old WoW64 it bets a bit further but then runs into bug 45707. The ISO: > $ sha256sum "3D Pets - PC Pup (1998)(Neechez Innovation).iso" > 5f18b203e9afab09df778ab54a05edd43895b7bd321b83d44c6995577cf1cd9c 3D Pets - PC Pup (1998)(Neechez Innovation).iso > $ du -h "3D Pets - PC Pup (1998)(Neechez Innovation).iso" > 174M '3D Pets - PC Pup (1998)(Neechez Innovation).iso' The setup.exe itself: > $ sha256sum SETUP.EXE > 93e9849c90bba09e78170720a89c061948af454e1bbdb095dcee7ba4bae11095 SETUP.EXE > $ du -h SETUP.EXE > 12M SETUP.EXE -- 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 45707] New: PC Pup: Setup hangs - "syslevel.c: Win16Mutex" wait timed out
by wine-bugs＠winehq.org Oct. 5, 2026

Oct. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=45707 Bug ID: 45707 Summary: PC Pup: Setup hangs - "syslevel.c: Win16Mutex" wait timed out Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: wyattmeister(a)gmail.com Distribution: --- Created attachment 62136 --> https://bugs.winehq.org/attachment.cgi?id=62136 Dialogue box with progress bar The game is PC Pup by Neechez Innovation When I try to run setup.exe, a dialogue box with a progress bar appears, which fills to 100%, and then hangs. The program then stops drawing to the screen, and after a while, this appears in the terminal: 002f:err:ntdll:RtlpWaitForCriticalSection section 0x7e78d340 "syslevel.c: Win16Mutex" wait timed out in thread 002f, blocked by 0030, retrying (60 sec) Have tried using single-threading, and also tried Windows 95 and Windows XP in winecfg, to no avail. -- 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 48078] New: Astro Avenger 2 fails to run with seh:setup_exception_record stack overflow
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48078 Bug ID: 48078 Summary: Astro Avenger 2 fails to run with seh:setup_exception_record stack overflow Product: Wine Version: 4.19 Hardware: x86-64 URL: https://astro-avenger.en.softonic.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iodreamify(a)gmail.com Distribution: Ubuntu Created attachment 65628 --> https://bugs.winehq.org/attachment.cgi?id=65628 winedebug warn+all log Astro Avenger 2 manages to launch but clicking "Run" in the launcher makes the game freeze forever with a "002a:err:seh:setup_exception_record stack overflow 816 bytes in thread 002a eip 00ac1926 esp 00231000 stack 0x230000-0x231000-0x330000" error. Tried it both in 64bit and 32bit prefixes in windows 7, XP, 2000 and 98 modes and also disabling csmt.I've added a winedebug=warn+all log below. A demo 60 min trial can be found at the link above. I've also done a +relay log but i'm not sure if it's relevant. Thank you. -- 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 57796] New: Testcomplete fails to authenticate license key
by WineHQ Bugzilla Oct. 5, 2026

Oct. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=57796 Bug ID: 57796 Summary: Testcomplete fails to authenticate license key 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: francisco278herrera(a)gmail.com Distribution: --- Testcomplete fails to authenticate license key, this is not very obvious when running it on vanilla wine but if you run wine staging i believe it becomes more visible. i have attached the full console output from installation onwards using winetricks since i had difficulty saving console output for just the program. i ran the installer which then opens the program on it's own, the program itself starts to run with the first line that says 01f8:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot in the terminal. in vanilla wine the program installs successfully then opens a browser window to obtain a license key which fails silently and the program closes, then the program refuses to open past the splash screen. when the program fails it closes with 0994:err:menubuilder:InvokeShellLinker failed to extract icon from L"C:\\Program Files (x86)\\SmartBear\\TestComplete 15\\Help\\Getting Started With TestComplete 15.doc" in the terminal in wine staging i believe, the program behaves largely the same way but when authentication fails, the program says it failed to communicate with the backend or something similar. then when you close the program and open it again it gives an error about not being able to start or find the sentinel license? service or it gives an error about not having an active license? if i remember correctly the sentinel error appears the first time you try to open the program yourself, the license error appears the second time you try. based on what i have seen in game anticheat, the CreateToolhelp32Snapshot is used to verify a system's integrity so it is possible the program is not running due to the sentinel? DRM not being able to determine, or failing the system's integrity, not entirely sure this can be fixed in wine since they could just look at running wine processes and determine that it's not a windows system maybe? -- 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 12

[Bug 48363] New: Adobe Creative Cloud Installer shows blank window
by WineHQ Bugzilla Oct. 4, 2026

Oct. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=48363 Bug ID: 48363 Summary: Adobe Creative Cloud Installer shows blank window Product: Wine Version: 5.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ajg02(a)elfringham.co.uk Distribution: --- Created attachment 66106 --> https://bugs.winehq.org/attachment.cgi?id=66106 Console log for Set-up.exe Clean Wine prefix set to Win10 runs Set-up.exe for CC installer which shows a blank window. See attachment for console log. -- 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 6