[Bug]: Crash when using external/non-default path (in 3.14.x, 3.13.x, but 3.12.x okay)

[matvit92]

⚠️ 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 from version 3.12.3 to 3.13.0 client crash, when using external storage path for files. In my case on SD card. After downgrade to 3.12.4 it working OK.

Issue reported by another user here: https://github.com/nextcloud-releases/desktop/issues/9

Steps to reproduce

Set files path to external media (SD card)

Expected behavior

Client crash

Which files are affected by this bug

No files affected

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Other

Nextcloud Server version

24.0.4

Nextcloud Desktop Client version

3.13.0

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

Updated to a major version (ex. 3.3.6 to 3.4.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

No response

Additional info

No response

[michael-r-elp]

Can confirm, got a call today from someone on 3.13.0 experiencing the same problem, after downgrade to 3.12.4 everything worked fine again.
Logs didn't say anything useful, the event viewer showed that nextcloud crashed within module ntdll with error code 0xc0000005.

[DavidS]

Same on my dad's machine: crashes with 3.13.0; works fine with 3.12.4; has the nextcloud storage on N:\, a mapped drive

[willie68]

Confirm: USB SDD -> crash, same pc local HDD -> works
Nothing in my logs.

[hdmr14]

oh, that's interesting.
local SSD(SATA) -> crashed on my PC.

[matvit92]

oh, that's interesting. local SSD(SATA) -> crashed on my PC.

Mapped in default directory?

[hdmr14]

oh, that's interesting. local SSD(SATA) -> crashed on my PC.

Mapped in default directory?

Ah, No.
I've set up a mapping to 'H:\Nextcloud'.
Sorry for any confusion.

[digimbyte]

same issue, I thought this was related to a case insensitive issue as NextCloud is Case Sensative on the server but it maybe related to external media.
I use a 12TB external HDD for our teams backup/media and its been crashing. I updated because files weren't updating prior.

[haziqnorisham]

Same issue here, sync to external usb hdd will crash on 3.13.0, downgrade to 3.12.4 & sync works.

[pascal142]

Same issue, windows client 3.13 crashes. Downgrade to 3.12.5 is working again
Nom de l’application défaillante nextcloud.exe, version : 3.13.0.55335, horodatage : 0x66280dc7
Nom du module défaillant : ntdll.dll, version : 10.0.22621.3374, horodatage : 0xeae8eecc
Code d’exception : 0xc0000005

[steinjo]

Exact same problem here, windows 11, drive is an encrypted container mapped to X:
Downgrading to client 3.11.0 and it works again

[obriat]

Confirm I got the same problem Windows 10 + Sandisk external SSD on E: drive. But only one of my account made the app crash

[git-ikeda]

Same issue, windows client 3.13 crashes. Downgrade to 3.12.5 is working again.
Windows 11 + External network drive on \network\example\

[unddef]

same issue here with client 3.13.0-x64 on win10
file directory hosted on a veracrypt container mounted to x:\

program starts up. task bar symbol shows up. you can even open the main window. sync process starts and after 1-4 files it crashes. the log files contained no significant error messages.

downgrade to 3.14.5-x64 solved the issue

[ragsna]

Also here Nexcloud client 3.13.0 crashes when using an encrypted drive

• after a few seconds when synching with local sync drive being a Veracrypt-encrypted file container
• happens with two nextcloud server instances (synchronization with both servers was working previously)
• attempt to sync with unencrypted local drive works
• Windows 11 (version 22H2)
• Windows event viewer on local client shows
  Level: Error; Source: ApplicationError
  AppName: nextcloud.exe, AppVersion 3.13.0.55335
  ModuleName: ntdll.dll, ModuleVersion 10.0.22621.3527

[DcryptedCA]

Same issue with crashing on both 3.13.1 or 3.13.0 .
Drive is on SD Card. Runs for 30 seconds and then crashes.
Currently running on 3.12.6 without issues.
Windows 11.

[git-ikeda]

Windows client 3.13.1 also crashes again. Downgrade to 3.12.5 is working.
Windows 11 + External network drive on \network\example\

[willie68]

After 3 months of silence from the development team, is there anything new?

[tigernero79]

News?

[tigernero79]

Is it possible that this bug still exists in release 3.13.x? and no one bothers or is there any solution? a bug that doesn't exist in version 3.12.x

[CleyFaye]

Last time I checked a 3.13.x patch a month ago or so, it was still there. I'll admit I've been reluctant to test more recently, as long as there is no news posted on this issue.

[willie68]

As me. On all my Devices I'm still on the latest 3.12, clicking all the time the "you have to update " box away.

[MichiS97]

Just chiming on this: I've got the exact same problem on my Windows 11 install. I'm synching to a separate HDD and any client version newer than 3.12.x just crashes without notice

[hurgelwurz666]

I have the same problem. I am syncing to a drive encrypted with Veracrypt. The client 3.12.4 works, all subsequent versions crash. The synchronization to an unencrypted drive also works with higher versions than 3.12.4.

[igorneumann]

Any way to prevent it from updating itself?
Even with "Check updates automatically" disabled it keeps updating itself to the latest version.

Im reinstalling the 3.12.3 almost daily.

[willie68]

On every start, I'll get a box with 3 buttons, where i can select what to do.

I'll always take the first button.
On the settings i have selected the stabil update channel, and i do not switch on the automatic check.

[david4office]

Current the Nextcloud desktop client v3.14.1 on my Windows 10 Pro 22H2 still crashed immediately after startup, after uninstall and reinstall v3.12.7, the problem has been solved. but same client version v3.14.1 on my another Windows 11 Pro doesn't have this problem.

[tigernero79]

unfortunately even version 3.14.1 has no cirrettonil bug. on my surface with microsd nextcloud vabin ctash a few seconds after its startup. only version 3.12.x works. but damn i dont know why the bug is still there

[Aesculapius]

Same here, all is updated to the latest on server & client side (3.14.1) but it still crashes after a few seconds. Nothing in the log files to point in the right direction. What can we do to debug further, because staying on 3.12.x isn't a real solution of course...

It does show the crash in Windows Event logger though:

Faulting application name: nextcloud.exe, version: 3.14.1.55839, time stamp: 0x66f6776f
Faulting module name: ntdll.dll, version: 10.0.22621.4111, time stamp: 0x518e67bb
Exception code: 0xc0000005
Fault offset: 0x00000000000783a0
Faulting process id: 0x0x67D0
Faulting application start time: 0x0x1DB17F8E6D5B6F2
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ef885cfc-aede-4a46-8693-270eccc862db
Faulting package full name:
Faulting package-relative application ID:

[david4office]

Ha. Today on my Windows 11, the Nextcloud Desktop Client 3.14.1 also crashed immediately at startup, the following is error log shows in the windows application event logs..
Log Name: Application
Source: Application Error
Date: 10/7/2024 8:06:10 AM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
Description:
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: 0x0x62C0
Faulting application start time: 0x0x1DB184CB26AF9C4
Faulting application path: C:\Program Files\Nextcloud\nextcloud.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 37d38442-ad2f-40da-b658-457b7b7629a2
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-10-07T00:06:10.0664694Z" />
    <EventRecordID>37001</EventRecordID>
    <Correlation />
    <Execution ProcessID="18020" ThreadID="25620" />
    <Channel>Application</Channel>
    <Computer>...</Computer>
    <Security UserID="..." />
  </System>
  <EventData>
    <Data Name="AppName">nextcloud.exe</Data>
    <Data Name="AppVersion">3.14.1.55839</Data>
    <Data Name="AppTimeStamp">66f6776f</Data>
    <Data Name="ModuleName">ucrtbase.dll</Data>
    <Data Name="ModuleVersion">10.0.22621.3593</Data>
    <Data Name="ModuleTimeStamp">10c46e71</Data>
    <Data Name="ExceptionCode">c0000409</Data>
    <Data Name="FaultingOffset">000000000007f6fe</Data>
    <Data Name="ProcessId">0x62c0</Data>
    <Data Name="ProcessCreationTime">0x1db184cb26af9c4</Data>
    <Data Name="AppPath">C:\Program Files\Nextcloud\nextcloud.exe</Data>
    <Data Name="ModulePath">C:\WINDOWS\System32\ucrtbase.dll</Data>
    <Data Name="IntegratorReportId">37d38442-ad2f-40da-b658-457b7b7629a2</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

[Aesculapius]

So this is still an issue in the latest versions and apparently a lot of folks are getting this. How can we proceed as it seems this bug report isn't really followed up. Providing logging could prove difficult as there isn't many... Staying on old versions also is not quite the acceptable long term solution of course. Anyone?

[digimbyte]

until nextCloud becomes the next CrowdStrike - I doubt this is a high priority, since new versions are being pushed without a fix.

[Maxobus]

Also confirm crash on v3.14.3. Windows 10, folder is mapped on virtual (encrypted) drive.
v3.12.x is working fine.

v3.14.3 on MacOS is also working without issues.

[hdmr14]

I tried setting up a junction and a symbolic link to link an external storage to the C drive so that the Nextcloud client would appear to sync files to C:\Users\<username>\Nextcloud, but it still results in a silent crash.
I was considering the possibility that the drive letter or path might be the issue, so I thought this setup would work around it. I'm disappointed. I just hope we can find some kind of workaround.

Windows 11, Nextcloud client 3.14.3

[matvit92]

First test on one of my devices after update to 3.15.0 seems ok. What about the rest of you? Your experiences?

[CleyFaye]

It is a bit early to provide a definitive answer, but my setup that crashed the client almost immediately on 3.13 and 1.14 did synchronize files both way with 3.15.0 and did not crash. It is very promising.

[willie68]

Just updated to 3.15, seems to work... Promising

[3d-pro]

another confirmed that updated from 3.12.x to 3.15.0 seems to fixed the issue.

[Maxobus]

Crash on v3.14.3. Windows 10, folder is mapped on virtual (encrypted) drive. v3.12.x is working fine.

I confirm, that on Windows 10 update from 3.12.x to 3.15.0 fixed the issue.

[hdmr14]

The application still crashes in my environment (Windows 11, Nextcloud Client 3.15.0).
However, I am not sure if the crash is caused by the same issue as before.
In any case, it seems I still need to stick with version 3.12.x.

Faulting application name: nextcloud.exe, version: 3.15.0.56037, time stamp: 0x6744f4a6
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000409
Fault offset: 0x000000000007f6fe

[rootseeker]

The application still crashes in my environment (Windows 11, Nextcloud Client 3.15.0). However, I am not sure if the crash is caused by the same issue as before. In any case, it seems I still need to stick with version 3.12.x.

Faulting application name: nextcloud.exe, version: 3.15.0.56037, time stamp: 0x6744f4a6 Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71 Exception code: 0xc0000409 Fault offset: 0x000000000007f6fe

same exception code 409 here. and i'm running v3.15.0 on win10. NC crashed when syncing file.

when i tried to pause the background sync task and resumed it on the settings page, it crashed on some "unresolved conflicts" message, not sure if that's the cause, but no help removing the files to sync on local machine.

[matvit92]

@hdmr14 @rootseeker I think, its different issue. In my (our) case, it instantly crashed after application start, and there was no log info. Try to open another ticket with your log informations, because this topic is in my opinion solved. I will close it soon.

[Uzurka]

Just updated from 3.12 to 3.15, seems to sync. FInally fixed ?

[rootseeker]

@hdmr14 @rootseeker I think, its different issue. In my (our) case, it instantly crashed after application start, and there was no log info. Try to open another ticket with your log informations, because this topic is in my opinion solved. I will close it soon.

i think you're right. i just saw someone opened a new ticket [#7592 ] and i left my log info there.

[steinjo]

after installing 3.15 with Nextcloud Hub 9 (30.0.2) it works again on my veracrypt drive.
Thanks for fixing it!

[matvit92]

Today i updated to 3.15.1 on 3 windows PCs with external paths and still no problem, so its finally solved. Thanks everyone :)