So what directories should this “libssl-1_1-x64.dll” file be in?
My Windows runs on default settings, without any strange programs.
Seriously - lets not derail this with irrelevant advice found via Google. Duplicate File Finders will NOT help here. In fact they will do the opposite. If you want to talk about duplicate file finders and the like lets make a new thread and keep this one focused on the OP’s question when they come back.
2 Likes
This worked.
Now all libcrypto and libssl files in Windows and system 32 has been “hidden”.
6 Likes
Excellent. Glad to see you got it fixed.
Now at some point in the next weeks some other app you installed will have SSL hiccups… and no doubt that will turn out to be the one who did this. Drop these “hidden” dlls into that app’s folder and it will likely start working. But beware of updating that rouge app as the installer that comes with it may repeat this same wrecking trick.
2 Likes
Had the same issue with the latest version of MusicBrainz Picard popping up two error messages.
No surprise, but renaming the two DLLs also fixed it for me. Initially I just rolled back to Picard 2.12 which works without renaming the DLLs. Hoping this will help the next people who end up here.
The DLLs in question both had “date modified” listed as 08/13/2024. Out of curiosity, I checked if I installed on software on that date, and I didn’t see anything. I did have two Windows Updates installed on that date, “2024-08 .NET 8.0.8 Security Update for x64 Client (KB5042132)” and “2024-08 .NET 6.0.33 Update for x64 Client (KB5042131)”. I don’t know if that’s related, but thought I should mention.
2 Likes
@Lasborg @ZocaloUK As you have both been reporting the issue, which version have you been running before you upgraded?
I’m trying to understand what changed in the packaging that triggers the issue. Because issues like this were supposed to be solved.
3 Likes
@Lasborg @TartPostBox @ZocaloUK I ivestigated this further, as the issue was supposed to be fixed long time ago. But turns out a recent change to the packaging (we had to change the way the code signing works) accidentally disabled the code that was supposed to fix the packaging.
The following is the recommended solution:
Copy all DLL files inside the PyQt5\Qt5\bin\ folder into the root folder of the Picard installation (where the picard.exe is located, so usually C:\Program Files\MusicBrainz Picard.
That way you also do not need to rename any files in system locations.
We will do a release fixing this soon. See also https://tickets.metabrainz.org/browse/PICARD-3034
7 Likes
Yes this worked! Thank you
2 Likes
The release with the proper fix for this is available now: Picard 2.13.3 released – MetaBrainz Blog
6 Likes
2.13.3 worked perfectly here.
Thank you for looking into this and for all the hard work developing this software.
3 Likes