[Bug]: Windows Client Crash when Sync - Errorcode: 0xc0000409

[PaulEDV]

⚠️ 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

The Windows client regularly crashes during the first synchronization and does not start automatically afterwards.

This affects several of our clients but not all, regardless of whether Windows 10 22h2 or Windows 11 23h2.
See forum post:
https://help.nextcloud.com/t/windows-desktop-version-crash-when-sync/205224/3

The following message is in the Windows 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

Here are the log files of the Nextcloud client and the event log:
nextcloud_log.zip

Steps to reproduce

1. install Nextcloud Client
2. connect Nextcloud Client with the Nextcloud
3. set up Nextcloud Sync with virtual files
4. wait until client crashes unnoticed

Expected behavior

The Nextcloud client should display an error message in the event of a crash or restart automatically after a crash during sync

Which files are affected by this bug

last Sync File in the log is: 20220314_Art der Vergabe - Verknüpfung.lnk

Operating system

Windows

Which version of the operating system you are running.

Windows 10 22H2 an Windows 11 23H2

Package

Official Windows MSI

Nextcloud Server version

29.0.5

Nextcloud Desktop Client version

3.14.1

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

Fresh desktop client install

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

No response

[Killea]

same issue.
down to 3.13.3 worked for me. (I also disabled auto upgrade)
could also try Nextcloud-3.13.4-x64.msi
3.14+ will not work.

[eckgit]

The same issue with Nextcloud-Client-version 3.14.1 in virtual folder mode occured for me in Windows 11 Pro, 10.0.22631, Build 22631.
Will give also version 3.13.3 a try.

[y0umu]

I encountered the same problem even without using the virtual folder mode. Versions are 3.14.0-x64, 3.13.4-x64 on windows.

[PaulEDV]

Version 3.13.3 works for me. Synchronization is currently running there without crashes.

[mgallien]

@PaulEDV and others
I have a possible fox for this
already merged in stable branch
you can test this test build from the 3.14 stable branch
https://cloud.nextcloud.com/s/Pfw35DDoDWGnft2

[nkamkar]

Hi mgallien

Thank you for the update. I have installed the build from the link you have provided on 2 problematic machines and both are now behaving well again. I will continue to monitor to ensure they remainwell-behaved, but for now, I would like to specially thank you for providing the fix.

Best wishes

Nima

[toxn]

Just had the same bug with a 256-chars path with the latest stable (3.14.1).

Last log line:

2024-10-10 13:47:37:597 [ warning nextcloud.sync.filesystem C:\Users\User\AppData\Local\Temp\windows-26085\client-building\desktop\src\libsync\filesystem.cpp:204 ]:    Error setting mtime for "C:/Users/redact/Documents/redac/redactedredactedreda/redactedredacted/redactedredactedredactedredactedredactedredactedr/redactedreda/redacte/.redactedredactedredactedredactedredactedredactedredactedredactedredactedredactedredactedredactedredactedreda.pptx.~559c" failed: rc -1 , errno: 20 

[madtownchris]

The updated installer linked by @mgallien appears to solve the issue I encountered (app event pasted below) which I believe is the core issue here:

Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000409
Fault offset: 0x000000000007f6fe
Faulting process id: 0x0x34B4
Faulting application start time: 0x0x1DB1C01AB284F7E
Faulting application path: C:\Program Files (x86)\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 1bf3b91c-69e2-4388-9f13-220df256c405
Faulting package full name:
Faulting package-relative application ID:

[ziyiat]

-
nextcloud.exe
3.14.1.55839
66f6776f
ucrtbase.dll
10.0.19041.3636
81cf5d89
c0000409
000000000007286e
274
01db1cc92afb0abf
D:\Program Files\Nextcloud\nextcloud.exe
C:\WINDOWS\System32\ucrtbase.dll
f4123dcc-4b31-40c4-a28f-044ea406f59b

[radiskis]

@mgallien installer solved the problem, previously Nextcloud 3.14.1 x64 on Windows 11 in folder without virtual files logged such an error (file name redacted with character "1") and quit silently:

2024-10-17 11:05:37:336 [ warning nextcloud.sync.filesystem C:\Users\User\AppData\Local\Temp\windows-26085\client-building\desktop\src\libsync\filesystem.cpp:204 ]: Error setting mtime for "C:/Users/User/Nextcloud/1111111111111/111111111111111111111111/111111111/.1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111.docx.~745f" failed: rc -1 , errno: 20

[airbenich]

Same behaviour on our clients. Thanks @mgallien for the installer. This fixed it for us.

[airbenich]

Will this fix be in Release 3.14.2? I couldn't find #7258 in the changelog.

[dd6464]

I'm still having an issue with Nextcloud version 3.14.1.55839.

Level Date and Time Source Event ID Task Category
Error 21/10/2024 09:56:45 Application Error 1000 Application Crashing Events "Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000409
Fault offset: 0x000000000007f6fe
Faulting process id: 0x0x2168
Faulting application start time: 0x0x1DB2397158F56D9
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 23e533f5-dad3-4b7c-9f11-9b8b6d8a7fa8
Faulting package full name:
Faulting package-relative application ID: "

System Information

Device Spec

Device name EK1
Processor AMD Ryzen 5 PRO 3350G with Radeon Vega Graphics 3.60 GHz
Installed RAM 16.0 GB (13.9 GB usable)
Device ID 20226564-211C-4ACB-B90F-E5DBE411588E
Product ID 00330-53698-70641-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Windows Spec

Edition Windows 11 Pro
Version 23H2
Installed on ‎20/‎08/‎2024
OS build 22631.4317
Experience Windows Feature Experience Pack 1000.22700.1041.0

[steven0081]

I encountered the same problem even without using the virtual folder mode. Versions are 3.14.0-x64, 3.13.4-x64 on windows.

yes ,me too,i try every edtion from 3.14.0-x64, 3.13.4-x64 on windows.

[zhiiwg]

Try versions from v3.13.4 — v3.14.2, crashed after start sync.

1. Uninstall Nextcloud
2. Delete config and cache files in %appdata% (local & roaming /nextcloud)
3. Install Nextcloud v3.13.3 then setup account
4. Upgrade to Nextcloud v3.14.3 from settings (most recent version)

This solves my crash problem, hope this can be helpful :)

Update: sadly, this workaround only works for one time, after a reboot at a day after, nextcloud v3.14.3 start crash at sync too.

QQ2024116-19512.mp4

And sync log for captured video like this:

#=#=#=# Syncrun started 2024-11-06T10:34:09Z
#=#=#=#=# Propagation starts 2024-11-06T10:34:10Z (last step: 791 msec, total: 791 msec)
#=#=#=# Syncrun started 2024-11-06T11:49:35Z
#=#=#=#=# Propagation starts 2024-11-06T11:49:35Z (last step: 788 msec, total: 788 msec)
#=#=#=# Syncrun started 2024-11-06T11:51:06Z
#=#=#=#=# Propagation starts 2024-11-06T11:51:07Z (last step: 849 msec, total: 849 msec)

[hokascha]

@mgallien is this merged now in 3.14.3?

[zhiiwg]

App crash in windows event viewer with nextcloud v3.14.3:

- EventData 
  AppName nextcloud.exe 
  AppVersion 3.14.3.55943 
  AppTimeStamp 67238c6c 
  ModuleName ucrtbase.dll 
  ModuleVersion 10.0.26100.1882 
  ModuleTimeStamp 52db7a2d 
  ExceptionCode c0000409 
  FaultingOffset 00000000000a502e 
  ProcessId 0x2904 
  ProcessCreationTime 0x1db3046f4db82c5 
  AppPath C:\Program Files\Nextcloud\nextcloud.exe 
  ModulePath C:\WINDOWS\System32\ucrtbase.dll 
  IntegratorReportId 791e60e4-7d94-47d8-adc2-b5e9c895b4b5 
  PackageFullName  
  PackageRelativeAppId  

[fuchse-ohren]

If you experience crashes in a non-English environment, please try the following mitigations.
However, this operation may cause garbled characters in some software.

1. Open the Settings application.
2. Click on “Time and Language” > “Language and Region
3. Click on “Administrative language settings” in the relevant settings at the bottom of the screen.
4. A new window will open. Click on “Change system locale”.
5. Check “Beta: Use Unicode UTF-8 for worldwide language support (U)”
6. Click “OK” and restart

Translated with DeepL.com (free version)

--- original language below ---

非英語環境でクラッシュが発生する場合は次の緩和策をお試しください．
ただし，この操作を行うと一部のソフトは文字化けする可能性があります．

1. 設定アプリを開く
2. 「時刻と言語」 > 「言語と地域」 の順にクリック
3. 画面最下部の関連設定に表示される「管理用の言語の設定」をクリック
4. 新しくウィンドウが開くので「システムロケールの変更」をクリック
5. 「ベータ:ワールドワイド言語サポートでUnicode UTF-8を使用(U)」にチェックを入れる
6. 「OK」をクリックして再起動

[zhiiwg]

@fuchse-ohren Thank you! It works for me.

And after nextcloud works fine, uncheck Unicode utf-8 support seems to be OK. (Because this option will cause other language display problems like ftp...)

[jstdoit]

i am still suffering this problem.

[jstdoit]

If you experience crashes in a non-English environment, please try the following mitigations. However, this operation may cause garbled characters in some software.

1. Open the Settings application.
2. Click on “Time and Language” > “Language and Region
3. Click on “Administrative language settings” in the relevant settings at the bottom of the screen.
4. A new window will open. Click on “Change system locale”.
5. Check “Beta: Use Unicode UTF-8 for worldwide language support (U)”
6. Click “OK” and restart

Translated with DeepL.com (free version)

--- original language below ---

非英語環境でクラッシュが発生する場合は次の緩和策をお試しください． ただし，この操作を行うと一部のソフトは文字化けする可能性があります．

1. 設定アプリを開く
2. 「時刻と言語」 > 「言語と地域」 の順にクリック
3. 画面最下部の関連設定に表示される「管理用の言語の設定」をクリック
4. 新しくウィンドウが開くので「システムロケールの変更」をクリック
5. 「ベータ:ワールドワイド言語サポートでUnicode UTF-8を使用(U)」にチェックを入れる
6. 「OK」をクリックして再起動

Great Tip, it works for me. windows 10, nextcloud v3.14.3

[dybai]

错误应用程序名称: nextcloud.exe，版本: 3.14.3.55943，时间戳: 0x67238c6c
错误模块名称: ucrtbase.dll，版本: 10.0.19041.3636，时间戳: 0x81cf5d89
异常代码: 0xc0000409
错误偏移量: 0x000000000007286e
错误进程 ID: 0xe74
错误应用程序启动时间: 0x01db3a534cc9af37
错误应用程序路径: C:\Program Files\Nextcloud\nextcloud.exe
错误模块路径: C:\WINDOWS\System32\ucrtbase.dll
报告 ID: fc31bb4d-2e35-4026-9aa5-04670fbb71b2
错误程序包全名:
错误程序包相对应用程序 ID:

[yatokesa]

Even with version 3.15.0, nextcloud.exe crashed during sync.
I use it on Windows10 Japanese.
I have to go back to version 3.13.4.

障害が発生しているアプリケーション名: nextcloud.exe、バージョン: 3.15.0.56037、タイム スタンプ: 0x6744f4a6
障害が発生しているモジュール名: ucrtbase.dll、バージョン: 10.0.19041.3636、タイム スタンプ: 0x81cf5d89
例外コード: 0xc0000409
障害オフセット: 0x000000000007286e
障害が発生しているプロセス ID: 0x2100
障害が発生しているアプリケーションの開始時刻: 0x01db40619b712d57
障害が発生しているアプリケーション パス: C:\Program Files\Nextcloud\nextcloud.exe
障害が発生しているモジュール パス: C:\Windows\System32\ucrtbase.dll
レポート ID: 556279d2-d6a0-42d6-8a73-d31d20709084
障害が発生しているパッケージの完全な名前: 
障害が発生しているパッケージに関連するアプリケーション ID: 

エディション Windows 10 Pro
バージョン 22H2
インストール日 ‎2024/‎03/‎23
OS ビルド 19045.5131
エクスペリエンス Windows Feature Experience Pack 1000.19060.1000.0

[Wyrm82]

Windows 11 Korean here, I have two PCs the clients are crashing since 3.14 update. This seems to be a locale issue?

[CuteRogue]

nextcloud 3.15 just stuck in task manager.. i rolled back to 3.13.3 and it was ok

[karlisi]

@fuchse-ohren Thank you! It works for me.

And after nextcloud works fine, uncheck Unicode utf-8 support seems to be OK. (Because this option will cause other language display problems like ftp...)

Tested on Windows 11, NC client 3.15.0, unchecking UTF-8 reverts to crashing Nextcloud client. Still waiting for fixed version.

[zhiiwg]

@fuchse-ohren Thank you! It works for me.
And after nextcloud works fine, uncheck Unicode utf-8 support seems to be OK. (Because this option will cause other language display problems like ftp...)

Tested on Windows 11, NC client 3.15.0, unchecking UTF-8 reverts to crashing Nextcloud client. Still waiting for fixed version.

Yes you're right, after some reboot client crash at the sync starts again.

[waylon2002my]

If you experience crashes in a non-English environment, please try the following mitigations. However, this operation may cause garbled characters in some software.

1. Open the Settings application.
2. Click on “Time and Language” > “Language and Region
3. Click on “Administrative language settings” in the relevant settings at the bottom of the screen.
4. A new window will open. Click on “Change system locale”.
5. Check “Beta: Use Unicode UTF-8 for worldwide language support (U)”
6. Click “OK” and restart

Translated with DeepL.com (free version)

--- original language below ---

非英語環境でクラッシュが発生する場合は次の緩和策をお試しください． ただし，この操作を行うと一部のソフトは文字化けする可能性があります．

1. 設定アプリを開く
2. 「時刻と言語」 > 「言語と地域」 の順にクリック
3. 画面最下部の関連設定に表示される「管理用の言語の設定」をクリック
4. 新しくウィンドウが開くので「システムロケールの変更」をクリック
5. 「ベータ:ワールドワイド言語サポートでUnicode UTF-8を使用(U)」にチェックを入れる
6. 「OK」をクリックして再起動

this work for me. TQ for sharing!

[syzop]

We also had many (possibly even all) clients crashing in our organization a couple of weeks ago, all because of one file with a too long filename. Did not contain any special UTF8 characters as far as I could see, just a very long name (in a folder 4 levels deep but nothing special there). Upgraded the client version but didn't help at the time. My colleague noticed it was related to the long filename first, and that if he deleted the file on the client, then restarted nextcloud, that client synced OK again. But then we would have to help people one by one which isn't feasible with 100+ people, so we ended up renaming the file on the server via the webinterface. Took us a while to figure out that this was the cause and that simply deleting or renaming the file on the server fixed it. In the meantime many people could not use the cloud (well they could use the web interface), it was a disaster. Took more than a week, though that was also partially our fault. Users not reporting immediately and us IT staff not realizing how widespread the issue was. Once it was resolved by renaming the file, because we upgraded clients to 3.15.0 we were hit with by the .LNK file not allowing to sync issue (#7579), but at least that affected fewer people.

Sorry if this isn't too much added information (or is it?) but just wanted to make clear it was really bad. Also, yeah, i don't think this is related to UTF8 (unless I overlooked something), similar to #7265.

[minoru9999]

Me too.
I Reinstall 3.13.4, It Work fine.
Source is %AppData%\NextCloud/ or
https://download.nextcloud.com/desktop/releases/Windows/

v3.15.2 is Crash...