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

[Bug 54784] New: mIRC 7.72 crashes after restoring from application tray
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=54784 Bug ID: 54784 Summary: mIRC 7.72 crashes after restoring from application tray Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dragone2(a)risposteinformatiche.it Distribution: --- Created attachment 74279 --> https://bugs.winehq.org/attachment.cgi?id=74279 Unhandled exception: page fault on read access - mIRC - Wine-staging 8.5 mIRC was running for about 4-5 hours before the crash. It was reduced on the tray and its icon was blinking to notify that there were new messages / activities in channels or private messages. I clicked on it to restore the window and see the messages and wine gave me this backtrace (see the attachment). I was forced to quit mIRC and restart it again. This rarely happens, so it's not a real problem for me, but I don't know if it could help you fix this. Other infos: - Executable path: D:\mIRC\mirc.exe - mIRC Version: 7.72 (the latest one). - mIRC running in portable mode from a specific drive (on Wine, D:\) formatted in NTFS. - mIRC was running using some custom scripts. But this crash never happen on Windows. - Distro: Linux Mint 21.1 with latest updates. - Kernel: 5.15.0-69-generic - Wine infos: Wine build: wine-8.5 (Staging) Platform: i386 (WOW64) Version: Windows 10 - Drive Z: is a drive formatted in BTRFS. - CPU: Intel Core i7-6700 - RAM: 32 GB, when the crash occurred I was using less than 8 GB. -- 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 11

[Bug 58913] New: Photoshop CC interface is broken on recent wine dev
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=58913 Bug ID: 58913 Summary: Photoshop CC interface is broken on recent wine dev Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeff.artik(a)gmail.com Distribution: --- Created attachment 79593 --> http://bugs.winehq.org/attachment.cgi?id=79593 Terminal output Since recent Wine versions, the Photoshop interface is broken. Here is the difference between Wine stable 10.0 and Development Wine 10.18: Wine stable 10.0: https://imgur.com/SiReCp1 Development Wine 10.18: https://imgur.com/64qDG92 -- 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 23

[Bug 59714] New: Add support for loading and executing ring-0/ring-1 virtualization drivers (Hypervisor bypass/Custom VBS)
by WineHQ Bugzilla May 3, 2026

May 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59714 Bug ID: 59714 Summary: Add support for loading and executing ring-0/ring-1 virtualization drivers (Hypervisor bypass/Custom VBS) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)list.winehq.org Reporter: vidyutsanthosh4(a)gmail.com Distribution: --- Hello developers, First off, thanks for your work on Wine and for all that you do. I want to bring up the topic of one of Wine's limitations related to its ability to run software depending on kernel-mode drivers and hypervisor-based features. Summary Some new applications have requirements of: Custom kernel-mode drivers Virtualization-based protection mechanisms Execution in virtualization-assisted mode (such as usage of VT-x / AMD-V) Such apps fail to start with Wine because: Wine lacks any possibility to load and execute kernel-mode Windows drivers There is no way to access host-level virtualization features Implementation of ntoskrnl is not capable to handle such situations Observed behavior When started: Drivers cannot load successfully or report errors Sometimes, Wine might crash or terminate without reason There are no errors that hint at necessity of virtualization or kernel-mode execution Expected / desired behavior While I know that full support of kernel-mode drivers and hypervisor-level execution is not in Wine's roadmap. It would still be nice to see the following improvements made: Detection and diagnostics Detect if the application tries to: Load kernel-mode driver Utilize virtualization instructions or hypervisor APIs Display an error that explicitly states that such functionality is not supported by Wine Documentation improvements Documentation about: Restrictions around kernel-mode execution Incompatibility of applications dependent on virtualization features Alternatives in running such programs (e.g. KVM-based VM) Research in possible hybrid solutions (long-term) Look into possible ways to integrate with the host OS's virtualization (e.g. KVM), possibly for selected scenarios, even if partially Some kind of experimental flag or limited feature set could be useful for research and tooling purposes Use cases Better diagnostics of the issue would be useful for: Debugging of incompatibilities Running software which requires virtualization or kernel-mode operation Development tools that need low-level control of the system Closing notes I realize that Wine cannot provide kernel-mode and hypervisor-based features. My suggestion rather focuses on: Visibility into the issue Improved handling of such applications Error reporting -- 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 55827] New: Can't install Scratch3
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=55827 Bug ID: 55827 Summary: Can't install Scratch3 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zuomug67(a)gmail.com Distribution: --- Created attachment 75319 --> https://bugs.winehq.org/attachment.cgi?id=75319 backtracefile Can'tinstall Scratch3 -- 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 3

[Bug 51850] New: does not start MediaCreationTool21H1.exe
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=51850 Bug ID: 51850 Summary: does not start MediaCreationTool21H1.exe Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 79625490833(a)yandex.ru Distribution: --- Created attachment 70744 --> https://bugs.winehq.org/attachment.cgi?id=70744 backtrace Hello. Does not start MediaCreationTool21H1.exe Operating System: ROSA Fresh Desktop 2021.1 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.10.70-generic-2rosa2021.1-x86_64 (64-bit) Graphics Platform: X11 Processors: 6 × AMD FX(tm)-6300 Six-Core Processor Memory: 7.7 ГиБ of RAM Graphics Processor: NVC1 -- 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 10

[Bug 54566] New: Speed Busters: not clickable buttons in main menu
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=54566 Bug ID: 54566 Summary: Speed Busters: not clickable buttons in main menu Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stabilergriller(a)gmail.com Distribution: --- Created attachment 74107 --> https://bugs.winehq.org/attachment.cgi?id=74107 Wine Output running programm Hello, The game "Speed Busters: American Highways" [https://appdb.winehq.org/objectManager.php?sClass=application&iId=2832] bought on GOG [https://www.gog.com/game/speed_busters] installs just fine, but it's not possible to progress beyond the main menu. The main menu is fully visible, the mouse cursor itself too, but it's not actually possible to click on any of the buttons (or other interactive elements). Nothing seems to happen, when clicking on anything. Note: In winecfg, it's necessary to "Emulate a virtual desktop". Otherwise the game will start in full screen mode, and due to that described non-interactivity, it becomes impossible to leave the game anymore, so you will get perpetually stuck unless rebooting the computer. When alt tabbing the game running in full screen mode, it can be seen that an error window from wine is produced in the background, which is not readable, because the game always immediately commands control back. -- 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

[Bug 54979] New: Futexes which protect memory allocation congest, causing 100x performance degradation
by WineHQ Bugzilla May 3, 2026

May 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=54979 Bug ID: 54979 Summary: Futexes which protect memory allocation congest, causing 100x performance degradation Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: nagle(a)animats.com Distribution: --- Created attachment 74518 --> https://bugs.winehq.org/attachment.cgi?id=74518 Debugger output with multiple threads stuck in spinlocks. SUMMARY Under the wrong circumstances, a program doing many memory allocations from multiple threads can experience more than 100x performance degradation. I'm seeing this in my own Rust program, which has 16 sometimes-compute-bound threads on a 12 CPU machine. This works fine on Microsoft Windows and when compiled for Linux. Under Wine, it can be over 100x slower. Multiple threads are banging on a spinlock at _InterlockedCompareExchange [Z:\usr\src\packages\BUILD\include\winnt.h:6630] in ntdll spin_lock [Z:\usr\src\packages\BUILD\dlls\ntdll\sync.c:937] in ntdll This is the spin lock around the queue for pausing threads. DISCUSSION This looks like futex congestion. That's a known kind of problem, but doesn't seem to have been seen in Wine before. It may be that some programs just run really slow under Wine, and nobody knows why. The code in NTDLL is clearly intended to handle the fast case without doing an OS-level lock. Under light load, that's O(1). But under heavy load, with multiple threads pounding on spinlocks, each spinlock waits longer, and there are multiple threads, so it becomes O(N^2). Which means huge slowdowns. See discussion at https://forum.winehq.org/viewtopic.php?t=37688 which has snippets of the code that's causing the problem. I can copy all that info over here if necessary. Let me know. -- 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 21

[Bug 54414] New: Window content corrupted after using scrollbars
by WineHQ Bugzilla May 2, 2026

May 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=54414 Bug ID: 54414 Summary: Window content corrupted after using scrollbars Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maranbr(a)outlook.com Distribution: --- Created attachment 73975 --> https://bugs.winehq.org/attachment.cgi?id=73975 Window content after scroll The window content gets completely corrupted after use scroll bars. Tested on versions 4.x, 5.x, 6.x, 7.x and the last one available, the 8.0. -- 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 8

[Bug 59713] New: タダポックスのレビュー – 作用機序と有効性
by WineHQ Bugzilla May 2, 2026

May 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=59713 Bug ID: 59713 Summary: タダポックスのレビュー – 作用機序と有効性 Product: Wine-staging Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tisiyumei5(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 80852 --> http://bugs.winehq.org/attachment.cgi?id=80852 シルダリストは、勃起不全（ED）の治療に一般的に処方される医薬品です。有効成分としてシルデナフィルとタダラフィルを含有しています。これらはいずれもPDE5阻害薬であり、勃起を引きタダポックスは、男性によく見られる性機能の問題に対処するため、体内で強力な二重作用を発揮する複合製剤です。服用すると、タダポックスは素早く溶解して血流に入り、それぞれの有効成分がその働きを始めます。 https://kaigaikusuri.com/product/tadapox/ PDE5阻害剤であるタダラフィルは、一酸化窒素の作用を増強することで、陰茎への血流を増加させ、勃起を促進します。同時に、選択的セロトニン再取り込み阻害剤であるダポキセチンは、神経伝達物質の活動を調節し、射精を遅らせるのに役立ちます。これら2つの成分が相乗効果を発揮することで、親密さと性的満足度を高める包括的な解決策を提供します。タダポックスの用途タダラフィル＋ダポキセチンは、勃起不全および早漏の治療に使用されます。タダラフィル＋ダポキセチンの具体的な用途は以下の通りです：勃起不全の管理：タダラフィル＋ダポキセチンは、勃起不全の男性が性行為中に勃起を達成し、維持できるよう支援するために一般的に処方されます。性的パフォーマンスの向上：タダラフィル＋ダポキセチンは陰茎への血流を増加させ、性的反応の改善を可能にします。心理的要因へのサポート：タダラフィル＋ダポキセチンは、身体的反応を高めることで、不安やストレスといった勃起不全の心理的要因への対処を支援します。早漏の治療：タダラフィル＋ダポキセチンは、早漏に関連する問題の管理に役立ち、より満足のいく性生活の実現に寄与する可能性があります。生殖機能の健康維持：勃起不全に対処することで、タダラフィル＋ダポキセチンは男性の生殖機能全般の健康をサポートし、生殖能力の向上につながる可能性があります。タダポックスはどのように作用するのでしょうか？多くの患者さんから「タダポックスは効果がありますか？」という質問をいただきます。答えは「はい」です。その理由は以下の通りです：タダラフィルは陰茎の血管を弛緩させ、性的刺激を受けた際に血流を増加させます。その効果は最大36時間持続するため、「週末の錠剤」という愛称で親しまれています。ダポキセチンは神経系におけるセロトニン濃度を上昇させ、射精を遅らせ、コントロール力を向上させます。効果は迅速に現れ（1～2時間以内）、性交時間の延長に役立ちます。より強く、より確実な勃起より長く持続する性機能ベッドでの自信の向上 ED治療におけるタダポックス使用のメリットタダラフィルとダポキセチンの強力な組み合わせであるタダポックスは、勃起不全に悩む男性に様々なメリットをもたらします。タダポックスを使用する主な利点は以下の通りです：勃起の質の向上：タダポックスの有効成分であるタダラフィルは、陰茎への血流を増加させ、より良好で持続時間の長い勃起をもたらします。性機能の向上：ダポキセチンは射精までの時間を延長することで性機能を向上させ、親密なひとときにおいてより高いコントロールと満足感をもたらします。二重作用：タダポックスは、2つの強力な成分の利点を組み合わせることで、勃起不全の身体的および心理的側面の両方に働きかけ、包括的な解決策を提供します。副作用頭痛吐き気下痢消化不良視覚障害不安感めまい顔面紅潮注意事項以下の症状がある方は慎重に使用してください。腎機能障害肝機能障害心血管疾患出血性疾患成分に対する過敏症またはアレルギー心臓の合併症肝臓疾患女性への使用は推奨されません。警告小児および高齢者は使用しないでください。医師の処方箋に基づいて使用してください。飲酒は避けてください。めまいを引き起こす可能性があるため、運転はしないでください。よくある質問タダポックスの効果はどのくらい持続しますか？作用時間は2つの成分によって決まります。タダラフィル成分は、勃起不全に対して最大36時間という長い有効期間を提供します。タダポックスは毎日服用できますか？いいえ。タダポックス（タダラフィル20mg／ダポキセチン60mg）の固定用量配合剤は、毎日の服用については承認されておらず、その点に関する研究も行われていません。ダポキセチンは、必要に応じて服用するよう特別に設計されています。 -- 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 59695] New: load_init_registry_from_file takes a long time during wine boot
by WineHQ Bugzilla May 2, 2026

May 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=59695 Bug ID: 59695 Summary: load_init_registry_from_file takes a long time during wine boot Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)list.winehq.org Reporter: stephan.seitz(a)fau.de Distribution: --- Created attachment 80812 --> http://bugs.winehq.org/attachment.cgi?id=80812 Flamegraph showing time spend during wine boot Please excuse if this is a duplicated. I noticed that wine boot takes a long time on my machine. Being curious I ran perf (see flamegraph screenshot) on it and saw that most of the time (almost 16s) is spent during load_init_registry_from_file. I was wondering whether there is a faster way to deserialize the registry. I built wine from source 607d214b9b33be8ee7377f194a98c01a36af803c (2026/04/05) using `./configure && make -j20`. I have a wine prefix with some development tools installed. 28% of the overall boot time samples is spend in running the two `to_lower` in `memicmp_strW` server/unicode.c ``` static inline WCHAR to_lower( WCHAR ch ) { return ch + casemap[casemap[casemap[ch >> 8] + ((ch >> 4) & 0x0f)] + (ch & 0x0f)]; } int memicmp_strW( const WCHAR *str1, const WCHAR *str2, data_size_t len ) { int ret = 0; for (len /= sizeof(WCHAR); len; str1++, str2++, len--) if ((ret = to_lower(*str1) - to_lower(*str2))) break; return ret; } ``` so optimizing `memicmp_strW` would have a big impact on boot time (e.g. adding a fast path for ascii chars or adding vectorization if that is possible in the wine server and we are allowed to access memory past a possible \0 byte. If the registry would be stored as a case-insensitive filesystem or consistent with the in-memory representation of the registry it would maybe even be possible to skip deserialization or make it very cheap. -- 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