[Bug 57980] New: Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx
https://bugs.winehq.org/show_bug.cgi?id=57980 Bug ID: 57980 Summary: Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Every so often I test installing Adobe CC on Wine to see if it will work. With the recent fixes relating to libcef/edge/chromium sandboxing, I gave it another go. Seems like this is now an issue: ``` wine: Call from 00006FFFFFC75D38 to unimplemented function KERNEL32.dll.SetThreadpoolTimerEx, aborting ``` -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57980 Qwerty Chouskie <asdfghrbljzmkd(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu CC| |asdfghrbljzmkd(a)outlook.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57980 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, could you add info how to reproduce this? I downloaded the installer from Adobe site, and installed webview2, but I wasn't able to reproduce this crash (though it didn't start either). Where did you download the installer? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 herobrinecat <noaaweatherradiostatus(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noaaweatherradiostatus(a)gmai | |l.com --- Comment #2 from herobrinecat <noaaweatherradiostatus(a)gmail.com> --- I just manually installed ACC by copying the Creative Cloud to it's location (specifically with ACCC, ACC64, and Utils in the ACC Folder with ACCC and Utils in the Program Files (x86)\Adobe\Adobe Creative Cloud, while ACC64 in Program Files\Adobe\Adobe Creative Cloud.) and letting Creative Cloud running Repair, which gets the rest of the files. I can confirm this error because after signing in, the ACC keeps on crashing with this possible reason: Call from 00006FFFFFC66C18 to unimplemented function KERNEL32.dll.SetThreadpoolTimerEx, aborting -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #3 from herobrinecat <noaaweatherradiostatus(a)gmail.com> --- (I meant as a alternative download, which is a zip file, just adding context) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 redbeana44945(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |redbeana44945(a)gmail.com --- Comment #4 from redbeana44945(a)gmail.com --- Created attachment 79812 --> http://bugs.winehq.org/attachment.cgi?id=79812 backtrace-photoshop2026-kernel32-setthreadpooltimerex -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #5 from redbeana44945(a)gmail.com --- Any updates for this bug? I encountered this issue while trying to run Photoshop 2026 using Wine: ``` $ wine Photoshop.exe wine: Call from 00006FFFFFC5D92A to unimplemented function KERNEL32.dll.SetThreadpoolTimerEx, aborting ``` The complete backtrace has been uploaded as an attachment. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 zefkerr <zefkerrigan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zefkerrigan@gmail.com -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 Leonardo (MrPowerGamerBR) <winehq@mrpowergamerbr.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@mrpowergamerbr.com --- Comment #6 from Leonardo (MrPowerGamerBR) <winehq@mrpowergamerbr.com> --- I've decided to document my findings here, some of the findings are based on Qwerty Chouskie's findings Some of the findings are unrelated to Creative Cloud itself and related to Photoshop and should be moved to other bug reports later. 1. Build Wine with this patch. Keep in mind that the patch SHOULD NOT be used in production because it was generated by an LLM, so avoid it at all costs and it should only be used as an experiment: https://gist.github.com/MrPowerGamerBR/0df28e30b21477363764f8fb84ec489c 2. Enable Wine Virtual Desktop, this is useful because the cursor (at least on KDE Plasma) does not render on top of WebView2 surfaces. Keep in mind that your cursor seems to be offset in the Y axis downwards when interacting with WebView2 surfaces. 3. Install the WebView2 Evergreen Installer from https://developer.microsoft.com/pt-br/microsoft-edge/webview2/?form=MA13LH 4. Create an application override for "msedgewebview2.exe", set it to Windows 7 5. Run "Creative_Cloud_Set-Up.exe", login into your Adobe account and install it 6. During the middle of the installation, the Virtual Desktop for some reason will close, at this point just wait a bit until you feel like the Wine logs have calmed down and restart Explorer 7. Open "Creative Cloud.exe", it will close by itself after a while, then open "Creative Cloud.exe" again and now it will work If your objective was to only get Creative Cloud working, then you are done! But chances are you want to use Photoshop in Wine... 8. Install Photoshop 22.2 (CC 2021) via Creative Cloud, which is the earliest version that you can install via Creative Cloud. Newer Photoshop versions (like CC 2026) crash when starting (I haven't checked which error Wine reports when starting newer CC 2026 versions) 9. After finishing the installation, start Photoshop Photoshop CC 2021 will start, but it "freezes" and displays a off-white popup with nothing in it (the color is the same color as the one used on Adobe's website). While I haven't activated Photoshop on Windows in quite some time, I'm pretty sure that this is the activation popup, where it asks you to login into your Adobe account and activate it/deactivate another machine. The only relevant error logs that I have are 01a8:fixme:mshtml:DocObjOleInPlaceActiveObject_TranslateAccelerator Unsupported message 000f (I'm using this Wine Staging patch, when not using it, it just logs the fixme message: https://gitlab.winehq.org/wine/wine-staging/-/blob/master/patches/mshtml-Tra...) While Photoshop logs messages related to this bug https://bugs.winehq.org/show_bug.cgi?id=37906 when starting up, I think the issue is actually this one, where the page expects newer mshtml features that are not provided in Wine https://bugs.winehq.org/show_bug.cgi?id=50457 Installing "winetricks ie8" causes Photoshop CC 2021 to crash when starting. Newer Internet Explorer (10+) aren't able to be installed in Wine. The reason why there are people that were able to get Photoshop CC 2021 running on Wine is because they are using pirated copies which skip the activation screen. There's also this fork going around claiming that it fixes the Photoshop installer. I did try it to see if it would fix the activation screen, but it didn't fix anything. It may be that the patches need to be updated to Wine 11.0 though (the fork is based on Valve's Wine 10.0 fork), I did try the pre-compiled build that the creator shared on the GitHub page, but I couldn't get Photoshop to start due to it complaining about missing graphic-related DLLs, which I guess is because you are supposed to run it via Proton itself instead of running it via Wine. Someone that may be more knowledgeable about Proton may be able to get it running however. https://github.com/PhialsBasement/wine-photoshop-installers/commits/bleeding... -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 Tomáš Bžatek <bugs@bzatek.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs@bzatek.net -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #7 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Overriding certain EXEs to Windows 7 was previously enough to the the Adobe Creative Cloud app running, however I just deleted and re-created the prefix (was trying to reset to a fresh prefix state after trying various winetricks native DLLs to attempt to fix https://bugs.winehq.org/show_bug.cgi?id=59311), and now it calls KERNEL32.dll.SetThreadpoolTimerEx even with the same EXE overrides. It appears something changed in the Creative Cloud app in just the past few days, which is very unfortunate, as it stops my work (at least for now). Shouldn't have deleted the old prefix, I guess... I did find this change in Chromium from mid-2025 which seems to introduce a hard dependency on SetThreadpoolTimerEx: https://source.chromium.org/chromium/_/chromium/external/github.com/google/n... Perhaps Adobe updated which version of libcef they are using? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #8 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Wait, I got it to run again, though the reason for it working or not working doesn't make much sense. I'll do some more investigation. Having an actual implementation of KERNEL32.dll.SetThreadpoolTimerEx would make things much smoother/less janky/better though. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #9 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- `winetricks msxml3` results in a somewhat borked installation of msxml3, as the 64-bit version of msxml3r.dll is not installed. This actually breaks Adobe Character Animator 2026. However, msxml3 seems to *need to be somewhat borked* for the Creative Cloud app to work, as otherwise it constantly tries to call KERNEL32.dll.SetThreadpoolTimerEx and crashes. AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA Hey, at least I can still somewhat work on stuff, though having to choose between working msxml3 (needed for at least one of the apps) and borked msxml3 (needed for Creative Cloud itself) is quite the messy situation. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #10 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Inspired by https://github.com/i486/VxKex/blob/baca713935809769a6f6d0054a78aae63067456a/... I made a simple version of SetThreadpoolTimerEx: ```c /*********************************************************************** * TpSetTimerEx (NTDLL.@) */ BOOL WINAPI TpSetTimerEx( TP_TIMER *timer, LARGE_INTEGER *timeout, LONG period, LONG window_length ) { BOOL ThreadpoolTimerSet = TpIsTimerSet( timer ); TpSetTimer( timer, timeout, period, window_length ); return ThreadpoolTimerSet; } ``` After also adding the needed lines in the various .spec and .h files (`kernelbase.spec`, `kernel32.spec`, `ntdll.spec`, `threadpoolapiset.h`, `winternl.h`), it seems to work as-expected when running the Adobe CC app, avoiding the need for juggling msxml between a half-broken native version and a working builtin version, and also avoiding the need for overriding the Windows version of a bunch of executables to Windows 7 that is currently done by the Winetricks installation script for adobe_cc. Is this truly all that's needed for SetThreadpoolTimerEx, or are there other details I'm missing? I'd be happy to create a PR, but want to make sure I'm not missing anything. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #11 from Zeb Figura <z.figura12@gmail.com> --- TpSetTimerEx() shouldn't redirect to TpSetTimer(), rather the reverse. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #12 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Created attachment 80578 --> http://bugs.winehq.org/attachment.cgi?id=80578 SetThreadpoolTimerEx.patch Is this closer to what you are looking for? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #13 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Hmm, it looks like a DWORD can't be null, so that extra check is unnecessary. (Then why do the docs specify `[in] DWORD msWindowLength` for SetThreadpoolTimer and `[in, optional] DWORD msWindowLength` for SetThreadpoolTimerEx? Maybe just docs being inconsistent...) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 Qwerty Chouskie <asdfghrbljzmkd@outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #80578|0 |1 is obsolete| | --- Comment #14 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> --- Created attachment 80579 --> http://bugs.winehq.org/attachment.cgi?id=80579 SetThreadpoolTimerEx.patch (revision 2) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 mirh <mirh@protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 Alistair Leslie-Hughes <leslie_alistair@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch CC| |leslie_alistair@hotmail.com -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57980 --- Comment #15 from Qwerty Chouskie <asdfghrbljzmkd@outlook.com> ---
Is this closer to what you are looking for?
Never got feedback on the approach, but looks like it's in staging now (https://gitlab.winehq.org/wine/wine-staging/-/commit/f90501e0828a5ef56471675...) Does this mean the approach is correct? @leslie_alistair If you think the patch is correct, feel free to take ownership/upstream it; I don't care about credit/etc and really just care about the bug being fixed. I'm not really familiar with the various intricacies of the upstream submission process, so perhaps that would be the easier path? -- 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.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla