[Bug]: Windows Explorer Crash (MSVCP140.dll)

[SpecialT131]

⚠️ 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 the last update i cant use the windows explorer becouse it crashes directly after trying to use it.
The windows log says, there is a defect MSVCP140.dll.

The crash only appears on the "Homescreen" of the windows explorer. If i use any other folder on my desktop to access windows explorer it works. But there it also crashes after i click on "quick access"

Steps to reproduce

Open Windows Explorer through Taskbar

Expected behavior

Should open Windows Explorer

Which files are affected by this bug

no files

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Appimage

Nextcloud Server version

xx.xx.xx

Nextcloud Desktop Client version

3.13.0

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 Enabled

Are you using an external user-backend?

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

Nextcloud Server logs

No response

Additional info

After Uninstalling, the Windows Explorer worked as it should be.

[frknakk]

Exactly same problem here, identical error logs, also windows 10. But i can't use my computer at all because explorer/desktop keeps crashing and restarting - so the display is constantly flickering. Restarting the computer does not solve the problem, after logging in the error happens again instantly.

Started yesterday (07.05) for the first time without any actions, i was away from my computer and after coming back i saw the flickering. After repairing windows the error disappeared for the rest of the day. Today i got the same error again, now uninstalled nextcloud desktop client and no errors anymore.

[xaras2]

https://central.owncloud.org/t/owncloud-client-5-2-1-13040-owncloud-client-explorer-exe-crash-loop/48472

As me

[FauxKalEl]

Only way to start explorer without crash is ctrl+shift+esc or ctrl+alt+del and task manager, run new task, browse and then find and rename owncloud dir (default c:\Program Files\OwnCloud.
Then Explorer immediately stop crashing. Then you can restore owncloud dir name and start owncloud manually but after next login to windows needs to rename again. Looks like shell integration problem.

Edit:
Reinstalling VC++ not helped, but replacing:
msvcp140.dll
msvcp140_1.dll
msvcp140_2.dll
msvcp140_atomic_wait.dll
msvcp140_codecvt_ids.dll

in ownCloud dir with newer libs (from 14.34.31938.0 to 14.38.33135.0) is resolving this problem.

[lordimac]

Same problem, same Logs. Windows 11, Version 23H2, Build 22631.3527

[Leah96xxx]

Confirmed I also have this issue, usually with error 0xc0000005 (access violation) like OP's post, but caused by NCContextMenu.dll instead, but sometimes with 0xc000041d (fatal user callback exception) caused by NCContextMenu.dll, and sometimes with 0xc0000409 (buffer overrun) caused by ntdll.dll.

Windows 10 22H2 19045.4412, Nextcloud 3.13.0

[Leah96xxx]

Doing a repair install of the Nextcloud client appears to have fixed it for me, but the question is whether or not it will stay fixed. I'll update in a few hours/days if the issue returns

[leboem]

I have the same issue. After some debugging and research, I figured out that:

• Nextcloud places the msvcp140 DLLs next to the Nextcloud exe.
• These redistributables are backward compatible. An app linked against an older version will still work with a newer version of the DLLs, but not the other way around (https://learn.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=msvc-170)
• Nextcloud isn't built with the newest version, but another App on my system is built with the latest version 14.40.33810.0.
• On Windows startup, Nextcloud is started first and explorer.exe loads the old DLLs placed next to Nextcloud.exe. After that, the other App starts and crashes since msvcp.dll is already loaded but that version is incompatible.

I think Nextcloud, either needs to upgrade to the newest C++ redistributables or better, change to the recommended "Central deployment by using Visual C++ Redistributable packages."

• https://learn.microsoft.com/en-us/cpp/windows/choosing-a-deployment-method?view=msvc-170
• https://learn.microsoft.com/en-us/cpp/windows/deploying-visual-cpp-application-by-using-the-vcpp-redistributable-package?view=msvc-170

[jasonmacer]

Is there no fix for this yet? My system just applied this update and now explorer is stuck in a crash/start loop.

[FauxKalEl]

Owncloud resolved bug few weeks ago, nextcloud should already merged this fix. This appears in certain circumstances, more frequently in new Windows versions with older vc++ libraries included in cloud installer. Bug is very old and now appeared more frequently. Devs why then not fixed in nextcloud? pt., 2 sie 2024, 20:18 użytkownik Jason Macer ***@***.***> napisał:

…

Is there no fix for this yet? My system just applied this update and now explorer is stuck in a crash/start loop. — Reply to this email directly, view it on GitHub <#6740 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BILVEJPHDECOI4AYLZVXGMDZPPEQHAVCNFSM6AAAAABHNBQWZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVHEYTCOJZGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jasonmacer]

@FauxKalEl I ended up having to completely remove oc, restart, re-install, restart and then it started working again; however, the computer was having issues so I then had to shutdown pull the power drain the board then plug back in and start up before it decided to work correctly again.

[camilasan]

in ownCloud dir with newer libs (from 14.34.31938.0 to 14.38.33135.0) is resolving this problem.

with 3.14.1, we are using 14.38.33135.0. Could you all try the latest 3.14.1 and check if the issue is resolved for you?