nextcloud
[Bug]: 4.0.0 and 4.0.1 crashes
⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a bug, not a question or a configuration issue.
- [x] This issue is not already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
- [x] I agree to follow Nextcloud's Code of Conduct
Bug description
Nazwa aplikacji powodującej błąd: nextcloud.exe, wersja: 4.0.1.403, sygnatura czasowa: 0x68ff996a Nazwa modułu powodującego błąd: ntdll.dll, wersja: 10.0.22621.6060, sygnatura czasowa: 0xac55daa3 Kod wyjątku: 0xc0000374 Przesunięcie błędu: 0x000000000010d5f9 Identyfikator procesu powodującego błąd: 0x0x6E4C Godzina uruchomienia aplikacji powodującej błąd: 0x0x1DC4DD530FFF099 Ścieżka aplikacji powodującej błąd: C:\Program Files\Nextcloud\nextcloud.exe Ścieżka modułu powodującego błąd: C:\Windows\SYSTEM32\ntdll.dll Identyfikator raportu: 719551a8-d93f-4b85-ab04-c7172cbe92e9 Pełna nazwa pakietu powodującego błąd: Identyfikator aplikacji względem pakietu powodującego błąd:
I have added [General] logDebug=true but the last logs are:
2025-11-05 11:29:06:159 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-34592\client-building\desktop\src\libsync\discovery.cpp:1117 ] [ OCC::ProcessDirectoryJob::folderBytesAvailable ]: Returning unlimited free space (-3) for item quota. 2025-11-05 11:29:06:159 [ debug nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-34592\client-building\desktop\src\libsync\discovery.cpp:1889 ] [ OCC::ProcessDirectoryJob::processFileFinalize ]: Processing "XSL/KDBX_Tabular_HTML.xsl" | (db/local/remote) | valid: true/db/db | mtime: 1746536059/0/0 | size: 3100/0/0 | etag: "d95704cbd3e65887ccfe4ba66a3bfa81"//"" | checksum: "SHA1:e045f584fad9737aa65d3753b661f3f851ed8963"//"" | perm: "GWNVS"//"" | fileid: "00234309oc9ae7rj2qnb"//"" | inode: 76079/0/ | type: CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeSkip/CSyncEnums::ItemTypeFile | e2ee: false/false | e2eeMangledName: ""/"" | file lock: not locked// | file lock type: ""//"" | live photo: false//false | metadata missing: /false/
Steps to reproduce
Random crashes on 2 Windows 11.
Expected behavior
No crashes
Which files are affected by this bug
nextcloud.exe
Operating system
Windows
Which version of the operating system you are running.
Windows 11
Package
Official Windows MSI
Nextcloud Server version
31
Nextcloud Desktop Client version
4.0.1
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 3.16.3 to 3.17.0)
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
Additional info
No response
Same errror; Random crashes with 4.0.1 on Windows 11
Foutbucket 1619213935185934890, type 4
Naam van gebeurtenis: APPCRASH
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0
Handtekening van probleem:
P1: nextcloud.exe
P2: 4.0.1.403
P3: 68ff996a
P4: StackHash_74e4
P5: 10.0.26100.3323
P6: facafff0
P7: c0000374
P8: PCH_CA_FROM_ntdll+0x0000000000160344
P9:
P10:
Toegevoegde bestanden:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bf638d80-4296-42e6-911c-b97115340dd4.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.177e2968-d3f3-4101-a55e-42c646554c9d.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0cd6a7dc-faf4-4aa2-9f86-f3631c8917c0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.51a76d84-2b4c-4684-9501-cfa7a47938cf.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5a3418cb-55e3-40cb-aa0f-a8e6042853e7.tmp.xml
Deze bestanden zijn mogelijk hier beschikbaar:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nextcloud.exe_787935fdddb462678fa5cf59167ef9cef78834d4_f21c9a05_c0a5e38e-1b98-433e-8fe5-782ca0b5a7dd
Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 5f61fb30-a97b-490e-9f32-1217bfec83ee
Rapportstatus: 268435456
Opgedeelde bucket: 83aca5fa5a96954656789a7ebe1eba2a
GUID van CAB-bestand: 0
Toepassingsnaam met fout: nextcloud.exe, versie: 4.0.1.403, tijdstempel: 0x68ff996a Naam van foutmodule: ntdll.dll, versie: 10.0.26100.3323, tijdstempel: 0xfacafff0 Uitzonderingscode: 0xc0000374 Foutoffset: 0x000000000008b035 Foutproces-id: 0xBF98 Begintijd van foutieve toepassing: 0x1DC4D9D0AC560F3 Faulting-toepassingspad: C:\Program Files\Nextcloud\nextcloud.exe Faulting-modulepad: C:\WINDOWS\SYSTEM32\ntdll.dll Rapport-id: 5f61fb30-a97b-490e-9f32-1217bfec83ee Faulting-pakket volledige naam: Faulting-pakket-relatieve toepassings-id:
Hey, could you upload the crash dumps (apparently inside \ProgramData\Microsoft\Windows\WER\Temp) and a client debug archive to https://cloud.nextcloud.com/s/wyEY5iBdnM9JdSC ?
Confirming Version 4.0.2 with Windows 11 does this, too. Randomly crashes in the background w/o further notice. You just get it, if you try to open a file on a NC related resource and Windows replies, the file is not there. Restarting NC Desktop Client solves this for the moment. Adding some Windows Eventlog Info from the recent crash:
TimeGenerated : 02.12.2025 18:15:52
Message : Fault bucket 1885402407015695953, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: nextcloud.exe
P2: 4.0.2.500
P3: 6924566a
P4: StackHash_74e4
P5: 10.0.26100.7019
P6: 9c8f8241
P7: c0000374
P8: PCH_43_FROM_ntdll+0x0000000000162814
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b06ea261-cff5-452e-8b63-b77cc7ecd59d.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bc77547e-2541-4399-af71-48c097aa8a9e.tmp.WERInte
rnalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ae814beb-5fde-426e-8d9e-13c7e1a613b7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.18bb74e9-685e-47a4-a2f0-7bf1f5c83d9b.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6158c44b-7bc2-4fb0-b7d5-2a2ca530078c.tmp.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nextcloud.exe_35391b7c4f8b6f6d4faa
24c94bd8c0fdb72b9ba1_f8393431_f96ba6da-8e95-4578-b60c-ade15ef60717
Analysis symbol:
Rechecking for solution: 0
Report Id: 61fd0b25-9eae-4f74-8969-84bdce201396
Report Status: 268435456
Hashed bucket: b713059c2e3aefb6da2a4b7ff8d64651
Cab Guid: 0
ReplacementStrings : {1885402407015695953, 4, APPCRASH, Not available…}
TimeGenerated : 02.12.2025 18:15:49
Message : Faulting application name: nextcloud.exe, version: 4.0.2.500, time stamp: 0x6924566a
Faulting module name: ntdll.dll, version: 10.0.26100.7019, time stamp: 0x9c8f8241
Exception code: 0xc0000374
Fault offset: 0x0000000000117885
Faulting process id: 0x203c
Faulting application start time: 0x1dc6395baa67af8
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 61fd0b25-9eae-4f74-8969-84bdce201396
Faulting package full name:
Faulting package-relative application ID:
ReplacementStrings : {nextcloud.exe, 4.0.2.500, 6924566a, ntdll.dll…}
@inoculator could you please upload the files mentioned in the event log to https://cloud.nextcloud.com/s/5P8FpTfn75Y8MTW so I can analyse them?
These crash reports don't really tell me anything on its own, only that there was a crash that happened somewhere within a Windows API call, but not where and why...
@nilsding did so. Unfortunately all those files mentioned in that event seem to already have been removed from TEMP (maybe by reboot o.s.). I only found that "report.wer" file left in the folder mentioned "These files may be available here:". Hope this helps.
@inoculator sadly the report.wer isn't too helpful either -- at least I couldn't find a way to get a stack trace out of it. However I noticed that the list of loaded modules (i.e. DLLs) contains some Citrix DLL for some reason. I wonder if that might be causing some trouble, but as we don't have access to a Citrix environment ourselves we cannot test for that.
For convinience: I have setup a scheduled task with an event trigger. XML Filter reads like this:
<QueryList>
<Query Id="0" Path="Application">
<Select Path="Application">
*[EventData[Data[@Name="AppName"] = "nextcloud.exe" or Data[@Name="P1"] = "nextcloud.exe"]]
</Select>
</Query>
</QueryList>
Triggered event: msg * "Nextcloud crash detected"
As soon as it crashes again, I will get a popup and hopefully the files do exist at that time. I post here, as soon as I have evidence.
BTW: Yes, I am working on CWA very often. Unfortunately I cannot provide you any access to test ;-) Question would be, if other crashed instances do have CWA installed, too.
I had some unresolved file conflicts that where piling up. After clearing them I have not seen any more crashes.
I am still tracing. Had have several crashes, but those dump files never were created. Tweaked Win reg at certain keys, but no success. But I was able to narrow it down to Google Chrome. I am syncing the data folder of Chrome for backup reasons (testing something for another project). The crashes occur if NC is syncing that folder and I launch Chrome. So it seems like a file access conflict at launch of Google Chrome from my PoV.
I've been seeing crashes since 4.0.0 and subsequent versions to 4.0.3.579 on Windows 11. This is now happening two or three times a day:
Win+R > eventvwr.msc > Windows Logs > Application > Filter Current Log ... (Rt Pane) > [/] Error > General
Error 2025-12-09 10:29:23 Application Error Application crashing events
Faulting application name: nextcloud.exe, version: 4.0.3.579, time stamp: 0x692ffaaa
Faulting module name: ntdll.dll, version: 10.0.26100.7019, time stamp: 0x9c8f8241
Exception code: 0xc0000374
Fault offset: 0x0000000000117885
Faulting process id: 0x8F3C
Faulting application start time: 0x1DC688878CDC7D3
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: dcb5b681-c8d9-4f3f-9943-0cbaf67502f0
Faulting package full name:
Faulting package-relative application ID:
Error 2025-12-09 09:15:58 Application Error Application crashing events
Error 2025-12-09 09:15:57 Application Error Application crashing events
Error 2025-12-08 10:29:23 Application Error Application crashing events
Error 2025-12-08 10:04.02 Application Error Application crashing events
Error 2025-12-07 21:25:06 Application Error Application crashing events
Error 2025-12-07 15:40:02 Application Error Application crashing events
Error 2025-12-07 11:49:51 Application Error Application crashing events
Error 2025-12-06 20:28:12 Application Error Application crashing events
Error 2025-12-06 17:14:20 Application Error Application crashing events
I have logDebug=true, but the last entries in the latest nextloud log show nothing of interest, just routine info activity:
2025-12-09 10:04:50:943 [ info nextcloud.sync.discovery C:\Users\User\AppData\Local\Temp\windows-35544\client-building\desktop\src\libsync\discovery.cpp:1886 ]: discovered "<redacted_file_path>" CSyncEnums::CSYNC_INSTRUCTION_SYNC OCC::SyncFileItem::Up CSyncEnums::ItemTypeFile
which is 25 minutes prior to the last crash. I'm happy to help with any debug investigations (availability permitting).
Is there a way to bump this up to get some attention?
@nilsding I found them... finally... Shout-out to https://helgeklein.com/blog/creating-an-application-crash-dump/ which lead me on the right path. I have uploaded one of the latest DMP files. Please check, if that lifts the curtain a little.
@inoculator Thanks for providing the crash dump (and the link to that blog post, this might be really useful in the future).
Could you give this build a try and report back if the crash still occurs? https://cloud.nextcloud.com/s/kBDcNHMnkdt5rrW That is a build from the temporary feature/backport/9251/stable-4.0 branch which is basically v4.0.4 plus the two commits from PRs #9251 and #9258.
FYI I installed 4.0.4 today, and it is still crashing several times a day. Please let me know how I can help.
I see this [crash] because by default I always have "Settings" [1] running (in an off-centre screen), so I notice as soon as Nextcloud Client crashes. Methinks it is crashing, silently, for many others, but they never notice. That sets a dangerous precident, you are lulled into thinking Nextcloud is doing its job in the background until one day, having relied on an upload or a download only to be cut short -- it hasn't.
[1] "Settings" is a misnomer, I am using this dialog [I wish it was a proper window] as a continuous monitor, never for setting anything (apart from once, right after installation). I can see at a glance all sync'd folders are green (sync'd) and it is safe to proceed with something that relies upon that.
@nilsding I also installed this [Nextcloud-feature-backport-9251-stable-4.0-x64.msi], but I guess we need to wait a few days. Out of interest, did you identify something that could explain the silent crashes?
@Bockeman It appears that too many sync errors (e.g. file conflicts as mentioned in https://github.com/nextcloud/desktop/issues/9025#issuecomment-3619025777, files being modified while the sync is in progress, ...) may have caused those random crashes.
FWIW I observed a random crash similar to this one on a macOS system as well; the stack trace from a macOS crash report is close enough to the Windows one (aside differences between compilers and CPU architectures).
@nilsding it looks like with this intermediate version there are no crashes anymore. Since I installed no popup from the event trigger came to my notice. Thumbs up for this!