Windows desktop version crash when sync

Desktop version of nextcloud client (3.14.1.55839) crash whenever the sync starts. Checked the event log, it shows the crash was due to module ucrtbase.dll (10.0.22621.3593), error code 0xc0000409.

1 Like

If you already checked the logs and have detailed information, you can directly contact the developers. I just found this crash report [Bug]: Nextcloud Client 3.14.0 Crashes with Virtual File support / vfs enabled · Issue #7194 · nextcloud/desktop · GitHub but it is on Linux, so yours seems to be different.

I just did some preliminary check from the event viewer, didn’t know what exactly caused the problem. But I suspect it was due to imcompatibility of the windows update (KB2267602, v 1.419.149.0 or 1.419.176.0).

If you still have pending updates, or some were partially installed, it can help sometimes to restart the computer (in case you haven’t tried this old trick). I already have seen strange behavior.

Already tried all tricks including restart, reinstall etc. I believe that is some issue that happens persistently rather than occasionally.

I have the same problem with several clients.

Windows 11 23H2 and the latest Nextcloud client

Is there already a solution for this?

The following entry appears in the event log:
Name der fehlerhaften Anwendung: nextcloud.exe, Version: 3.14.1.55839, Zeitstempel: 0x66f6776f

Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.3636, Zeitstempel: 0x81cf5d89

Ausnahmecode: 0xc0000409

Fehleroffset: 0x000000000007286e

ID des fehlerhaften Prozesses: 0x6240

Startzeit der fehlerhaften Anwendung: 0x01db13e6640a5c1f

Pfad der fehlerhaften Anwendung: C:\Program Files\Nextcloud\nextcloud.exe

If several people can reproduce, this should be reported to the but tracker:

I have created a bug report:

i get same problem in my desktop
system: windows 11 23H2 and system event show error below:
error application name: nextcloud.exe,version: 3.14.1.55839,timestamp: 0x66f6776f
error model name : ucrtbase.dll,version: 10.0.22621.3593,timestamp: 0x10c46e71
error code: 0xc0000409
error : 0x000000000007f6fe

Hello,
Same problem here.

They are already trying a fix:

Please follow up with feedback on the github topic directly.