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

[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

[Bug 60229] New: Netscape Navigator 3.04 for Windows 3.1 crashes on start on a null pointer
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=60229 Bug ID: 60229 Summary: Netscape Navigator 3.04 for Windows 3.1 crashes on start on a null pointer Product: Wine Version: 11.16 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole16 Assignee: wine-bugs(a)list.winehq.org Reporter: alexhenrie24(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81928 --> http://bugs.winehq.org/attachment.cgi?id=81928 Crash backtrace Steps to reproduce: 1. Copy n16d304.exe to an otherwise empty directory 2. Run `unzip n16d304.exe` (yes, I know it's an installer, but unzipping it is easier than running it in DOSBox) 3. Use an "old WoW64" Wine build because the setup program won't start on new WoW64 4. Run `wine SETUP.EXE` to install Netscape 5. Run `wine 'C:\Netscape\Comm\Program\NETSCAPE.EXE'` to start Netscape Netscape 3.04 used to work on Wine 5.0. `git bisect` says: ba3ca9970342a382f62dd1a792675f0f7e6c4531 is the first 'bad' commit commit ba3ca9970342a382f62dd1a792675f0f7e6c4531 Author: Elizabeth Figura <z.figura12(a)gmail.com> AuthorDate: Wed Jan 15 00:24:30 2020 -0600 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Tue Jan 21 20:54:32 2020 +0100 compobj: Always set the IMalloc pointer in CoInitialize(). Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/compobj.dll16/compobj.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) The root of the problem is that Netscape needs 16-bit CoGetMalloc to return a valid function without calling 16-bit CoInitialize first, just like how 32-bit CoGetMalloc works. $ sha256sum n16d304.exe 1ab3cd6e25cac74e2bdaf76228b6b3706e30965cf544172d1fd3571ae9fd4c04 -- 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 60219] New: Ankh - Anniversary Edition: Some textures are rendered black
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=60219 Bug ID: 60219 Summary: Ankh - Anniversary Edition: Some textures are rendered black Product: Wine Version: 11.16 Hardware: x86-64 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: z.figura12(a)gmail.com Target Milestone: --- Regression SHA1: b10b7e61b58c5536a01e5438607f8fa12a1f7932 Distribution: --- Created attachment 81920 --> http://bugs.winehq.org/attachment.cgi?id=81920 black textures Some textures are rendered completely black instead of displaying their normal texture. The issue is visible in several locations in the game. Lowering Shadows and Texture Quality to their minimum settings reduces the number of affected surfaces somewhat, but does not eliminate the problem. I reproduced the issue with the GOG.com version of Ankh - Anniversary Edition. The game is also available on Steam, but I do not own that version. Unfortunately, I could not find a demo version of the game. I bisected the regression to commit: b10b7e61b58c5536a01e5438607f8fa12a1f7932 Reverting the commit on top of Wine-11.16 fixes the problem for me. NVIDIA GeForce GTX 1660 SUPER NVIDIA driver 610.57.04 OpenGL 4.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 6

[Bug 50323] New: Multiple applications need 'winsock.getservbyname' to read information from '%SystemRoot%\System32\Drivers\Etc\services' (Autodesk 3ds Max 9 RaySat service)
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=50323 Bug ID: 50323 Summary: Multiple applications need 'winsock.getservbyname' to read information from '%SystemRoot%\System32\Drivers\Etc\services' (Autodesk 3ds Max 9 RaySat service) Product: Wine Version: 6.0-rc2 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, follow-up to bug 12076 Autodesk 3ds Max 9 installation will fail when 'SAT service' option is selected. The service is also mentioned in bug 32317. --- snip --- $ WINEDEBUG=+seh,+loaddll,+relay,+services,+msi wine msiexec -i 3dsmax9_win32.msi >>log.txt 2>&1 ... 0024:trace:msi:ACTION_PerformAction Performing action (L"StartServices") ... 0124:Call KERNEL32.CreateProcessW(00000000,00126b70 L"C:\\Program Files\\Autodesk\\3ds Max 9\\mentalray\\satellite\\raysat_3dsmax9_32server.exe",00000000,00000000,00000000,00000400,0012f5f0,00000000,0121f9d8,0121fbec) ret=00406247 ... 0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ntdll.dll" at 7BC00000: builtin 0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernelbase.dll" at 7B000000: builtin 0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernel32.dll" at 7B600000: builtin 0144:trace:loaddll:build_module Loaded L"C:\\Program Files\\Autodesk\\3ds Max 9\\mentalray\\satellite\\raysat_3dsmax9_32server.exe" at 00400000: native ... 0124:Ret KERNEL32.CreateProcessW() retval=00000001 ret=00406247 ... 01c4:Call advapi32.SetServiceStatus(00127df8,0040f380) ret=004028c3 ... 01c4:Ret advapi32.SetServiceStatus() retval=00000001 ret=004028c3 01c4:Call ws2_32.getservbyname(00cbf9e0 "mi-raysat_3dsmax9_32",0040bad4 "tcp") ret=004028fa ... 01c4:Ret ws2_32.getservbyname() retval=00000000 ret=004028fa 01c4:Call KERNEL32.GetLastError() ret=0040130c 01c4:Ret KERNEL32.GetLastError() retval=00002afc ret=0040130c 01c4:Call KERNEL32.GetLastError() ret=004011dd 01c4:Ret KERNEL32.GetLastError() retval=00002afc ret=004011dd 01c4:Call KERNEL32.FormatMessageA(00003100,00000000,00002afc,00000000,00cbf344,00000000,00000000) ret=004011eb 01c4:Call ntdll.RtlFindMessage(7b600000,0000000b,00000000,00002afc,00cbf290) ret=7b023ef5 01c4:Ret ntdll.RtlFindMessage() retval=c0000109 ret=7b023ef5 01c4:Call ntdll.RtlNtStatusToDosError(c0000109) ret=7b023f00 01c4:Ret ntdll.RtlNtStatusToDosError() retval=0000013d ret=7b023f00 01c4:Ret KERNEL32.FormatMessageA() retval=00000000 ret=004011eb 01c4:Call advapi32.RegisterEventSourceA(00000000,0040f260 "RaySat_3dsmax9_32 Server") ret=0040111e 01c4:fixme:advapi:RegisterEventSourceA ((null),"RaySat_3dsmax9_32 Server"): stub 01c4:fixme:advapi:RegisterEventSourceW (L"",L"RaySat_3dsmax9_32 Server"): stub 01c4:Ret advapi32.RegisterEventSourceA() retval=cafe4242 ret=0040111e 01c4:Call advapi32.ReportEventA(cafe4242,00000001,00000000,c0020002,00000000,00000002,00000000,00cbf364,00000000) ret=0040116b 01c4:fixme:advapi:ReportEventA (CAFE4242,0x0001,0x0000,0xc0020002,00000000,0x0002,0x00000000,00CBF364,00000000): stub 01c4:fixme:advapi:ReportEventW (CAFE4242,0x0001,0x0000,0xc0020002,00000000,0x0002,0x00000000,00128080,00000000): stub 01c4:err:eventlog:ReportEventW L"(1632) getservbyname: 0x2afc (11004)" 01c4:err:eventlog:ReportEventW L"" 01c4:Ret advapi32.ReportEventA() retval=00000001 ret=0040116b 01c4:Call advapi32.DeregisterEventSource(cafe4242) ret=004011ad 01c4:fixme:advapi:DeregisterEventSource (CAFE4242) stub 01c4:Ret advapi32.DeregisterEventSource() retval=00000001 ret=004011ad 01c4:Call advapi32.SetServiceStatus(00127df8,0040f380) ret=00402c28 ... 01c4:Ret advapi32.SetServiceStatus() retval=00000001 ret=00402c28 ... 0144:Call KERNEL32.ExitProcess(00000000) ret=00403a8a ... 0024:warn:msi:ITERATE_StartService service failed to start 1 ... 0024:trace:msi:msi_schedule_action Scheduling action L"StopServices" in script 2 ... 0024:err:msi:execute_script Execution of script 0 halted; action L"StartServices" returned 1627 ... 0024:err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned 1627 ... --- snip --- The following entry is written to '%SystemRoot%\System32\Drivers\Etc\services' file during service installation: --- snip --- ... mi-raysat_3dsmax9_32 7504/tcp #mental ray 3.5 Satellite (32-bit) --- snip --- The service tries to retrieve its own service information (port) using winsock 'getservbyname' function. This obviously fails because Wine calls Linux libc function which is by design unaware of '%SystemRoot%\System32\Drivers\Etc\services'. Wine source: https://source.winehq.org/git/wine.git/blob/3acb0b3326c4120ea0c4c6076bd03c9… --- snip --- 6386 /*********************************************************************** 6387 * getservbyname (WS2_32.55) 6388 */ 6389 struct WS_servent* WINAPI WS_getservbyname(const char *name, const char *proto) 6390 { 6391 struct WS_servent* retval = NULL; 6392 struct servent* serv; 6393 char *name_str; 6394 char *proto_str = NULL; 6395 6396 if (!(name_str = strdup_lower(name))) return NULL; 6397 6398 if (proto && *proto) 6399 { 6400 if (!(proto_str = strdup_lower(proto))) 6401 { 6402 HeapFree( GetProcessHeap(), 0, name_str ); 6403 return NULL; 6404 } 6405 } 6406 6407 EnterCriticalSection( &csWSgetXXXbyYYY ); 6408 serv = getservbyname(name_str, proto_str); 6409 if( serv != NULL ) 6410 { 6411 retval = WS_dup_se(serv); 6412 } 6413 else SetLastError(WSANO_DATA); 6414 LeaveCriticalSection( &csWSgetXXXbyYYY ); 6415 HeapFree( GetProcessHeap(), 0, proto_str ); 6416 HeapFree( GetProcessHeap(), 0, name_str ); 6417 TRACE( "%s, %s ret %p\n", debugstr_a(name), debugstr_a(proto), retval ); 6418 return retval; 6419 } --- snip --- $ sha1sum 3dsmax9.zip d04eeb0eeabbb7cedaf536170fb6879b2faf1a25 3dsmax9.zip $ du -sh 3dsmax9.zip 590M 3dsmax9.zip $ wine --version wine-6.0-rc2 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 6

[Bug 44137] New: Wine64 crashes with any 64-bit binary
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=44137 Bug ID: 44137 Summary: Wine64 crashes with any 64-bit binary Product: Wine Version: 2.19 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bourne.identity(a)hotmail.com Created attachment 59886 --> https://bugs.winehq.org/attachment.cgi?id=59886 Stack trace for putty.exe (64-bit) On FreeBSD 10.3 amd64, wine32 works perfectly. Wine64 builds/installs correctly, but crashes when used to launch any 64-bit executable: notepad from Windows 7; Pale Moon installer; putty.exe (all 64-bit). The behaviour is the same with wine (v2.03) and wine-staging (v2.19). -- 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 5

[Bug 60226] New: Wine XInput: XInputGetState returns 0 buttons for connected Bluetooth Xbox One controller
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=60226 Bug ID: 60226 Summary: Wine XInput: XInputGetState returns 0 buttons for connected Bluetooth Xbox One controller Product: Wine Version: 11.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs(a)list.winehq.org Reporter: lifeartas1(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81926 --> http://bugs.winehq.org/attachment.cgi?id=81926 Complete Wine XInput probe output and stderr (wine-staging 11.13) plus evdev monitor capture of the connected Bluetooth Xbox One controller On a clean Wine prefix (default layout, no DLL overrides, no third-party DLLs), a standalone Windows XInput probe polling XInputGetState(0) reports the controller as CONNECTED (result == ERROR_SUCCESS) but the button/trigger/thumb-stick state is permanently zero — buttons=0x0000, rt=0, lt=0, lx=0, ly=0 — even while the physical buttons and D-pad are pressed. The kernel-level input IS delivered to the controller's evdev node (a monitor captures button/axis events), so the break is in Wine's XInput backend: it enumerates the controller but never maps incoming HID/evdev input into the XINPUT_STATE it returns. Environment: - Nobara Linux 44 (KDE Plasma), x86_64 - Kernel: 7.1.4-200.nobara.fc44.x86_64 - Wine: 11.13 (Staging), package wine-staging-11.13-1.x86_64 - Controller: Microsoft Xbox Wireless Controller (Bluetooth), VID 045e PID 0b13, fw 0522 - Driver: xpadneo (hid-xpadneo) Repro: 1. Connect an Xbox One Wireless Controller over Bluetooth (xpadneo). 2. Create a clean prefix: WINEPREFIX=/tmp/wine-clean wineboot -i 3. Run a minimal XInput probe (loop XInputGetState(0) ~800x over 8s) under it while pressing A / D-pad. 4. Observed: t=0 result=0 packet=1 buttons=0x0000, then done — no button changes ever. Expected: XInputGetState(0) returns the pressed button bits when physical buttons are pressed, matching Windows. Actual: returns result=0 (connected) but buttons=0x0000 permanently, while the same presses produce valid events at the kernel evdev layer. Attached: complete probe output + wine stderr + evdev monitor capture. -- 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 58511] New: Unimplemented sub function KeAcquireGuardedMutex from ntoskrnl.exe
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=58511 Bug ID: 58511 Summary: Unimplemented sub function KeAcquireGuardedMutex from ntoskrnl.exe Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: indigosky30(a)gmail.com Distribution: --- Im trying to figure out why a game that was running a few weeks ago normally doesnt work anymore (gunbound). First, they added Anticheat (SARD), this might be the reason why it fails but trying to debug I found the problem comes from an unimplemented Windows kernel function (note this is an old function introduced in 2003). ------------------------------- 0320:fixme:advapi:DecryptFileW (L"C:\\Program Files (x86)\\GunBoundWC\\game\\sard\\sard_1.0.1.17.sys", 00000000): stub 0320:fixme:ntdll:NtLoadDriver (L"\\Registry\\Machine\\SYSTEM\\CurrentControlSet\\Services\\sard_1.0.1.17"), stub! 0320:fixme:ntdll:NtUnloadDriver (L"\\Registry\\Machine\\SYSTEM\\CurrentControlSet\\Services\\sard_1.0.1.17"), stub! wine: Call from 00006FFFFFC66438 to unimplemented function ntoskrnl.exe.KeAcquireGuardedMutex, aborting wine: Unimplemented function ntoskrnl.exe.KeAcquireGuardedMutex called at address 00006FFFFFC66438 (thread 033c), starting deb ugger... 0350:fixme:dbghelp:elf_search_auxv can't find symbol in module 0350:fixme:dbghelp:elf_search_auxv can't find symbol in module wine: Call from 00006FFFFFC66438 to unimplemented function ntoskrnl.exe.KeAcquireGuardedMutex, aborting 0328:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0! ---------------------- Looking at the call inside the ntoskrn routine, KeAcquireGuardedMutex isnt implemented in WINE (not found here) https://source.winehq.org/WineAPI/ntoskrnl.html, but can be found in the Windows kernel (https://gist.github.com/ntddk/56784b8da89f228f5f1d) Im wondering if implementing the function in WINE would solve the problem? Anyhow hoping someone more knowledgeable sheds some light on this problem. -- 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 50233] New: Signtools from Windows 10 SDK needs 'wintrust.CryptCATAdminAcquireContext2' implementation
by WineHQ Bugzilla Sept. 4, 2026

Sept. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=50233 Bug ID: 50233 Summary: Signtools from Windows 10 SDK needs 'wintrust.CryptCATAdminAcquireContext2' implementation Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. The stub was added in bug 45998 (https://source.winehq.org/git/wine.git/commitdiff/479c30072884c6342bc08faae…) Download(s): * "https://download.microsoft.com/download/1/c/3/1c3d5161-d9e9-4e4b-9b43-b70fe… SDK Signing Tools-x86_en-us.msi" * https://download.microsoft.com/download/1/c/3/1c3d5161-d9e9-4e4b-9b43-b70fe… * https://download.microsoft.com/download/1/c/3/1c3d5161-d9e9-4e4b-9b43-b70fe… * https://download.microsoft.com/download/1/c/3/1c3d5161-d9e9-4e4b-9b43-b70fe… * https://download.microsoft.com/download/1/c/3/1c3d5161-d9e9-4e4b-9b43-b70fe… You can get these direct downloads by running the the Windows 10 SDK web-installer, selecting the wanted packages and inspect the log file. https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/ I've created snapshots on archive.org because like other vendors, MS has a bad habit of silently removing stuff after a while "rewriting history; it didn't happen". Just prepend "https://web.archive.org/web/*/" to the original direct links from MS. One liner for downloading all required payloads: --- snip --- $ for file in {4c3ef4b2b1dc72149f979f4243d2accf,685f3d4691f444bc382762d603a99afc,e5c4b31ff9997ac5603f4f28cd7df602,e98fa5eb5fee6ce17a7a69d585870b7c}.cab "Windows SDK Signing Tools-x86_en-us.msi" ; do wget "https://download.microsoft.com/download/1/c/3/1c3d5161-d9e9-4e4b-9b43-b70fe…" ; done --- snip --- Prerequisite: 'winetricks -q mfc42' (32-bit) --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files (x86)/Windows Kits/10/bin/10.0.19041.0/x86 $ wine ./signtool.exe verify signtool.exe 0024:fixme:wintrust:CryptCATAdminAcquireContext2 0031E060 (null) (null) 00000000 0 stub SignTool Error: CryptCATAdminAcquireContext2 returned error: 0x00000078 Call not implemented. Unexpected error: "CryptCATAdminAcquireContext2 failed". --- snip --- Wine source: https://source.winehq.org/git/wine.git/blob/2ad09b01673381261815bfc804a2f69… --- snip --- 148 /*********************************************************************** 149 * CryptCATAdminAcquireContext2 (WINTRUST.@) 150 */ 151 BOOL WINAPI CryptCATAdminAcquireContext2(HCATADMIN *catAdmin, const GUID *sys, const WCHAR *algorithm, 152 const CERT_STRONG_SIGN_PARA *policy, DWORD flags) 153 { 154 FIXME("%p %s %s %p %x stub\n", catAdmin, debugstr_guid(sys), debugstr_w(algorithm), policy, flags); 155 SetLastError(ERROR_CALL_NOT_IMPLEMENTED); 156 return FALSE; 157 } --- snip --- $ sha1sum *.cab *msi 4614d732dfceb8816c95f147ff9d99dd1fcfd6dc 4c3ef4b2b1dc72149f979f4243d2accf.cab 933328788d00ec5b08fd9bfd2903b50a2caa83d3 685f3d4691f444bc382762d603a99afc.cab 3c452b0200382f8ab7495002b541735c47193c91 e5c4b31ff9997ac5603f4f28cd7df602.cab 8c451f3fdfe54356d1a4bb2ff9374aef200d399b e98fa5eb5fee6ce17a7a69d585870b7c.cab da91ee0facad49b74da579e73ab05a10630234c8 Windows SDK Signing Tools-x86_en-us.msi $ du -sh *.cab *msi 532K 4c3ef4b2b1dc72149f979f4243d2accf.cab 1.1M 685f3d4691f444bc382762d603a99afc.cab 580K e5c4b31ff9997ac5603f4f28cd7df602.cab 1.4M e98fa5eb5fee6ce17a7a69d585870b7c.cab 388K Windows SDK Signing Tools-x86_en-us.msi $ wine --version wine-5.22-260-g2ad09b01673 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