[Bug]: NextCloud Client didn't show names of E2E encrypted folders

[christoph-bittmann]

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

I encrypted a folder using nextclouds build in e2e encryption. On my linux client (v3.9.0), from which I started originaly the encryption, I could see all subfolders and files after typing the passphrase. Also on the android client. But the windows client (v3.9.0), which I used on a virtual windows 10 maschine, the encrypted folder still leaves encrypted after typing the passphrase. Strange: After selecting at least one of these encrypted subfolders, files will synchronized and stored unencrypted in the Nextcloud-Folder.

Steps to reproduce

1. Encrypt a folder in the linux client
2. add some files and subfolders to it
3. switch to the windows client
4. unlock with passphrase
5. Subfoldernames are still encrypted

Expected behavior

After unlocking with the passphrase, the "real" names of all encrypted folders and subfolders should be shown.

Which files are affected by this bug

-

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Appimage

Nextcloud Server version

test on: 26.0.3, 27.0.1

Nextcloud Desktop Client version

test on: 3.9.0, 3.9.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 Enabled

Are you using an external user-backend?

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

Nextcloud Server logs

No response

Additional info

No response

[bcutter]

This issue lacks a proper title - what is it about?

[christoph-bittmann]

Thanks @bcutter, I added a, so hopefully proper, title :)