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

[Bug 59522] explorerframe: ITaskbarList3 SetProgressValue/SetProgressState stubs - could use native desktop backends

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59522 Robert-Gerigk(a)online.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Robert-Gerigk(a)online.de --- The COM threading deadlock in ITaskbarList3 was fixed upstream in Wine 11.5. The remaining shcore Set/GetCurrentProcessExplicitAppUserModelID part was tracked as bug 59625 and is fixed in Wine 11.7 (MR !10565). FIXED in 11.5 / 11.7. -- 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.

May 27, 2026

[Bug 59604] setupapi: CM_Get_Parent stub breaks USB HID device identification

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59604 --- Comment #5 from Robert-Gerigk(a)online.de --- merged, perhaps in Wine 11.10: https://gitlab.winehq.org/wine/wine/-/merge_requests/10604 -- 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.

May 27, 2026

[Bug 59778] VOCALOID 6 VST3 crash on GUI initialization (.NET/OLE fixme error under Wine)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #20 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to dominikgx from comment #19) > I suspect this is not going > to be done in the foreseeable future? (by means, it depends?) > > d3d dlls and support for the installer. Is this bug report now set on freeze > by now? Or can you elaborate, if you continue to work on supporting the > program? d3d dll issues with you report seem more a problem caused by whatever bottles mechanism you are using vs a wine so d3d hardly seems a problem for this bug overall so far. Rather the installer not fully working seems to be the first major bug to solve so that manual registry edits are not required. I don't consider this issue frozen and will continue working to fixing the installer. You should be aware that many yabridge users are stuck using wine 9.21 due to a bug that emerged after that version: https://bugs.winehq.org/show_bug.cgi?id=58552 https://github.com/robbert-vdh/yabridge/issues/382 Wine had a bug for 9.21 and prior that yabridge was dependent upon so when it was fixed it broke yabridge causing GUI offset bugs and their dev team seem not to know how to fix it for compatibility with versions of wine later than 9.21. Unclear if bugs that cause yabridge users to revert to 9.21 are relevant for VOCALOID6 because it only effects VST GUI offsets but VOCALOID6 VST has no GUI components and instead just acts as a placeholder/bridge to the VOCALOID standalone Editor which seems to behave as a regular app rather than a VST. However, if you intend to use other VSTs along with VOCALOID via yabridge, then you'll likely encounter GUI offset bugs. It's an unfortunate but if yabridge compatibility issues are too difficult to resolve then perhaps a new bridge project more aligned with wine should be created to better handle VST compatibility with latest wine releases. -- 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.

May 27, 2026

[Bug 59778] VOCALOID 6 VST3 crash on GUI initialization (.NET/OLE fixme error under Wine)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #19 from dominikgx(a)gmail.com --- Thank you very much for your detailed information on the current state of the wine compatibility layer and your support. I suspect this is not going to be done in the foreseeable future? (by means, it depends?) I really intended creating music on Linux using V6 and I'm sure more people are out there. d3d dlls and support for the installer. Is this bug report now set on freeze by now? Or can you elaborate, if you continue to work on supporting the program? -- 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.

May 27, 2026

[Bug 59778] VOCALOID 6 VST3 crash on GUI initialization (.NET/OLE fixme error under Wine)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #18 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Nikolay Sivov from comment #16) > From your log a more likely reason is this: > > 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] wine: Call from > 00006FFFFE219628 to unimplemented function dxgi.dll.DXGID3D10CreateDevice, > aborting > 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] > 053c:err:seh:user_callback_handler ignoring exception 80000100 Indeed it seems whatever bottle methods being used to enable/disable renderering are nuking d3d dlls as I pointed out earlier: https://bugs.winehq.org/show_bug.cgi?id=59778#c8 Once missing d3d dlls is fixed again then missing registry entries for 8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003 become relevant. -- 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.

May 27, 2026

[Bug 59778] VOCALOID 6 VST3 crash on GUI initialization (.NET/OLE fixme error under Wine)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #17 from Stian Low <wineryyyyy(a)gmail.com> --- Created attachment 81039 --> http://bugs.winehq.org/attachment.cgi?id=81039 Screenshots for 8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003 registry missing bug and fixes (In reply to dominikgx from comment #14) > In OpenGL and DXVK this is the actual function which seems to be missing? I > found it in both logs. > > 07b0:fixme:ole:CoCreateInstanceEx no instance created for interface > {00000000-0000-0000-c000-000000000046} of class > {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003}, hr 0x80131604. This log indeed is problematic and may be caused by ongoing installer bugs that still need to be fixed: 07b0:fixme:ole:CoCreateInstanceEx no instance created for interface {00000000-0000-0000-c000-000000000046} of class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003}, hr 0x80131604. VOCALOID6 installer errors have been reported so despite it seemingly working for some test cases, it should probably not be assumed stable/reliable for wine yet: https://bugs.winehq.org/show_bug.cgi?id=59788 https://bugs.winehq.org/show_bug.cgi?id=56482 Wine ./pfx/system.reg is missing CLSID entry for 8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003 which exists for Windows registry (screenshot) as "Yamaha.VOCALOID.VST.VSTPluginController" which is probably missing because of the installer bugs. Install err logs which may cause registry update to fail: 02e8:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 00007FFFFE20FE80 026c:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=2680000026c, oid=2 026c:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d Manually creating missing registry entries partially fixes for Windows Bitwig via wine which allows VST to successfully open VOCALOID6 editor (screenshot). These lines were added to wine prefix system.reg to fix the logs and have the VST attempt to launch the Editor: [Software\\Classes\\CLSID\\{8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003}] 1779694646 #time=1dcec19555275cc @="Yamaha.VOCALOID.VST.VSTPluginController" [Software\\Classes\\CLSID\\{8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003}\\InprocServer32] 1779694646 #time=1dcec19555275cc @="C:\\Program Files\\VOCALOID6\\Editor\\VOCALOID6Plugin.comhost.dll" "ThreadingModel"="Both" [Software\\Classes\\CLSID\\{8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003}\\ProgId] 1779694646 #time=1dcec19555275cc @="Yamaha.VOCALOID.VST.VSTPluginController" Linux Bitwig VST fails to open VOCALOID6 Editor and crashes the plugin. Clicking reload plugin button within Bitwig just repeats this fail indefinitely. Linux Ardour succeeds in opening VOCALOID6 Editor but the app goes into not responding state. Windows Ardour via wine crashes when opening VOCALOID Editor. Because Windows Bitwig via wine seems most compatible with VOCALOID6, it may be worth testing first and building off of it since yabridge may be a factor for Linux-based DAW bugs. Just keep in mind that since Windows Ardour crashes also, Windows Bitwig may have additional issues that may require installer fixed first. Also, until causes of VOCALOID6 crashes for new vs old WoW64 is resolved, old seems recommended for progress testing VOCALOID6 support by wine: https://bugs.winehq.org/show_bug.cgi?id=59788 Continuing to work these issues. -- 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.

May 27, 2026

[Bug 59799] New: odbc32: SQLSetConnectAttr returns SQL_ERROR for unknown driver-specific connection attributes instead of forwarding to the driver

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59799 Bug ID: 59799 Summary: odbc32: SQLSetConnectAttr returns SQL_ERROR for unknown driver-specific connection attributes instead of forwarding to the driver Product: Wine Version: unspecified Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: odbc Assignee: wine-bugs(a)list.winehq.org Reporter: arthur.talpaert_winehq(a)m4x.org Description Per the ODBC specification, the driver manager's SQLSetConnectAttr must forward attributes outside the standard range (≥ SQL_CONNECT_OPT_DRVR_START = 1000) to the underlying driver's SQLSetConnectAttr without validation. Wine's odbc32 implementation has a hardcoded switch over known attribute IDs and returns SQL_ERROR for anything else, logging fixme:odbc:SQLSetConnectAttr unhandled attribute <N>. This breaks every modern SQL Server client built on Microsoft ODBC Driver 17/18, which routinely sets vendor-specific attributes: 1219 — SQL_COPT_SS_ENCRYPT 1224 — SQL_COPT_SS_TRUST_SERVER_CERTIFICATE 1226 — SQL_COPT_SS_APPLICATION_INTENT 1227 — SQL_COPT_SS_MULTI_SUBNET_FAILOVER Steps to reproduce Install Microsoft ODBC Driver 17 for SQL Server (msodbcsql.msi) into a Wine prefix. Run any application that calls SQLSetConnectAttr with SQL_COPT_SS_TRUST_SERVER_CERTIFICATE (1224) on the connection handle before SQLConnect. Concrete reproducer: GMC PaDok 5.0.5.0 client installer (setup_gmcpadok_5050.exe) pointed at any SQL Server with a default self-signed TLS cert. Expected SQLSetConnectAttr forwards the call to the driver's SQLSetConnectAttr, which honors it (the MS driver does). SQLConnect then proceeds with the trust-cert flag set. Actual SQLSetConnectAttr returns SQL_ERROR (-1). SQLGetDiagRec returns SQL_NO_DATA (Wine populated no diagnostic record). The application gives up before any TCP connection to SQL Server is attempted. Trace excerpt (with WINEDEBUG=-fixme,+odbc) 0214:trace:odbc:SQLSetConnectAttr (ConnectionHandle …, Attribute 103, Value 0000000F, …) Returning 0 0214:trace:odbc:SQLSetConnectAttr (ConnectionHandle …, Attribute 113, Value 0000001E, …) Returning 0 0214:trace:odbc:SQLSetConnectAttr (ConnectionHandle …, Attribute 1224, Value 00000001, …) 0214:fixme:odbc:SQLSetConnectAttr unhandled attribute 1224 0214:trace:odbc:SQLSetConnectAttr Returning -1 0214:trace:odbc:SQLGetDiagRec (…) Returning 100 0214:trace:odbc:SQLFreeHandle (HandleType 2, …) Proposed fix Wine's odbc32 should forward SQLSetConnectAttr calls for attributes ≥ 1000 (SQL_CONNECT_OPT_DRVR_START) directly to the underlying driver via the proxy table, without validation. Attributes < 1000 that are not in the manager's known set may still be rejected with SQL_ERROR, but with a populated diagnostic record per spec. Workarounds None known. WINEDLLOVERRIDES can replace odbc32 itself, but Microsoft ODBC Driver 17 doesn't ship its own driver manager. Installing native macOS unixODBC + Microsoft's native msodbcsql17 and putting Wine into Unix-proxy mode (libodbc.dylib) is untested and would also still hit downstream FILESTREAM-IOCTL issues unrelated to this bug. -- 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.

May 27, 2026

[Bug 59778] VOCALOID 6 VST3 crash on GUI initialization (.NET/OLE fixme error under Wine)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #16 from Nikolay Sivov <bunglehead(a)gmail.com> --- From your log a more likely reason is this: 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] wine: Call from 00006FFFFE219628 to unimplemented function dxgi.dll.DXGID3D10CreateDevice, aborting 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] 053c:err:seh:user_callback_handler ignoring exception 80000100 -- 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.

May 27, 2026

[Bug 59778] VOCALOID 6 VST3 crash on GUI initialization (.NET/OLE fixme error under Wine)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 dominikgx(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|VOCALOID6 VST3 doesn't load |VOCALOID 6 VST3 crash on | |GUI initialization | |(.NET/OLE fixme error under | |Wine) -- 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.

May 27, 2026

[Bug 59778] VOCALOID6 VST3 doesn't load

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59778 dominikgx(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #81030|0 |1 is obsolete| | Attachment #81037|0 |1 is obsolete| | --- Comment #15 from dominikgx(a)gmail.com --- Created attachment 81038 --> http://bugs.winehq.org/attachment.cgi?id=81038 WINEDEBUG VOCALOID 6 VST3 plugin fails to initialize GUI with yabridge under Wine due to .NET COM/OLE instantiation failure (CoCreateInstanceEx error for CLSID_CorRuntimeHost). Can someone fix this? :) -- 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.

May 27, 2026