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

[Bug 53241] New: wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test?
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=53241 Bug ID: 53241 Summary: wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test? Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wtsapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits during the test? Here is the failure: wtsapi.c:78: Test failed: failed to find pid 0x20e4 wtsapi.c:82: this is the last test seen before the exception 0618:wtsapi: unhandled exception c0000005 at 0000000000401848 https://test.winehq.org/data/patterns.html#wtsapi32:wtsapi The crash happens when check_wts_process_info() dereferences the NULL pointer returned by find_nt_process_info(). So presumably the test must check that some API does return information about at least some processes but it seems allowances should be made for processes exiting during the test. -- 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 42383] New: certmgr.exe is unable to import certificate in PKCS12 format
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=42383 Bug ID: 42383 Summary: certmgr.exe is unable to import certificate in PKCS12 format Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: info(a)winomega.com Distribution: --- Created attachment 57178 --> https://bugs.winehq.org/attachment.cgi?id=57178 error message Microsoft Certificate Manager Tool (certmgr.exe) is unable to import PKCS12 files. When this is attempted it failed with following error: "The file format is not recognized. Please select another file." I'm using the 32-bit version as published in Microsoft Visual Studio 2017 (freely downloadable). Its md5sum is: 322bf8029866cf3eb7f1de33f18fb07a certmgr.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.

2 6

[Bug 39336] New: ...
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=39336 Bug ID: 39336 Summary: ... Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arienta.g(a)gmail.com Created attachment 52415 --> https://bugs.winehq.org/attachment.cgi?id=52415 it popped up when pressing audio play button Failed when pressing the play button for the audio to start -- 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 53047] New: "IDS_ERROR_NO_WIZARD_PAGES" on running Sketchup 2021 installer, native xmllite is workaround
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=53047 Bug ID: 53047 Summary: "IDS_ERROR_NO_WIZARD_PAGES" on running Sketchup 2021 installer, native xmllite is workaround Product: Wine Version: 7.9 Hardware: x86-64 URL: https://download.sketchup.com/SketchUpPro-2022-0-354-1 26.exe OS: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: xmllite Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Created attachment 72439 --> https://bugs.winehq.org/attachment.cgi?id=72439 +xmllite,+msgbox This was reported on the forum so I gave it a try. It gets a bit further with native xmllite but than there`s a messagebox with "Invalid Handle". This bug report is for the 1st messagbeox with IDS_ERROR_NO_WIZARD_PAGES, after which the installer quits. Attached a +xmllite,+msgbox trace -- 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 49078] New: Sennheiser Wireless Systems Manager 4.4 server (.NET 4.5 app) crashes with 'System.ComponentModel.Win32Exception: Unknown error (0x80090308)'
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=49078 Bug ID: 49078 Summary: Sennheiser Wireless Systems Manager 4.4 server (.NET 4.5 app) crashes with 'System.ComponentModel.Win32Exception: Unknown error (0x80090308)' Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. You need to work around bug 49076 ("Sennheiser Wireless Systems Manager 4.4 installer overwrites Wine builtin "system/os" dlls, causing broken WINEPREFIX (SfcIsFileProtected is a stub)") to fix the WINEPREFIX after installation. Download: https://web.archive.org/web/20200502103749/http://sennheiser-sites.com/resp… Prerequisite: 'winetricks -q dotnet45' --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files (x86)/Sennheiser/Wireless Systems Manager $ WINEDEBUG=+seh,+relay,+loaddll,+process,+secur32,+ntlm wine ./WSM.exe >>log.txt 2>&1 ... 00c8:Call KERNEL32.CreateProcessW(00000000,03ece868 L"\"C:\\Program Files (x86)\\Sennheiser\\Wireless Systems Manager\\WSMServerBinaries\\WSM.Server.exe\" ",00000000,00000000,00000001,08000400,00000000,00000000,0031f7f4,03ecbc10) ret=6711d6b5 ... 00c8:warn:process:CreateProcessInternalW (L"C:\\Program Files (x86)\\Sennheiser\\Wireless Systems Manager\\WSMServerBinaries\\WSM.Server.exe",...): ignoring some flags in 8000400 ... 00c8:trace:process:CreateProcessInternalW started process pid 00e4 tid 00e8 ... 00c8:Ret KERNEL32.CreateProcessW() retval=00000001 ret=6711d6b5 ... --- snip --- First call of 'InitializeSecurityContextW' (ntlm auth): --- snip --- ... 00e8:Call secur32.InitializeSecurityContextW(0021e128,00000000,021dd75c L"http/localhost",00020800,00000000,00000000,00000000,00000000,021df460,021df3d8,021dd8d0,0021e120) ret=64474db2c56 ... 00e8:trace:secur32:InitializeSecurityContextW 0x21e128 (nil) L"http/localhost" 0x00020800 0 0 (nil) 0 0x21df460 0x21df3d8 0x21dd8d0 0x21e120 ... 00e8:trace:ntlm:ntlm_InitializeSecurityContextW 0x1d51b20 (nil) L"http/localhost" 0x00020800 0 0 (nil) 0 0x21dd80 0x21df3d8 0x21dd8d0 0x21e120 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Setting SECURITY_NETWORK_DREP ... 00e8:trace:ntlm:ntlm_InitializeSecurityContextW First time in ISC() ... 00e8:Call advapi32.CredReadW(01d7ae80 L"localhost",00000002,00000000,0021db00) ret=7f1c15c86283 ... 00e8:Ret advapi32.CredReadW() retval=00000000 ret=7f1c15c86283 ... 00e8:trace:ntlm:ntlm_InitializeSecurityContextW using cached credentials 00e8:trace:ntlm:fork_helper "ntlm_auth" "ntlm_auth" "--helper-protocol=ntlmssp-client-1" "--username=focht" "--use-cached-creds" ... 00e8:trace:ntlm:run_helper In helper: sending "OK" 00e8:trace:ntlm:read_line Creating a new buffer for the helper ... 00e8:trace:ntlm:read_line offset = 0, size = 200 00e8:trace:ntlm:read_line read_size = 20, read: "BH Command expected\n " 00e8:trace:ntlm:read_line offset_len is calculated from 0x1d4ef74 - 0x1d4ef74 00e8:trace:ntlm:run_helper In helper: received "BH Command expected" 00e8:trace:ntlm:preserve_unused offset_len = 0 00e8:trace:ntlm:preserve_unused helper->com_buf_offset was set to: 0 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Sending to helper: "OK" 00e8:trace:ntlm:run_helper In helper: sending "OK" 00e8:trace:ntlm:read_line offset = 0, size = 200 00e8:trace:ntlm:read_line read_size = 20, read: "BH Command expected\n " 00e8:trace:ntlm:read_line offset_len is calculated from 0x1d4ef74 - 0x1d4ef74 00e8:trace:ntlm:run_helper In helper: received "BH Command expected" 00e8:trace:ntlm:preserve_unused offset_len = 0 00e8:trace:ntlm:preserve_unused helper->com_buf_offset was set to: 0 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Helper returned "BH Command expected" 00e8:trace:ntlm:run_helper In helper: sending "YR" 00e8:trace:ntlm:read_line offset = 0, size = 200 00e8:trace:ntlm:read_line read_size = 60, read: "YR xxx==\ns" 00e8:trace:ntlm:read_line offset_len is calculated from 0x1d4ef9c - 0x1d4ef9c 00e8:trace:ntlm:run_helper In helper: received "YR xxx==" 00e8:trace:ntlm:preserve_unused offset_len = 0 00e8:trace:ntlm:preserve_unused helper->com_buf_offset was set to: 0 00e8:trace:ntlm:ntlm_InitializeSecurityContextW YR xxx== 00e8:trace:ntlm:decodeBase64 in_len: 56 00e8:trace:ntlm:ntlm_GetTokenBufferIndex 0x21df3d8 ... 00e8:Ret secur32.InitializeSecurityContextW() retval=00090312 ret=64474db2c56 ... --- snip --- --- snip --- ... 00e8:Call secur32.AcceptSecurityContext(0021e168,00000000,021dff18,00000800,00000000,021dffe0,021dff38,021de8e8,0021e160) ret=64474db7dd7 00e8:trace:secur32:AcceptSecurityContext 0x21e168 (nil) 0x21dff18 2048 0 0x21dffe0 0x21dff38 0x21de8e8 0x21e160 00e8:trace:ntlm:ntlm_AcceptSecurityContext 0x1d36130 (nil) 0x21dff18 2048 0 0x21de10 0x21dff38 0x21de8e8 0x21e160 ... 00e8:trace:ntlm:ntlm_AcceptSecurityContext Using SECURITY_NETWORK_DREP 00e8:trace:ntlm:fork_helper "ntlm_auth" "ntlm_auth" "--helper-protocol=squid-2.5-ntlmssp" ... 00e8:trace:ntlm:ntlm_AcceptSecurityContext Server set want_flags: "SF NTLMSSP_FEATURE_SESSION_KEY" 00e8:trace:ntlm:run_helper In helper: sending "SF NTLMSSP_FEATURE_SESSION_KEY" 00e8:trace:ntlm:read_line Creating a new buffer for the helper ... 00e8:trace:ntlm:read_line offset = 0, size = 200 00e8:trace:ntlm:read_line read_size = 3, read: "OK\n\x01" 00e8:trace:ntlm:read_line offset_len is calculated from 0x1d2f683 - 0x1d2f683 00e8:trace:ntlm:run_helper In helper: received "OK" 00e8:trace:ntlm:preserve_unused offset_len = 0 00e8:trace:ntlm:preserve_unused helper->com_buf_offset was set to: 0 00e8:trace:ntlm:encodeBase64 bytes is 54, pad bytes is 2 00e8:trace:ntlm:ntlm_AcceptSecurityContext Client sent: "YR xxx==" 00e8:trace:ntlm:run_helper In helper: sending "YR xxx==" 00e8:trace:ntlm:read_line offset = 0, size = 200 00e8:trace:ntlm:read_line read_size = 200, read: "TT xxx" 00e8:trace:ntlm:read_line offset = 200, size = 200 ... 00e8:trace:ntlm:read_line Resizing buffer! 00e8:trace:ntlm:read_line read_size = 16, read: "xxx=\n\x18" 00e8:trace:ntlm:read_line offset_len is calculated from 0x1d00678 - 0x1d00678 00e8:trace:ntlm:run_helper In helper: received "TT xxx=" 00e8:trace:ntlm:preserve_unused offset_len = 0 00e8:trace:ntlm:preserve_unused helper->com_buf_offset was set to: 0 00e8:trace:ntlm:ntlm_AcceptSecurityContext Reply from ntlm_auth: "TT xxx=" 00e8:trace:ntlm:decodeBase64 in_len: 212 ... 00e8:Ret secur32.AcceptSecurityContext() retval=00090312 ret=64474db7dd7 ... --- snip --- Second call of 'InitializeSecurityContextW' (ntlm auth): --- snip --- ... 00e8:Call secur32.InitializeSecurityContextW(0021e128,0021e1e0,021dd75c L"http/localhost",00020800,00000000,00000000,021e0948,00000000,021df460,021e0968,021dd8d0,0021e120) ret=64474db2c56 ... 00e8:trace:secur32:InitializeSecurityContextW 0x21e128 0x21e1e0 L"http/localhost" 0x00020800 0 0 0x21e0948 0 0x21df460 0x21e0968 0x21dd8d0 0x21e120 .... 00e8:trace:ntlm:ntlm_InitializeSecurityContextW 0x1d51b20 0x1d36ad0 L"http/localhost" 0x00020800 0 0 0x21e0948 0 0x21dd80 0x21e0968 0x21dd8d0 0x21e120 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Setting SECURITY_NETWORK_DREP ... 00e8:trace:ntlm:ntlm_GetTokenBufferIndex 0x21e0948 00e8:trace:ntlm:encodeBase64 bytes is 211, pad bytes is 1 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Server sent: "TT xxx=" 00e8:trace:ntlm:run_helper In helper: sending "TT xxx=" 00e8:trace:ntlm:read_line offset = 0, size = 200 00e8:trace:ntlm:read_line read_size = 3, read: "PW\xxx==" 00e8:trace:ntlm:read_line offset_len is calculated from 0x1d4ef63 - 0x1d4ef63 00e8:trace:ntlm:run_helper In helper: received "PW" 00e8:trace:ntlm:preserve_unused offset_len = 0 00e8:trace:ntlm:preserve_unused helper->com_buf_offset was set to: 0 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Helper replied: "PW" 00e8:trace:ntlm:ntlm_InitializeSecurityContextW Helper returned PW ... 00e8:Ret secur32.InitializeSecurityContextW() retval=80090308 ret=64474db2c56 00e8:Call KERNEL32.GetLastError() ret=00f8e42f 00e8:Ret KERNEL32.GetLastError() retval=00000490 ret=00f8e42f 00e8:Call secur32.DeleteSecurityContext(021df460) ret=64474db2920 00e8:trace:secur32:DeleteSecurityContext 0x21df460 00e8:trace:ntlm:ntlm_DeleteSecurityContext 0x1d36ad0 ... 00e8:Ret secur32.DeleteSecurityContext() retval=00000000 ret=64474db2920 00e8:Call KERNEL32.GetLastError() ret=00f8e42f 00e8:Ret KERNEL32.GetLastError() retval=00000490 ret=00f8e42f 00e8:Call KERNEL32.FormatMessageW(00003200,00000000,ffffffff80090308,00000000,0021dff0,00000101,00000000) ret=64474db108f 00e8:Ret KERNEL32.FormatMessageW() retval=00000000 ret=64474db108f 00e8:Call KERNEL32.GetLastError() ret=00f8e42f 00e8:Ret KERNEL32.GetLastError() retval=0000013d ret=00f8e42f 00e8:Call KERNEL32.RaiseException(e0434352,00000001,00000005,0021e1d8) ret=010e3a87 00e8:Call ntdll.memcpy(0021e058,0021e1d8,00000028) ret=7b00f656 00e8:Ret ntdll.memcpy() retval=0021e058 ret=7b00f656 00e8:trace:seh:raise_exception code=e0434352 flags=1 addr=0x7b00f665 ip=7b00f665 tid=00e8 00e8:trace:seh:raise_exception info[0]=ffffffff80004005 00e8:trace:seh:raise_exception info[1]=0000000000000000 00e8:trace:seh:raise_exception info[2]=0000000000000000 00e8:trace:seh:raise_exception info[3]=0000000000000000 00e8:trace:seh:raise_exception info[4]=0000000000f40000 00e8:trace:seh:raise_exception rax=000000000021e058 rbx=000000000021e1d8 rcx=000000000021e038 rdx=0000000000000036 00e8:trace:seh:raise_exception rsi=0000000000000005 rdi=000000000021e100 rbp=000000000021e138 rsp=000000000021e010 00e8:trace:seh:raise_exception r8=0000000000000000 r9=000000000021d810 r10=0000000000000000 r11=0000000000000000 00e8:trace:seh:raise_exception r12=0000000000004000 r13=000000000021e4fc r14=00000000e0434352 r15=0000000000000004 ... 00e8:Call KERNEL32.WideCharToMultiByte(000001b5,00000000,01dcd3c0 L"System.ComponentModel.Win32Exception: Unknown error (0x80090308)\r\n at WSMParis.Server.Program.Main(String[] args)",00000073,00218b28,00000073,00000000,00000000) ret=012b5854 00e8:Ret KERNEL32.WideCharToMultiByte() retval=00000073 ret=012b5854 --- snip --- Wine source: https://source.winehq.org/git/wine.git/blob/d1f858e03da732c621504f90e349d51… Second call handling: https://source.winehq.org/git/wine.git/blob/d1f858e03da732c621504f90e349d51… $ sha1sum Sennheiser_WSM_Setup_4.4.6.6.exe be82329265ce8fca79334612007ea9b1f894bf8f Sennheiser_WSM_Setup_4.4.6.6.exe $ du -sh Sennheiser_WSM_Setup_4.4.6.6.exe 122M Sennheiser_WSM_Setup_4.4.6.6.exe $ wine --version wine-5.7-177-gad1fad8a94 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 3

[Bug 58046] New: Horizon Chase Turbo: gamepad hotplugging doesn't work
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=58046 Bug ID: 58046 Summary: Horizon Chase Turbo: gamepad hotplugging doesn't work Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)gmail.com Distribution: --- Created attachment 78302 --> https://bugs.winehq.org/attachment.cgi?id=78302 `WINEDEBUG=+dinput`, launch game with one gamepad, disonnected, reconnected. In Horizon Chase Turbo (tested Epic Games Store version), gamepads are only usable if they have always been connected since the game has been launched. Otherwise, their inputs are completely ignored, and these gamepads will not be listed in the player mapping screen (Multiplayer). This is not the case on Windows. The only exception is in the title screen: "Press Any Button" does work with hotplugged gamepads. Logs are taken on a fresh prefix with `WINEDEBUG=+dinput`. Without this, the only dinput-related log is: ``` 0208:fixme:dinput:hid_joystick_device_try_open device usage ff72:00a1 not implemented! ``` -- 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 60256] New: Wine application prevents X11 root window from receiving mouse button events
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=60256 Bug ID: 60256 Summary: Wine application prevents X11 root window from receiving mouse button events Product: Wine Version: 11.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: achurch+wine(a)achurch.org Target Milestone: --- Distribution: --- Since wine-11.13, when a Wine application window has the input focus, the X11 root window does not receive mouse button events, preventing the user from (for example) opening a root window menu. This appears to be the same issue as was reported for the Dolphin emulator (https://bugs.dolphin-emu.org/issues/10668) caused by XInput2 enforcing an implicit input grab when an application asks for XI_ButtonPress inputs, and was fixed there by switching to raw button events (https://github.com/dolphin-emu/dolphin/commit/323d09f47e902cbf2b504a7ec11b4…) I can trivially fix this in my case by changing XI_ButtonPress to XI_RawButtonPress in x11drv_xinput2_enable(), but I don't see any change directly relevant to button press handling in 11.12 -> 11.13 diffs, so I presume this is a preexisting issue exposed by changes to use XInput2 in more conditions (the behavior change for my environment occurred in commit a2ceea3e "winex11: Enable XI2 raw events when window is focused."). -- 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 4

[Bug 50572] New: LDAP_AUTH_NEGOTIATE login fails as authorization user is used instead of authentication user
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=50572 Bug ID: 50572 Summary: LDAP_AUTH_NEGOTIATE login fails as authorization user is used instead of authentication user Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wldap32 Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com Distribution: --- In the "ldapsearch" command line tool, "-X" is the authorization user and "-U" is the authentication user. For a server using LDAP_AUTH_NEGOTIATE, it must have the authentication user - supplying only the authorization user always fails: $ ldapsearch -h HOSTNAME -v -X USERNAME -W ldap_initialize( ldap://HOSTNAME ) Enter LDAP Password: SASL/DIGEST-MD5 authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) <===================== additional info: 8009030C: LdapErr: DSID-0C09055F, comment: AcceptSecurityContext error, data 52e, v23f0 Changing the "-X" to "-U", it successfully logs in. If both "-X" and "-U" are present, it also successfully logs in. In dlls/wldap32/bind.c, in the callback function sasl_interact(), Wine supplies its username to SASL_CB_USER which is like "-X", so login always fails the same way. If I change it to supply the username to SASL_CB_AUTHNAME (like "-U"), login succeeds. -- 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 35056] New: Pro⁄Engineer Wildfire 5.0: Fails to start installation
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=35056 Bug #: 35056 Summary: Pro⁄Engineer Wildfire 5.0: Fails to start installation Product: Wine Version: 1.7.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Classification: Unclassified Created attachment 46746 --> http://bugs.winehq.org/attachment.cgi?id=46746 WINEDEBUG=+relay,+seh,+tid on wine-1.7.7-107-g61358d0 Steps to reproduce: 1) remove ~/.wine 2) wine setup.exe Behaviour: Nothing. Expected behaviour: Something. -- 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 14

[Bug 30155] New: secdrv.sys from SafeDisc v2.05.030 does not work
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=30155 Bug #: 30155 Summary: secdrv.sys from SafeDisc v2.05.030 does not work Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: stefan(a)codeweavers.com Classification: Unclassified Created attachment 39336 --> http://bugs.winehq.org/attachment.cgi?id=39336 service,relay,winedevice,ntoskrnl log SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is that the application exits with exit code 0 without any output. This affects for example the Command and Conquer Red Alert 2 installer, which is safedisc protected for some reason. The problem seems to be related to the specific secdrv.sys version. If I take a secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's revenge expansion) and put it in C:\windows\system32\drivers, the installer works. ProtectId says: Scanning -> D:\Setup\Setup.exe File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh) Byte(s) -> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h [File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027) [!] Safedisc v2.05.030 detected ! [i] Appended data contents.... [.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947 byte(s) -> ~de7bc4.tmp [.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208 byte(s) -> clcd32.dll [.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784 byte(s) -> clcd16.dll [.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584 byte(s) -> mcp.dll [.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220 byte(s) -> ~df394b.tmp [.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304 byte(s) -> drvmgt.dll [.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768 byte(s) -> secdrv.sys [.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248 byte(s) -> ~ef7194.tmp [CompilerDetect] -> Visual C++ 6.0 - Scan Took : 0.640 Second(s) The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010 driver is f376a1580204e47f37a721e1cbc5582a. I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of the setup tool. -- 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