[Bug]: System Error - libcrypto-1_1-x64.dll not found after update to 3.9.1 (Windows 11)

[phil-lipp]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

After updating to 3.9.1 my previously fully functional installation now throws an error on startup.

Steps to reproduce

1. update to 3.9.1
2. (try to) start the programm

Expected behavior

No error or provide the required dll.

Which files are affected by this bug

libcrypto-1_1-x64.dll

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Other

Nextcloud Server version

27.0.1

Nextcloud Desktop Client version

3.9.1

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

[mgallien]

this is already fixed and updated packages have been pushed
sorry for the trouble
please reinstall it or use the same installer in repair mode

[samanoskay]

Still getting this error from a fresh install using winget, soon as I install it requires upgrade to 3.9.1 and once upgraded says the dll file is not present and fails to run.

[bohni]

Using the msi package from nextcloud downlad page, the client starts after a reboot without error.

Using winget, after reboot an update is installed leading to the error, as mentioned from @samanoskay

[Olray]

Just experienced the same problem (updated at 17:59 CEST Europe/Berlin) so the auto updater is probably pulling the wrong package

[ghost]

Just experienced the same problem (updated at 17:59 CEST Europe/Berlin) so the auto updater is probably pulling the wrong package

As @bohni already said. You have to take the MSI. Winget is there like pypi, ziehmlich slow. Since aktuallisierung takes quite a long time, although the new packages are online :)

With the MSI there is in any case no more problem :)

[Olray]

And as I said, I never used Winget but installed from the original MSI package months ago. It's the automatic update process that trashed my install. Repair worked. But tens of thousands of long-term users might experience the same problem in the next few days.

[prissi]

On Japanese windows dowloading a fresh msi did not work. Never used winget. Fresh install still has the missing libcrypto 64 dll.

[prissi]

This is not really fixed, on Japanese Windows the manual install with MSI still gets this message. Repair did not worked. Uninstalling, reboot, reinstall have nextclound complain about the update failing and "please update to nextcloud 3.9.1". Selecting manual update and doing nothing gives a working installation with companing about a failing update at every start.

[Irdiism]

Just got a report from a client with the same problem. Tried also rolling back to 3.9.0 with the same issue poping up.

[ghost]

Just got a report from a client with the same problem. Tried also rolling back to 3.9.0 with the same issue poping up.

The easiest solution is to simply uninstall Nextcloud and then reinstall it via the installer. Works without problems. Please download the installer from the website. The issue or problem was closed a long time ago :)

[albgus]

This bug is not fixed. It still appears when doing the automatic updates.

Just because there's a workaround to manually download a installer from your website doesn't solve the issue for all installed clients that may run the regular manual update process suggested by the client.

[iwikus]

Bug is not fixed. Nextcloud did automatic update and now is unable to start!

It seems latest version is now 3.9.3, which is working. It is very sad, that automatic update did not update to latest or working version.