[Bug]: Desktop client doesn't sync after unlocking a password protected drive

[ik0api]

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

I notice that since a few versions, desktop client doesn't sync properly after unlocking a password protected drive (for example, after unlocking a password protected WD USB disk) which appears to be locked when Win10 boots up.

Other password-unprotected folders and disks are regularly syncing, instead.

In order to solve the issue I have to exit and restarting the client and everything runs fine.

I'm sure that, in the past (can't say when), when I noticed that a password-protected folder wasn't synced, simply unlocking that folder was enough in order for the client to automatically sync it, no need to force a resync or to restart the client.

Nextcloud Client desktop 3.15.3 running on Windows 10 pro syncing a NextcloudPI service.

Steps to reproduce

1. Wait for Win10 boot and Nextclud client to be fully functional
2. Verify proper syncing of folders while a password-protected folder is still locked
3. Unlock the password-protected folder
4. Verify proper syncing of the unlocked password-protected folder
   ...

Expected behavior

I expect to experience the previous and usual behaviour (automatic sync of folders unlocked after Nextcloud client start)

Which files are affected by this bug

password-protected folders in external USB disks

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Official Windows MSI

Nextcloud Server version

NextCloudPi 28.0.14

Nextcloud Desktop Client version

3.15.3

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 Disabled

Are you using an external user-backend?

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

Nextcloud Server logs

Additional info

[camilasan]

Hi, I think we will need logs to able to work on this.

Does the password protected folder has different permissions than the other folders?
Are you using VFS? => in this case, the client needs to access the files, possibly open them (would need to double check), therefore the operating system would expect a password and the client would fail then to sync it.
What does the whole error message in the desktop client say?

[ik0api]

Hi, thank you for infestigating. Replies follow. Il martedì 4 febbraio 2025 alle ore 12:05:27 CET, Camila Ayres ***@***.***> ha scritto: Hi, I think we will need logs to able to work on this. Does the password protected folder has different permissions than the other folders?      Same permissions  Are you using VFS? => in this case, the client needs to access the files, possibly open them (would need to double check), therefore the operating system would expect a password and the client would fail then to sync it.      No VFS What does the whole error message in the desktop client say?  - BEFORE unlocking the external USB drive the error message says (translated from Italian): "The local folder X:\.....\.... on (server url) doesn't exist - AFTER unlocking the external USB drive the error message reports the same error message, even if I manually force the sync (right click and then FORCE SYNC...)  Screenshot follows: Note: end-to-end cryptography is enabled no server and client More: like I wrote before, I'm totally sure that, formerly, the sync would reactivate spontaneously after I unlocked the USB disk drive Thank you! Marco — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Timmey33]

I came across this article because I noticed the same behavior. I have the data on a VeraCrypt volume that I have to unlock manually after booting. Afterwards, no sync takes place even after hours until I restart the client. I would be happy if the problem can be solved.