Nextcloud creating duplicate folders inside itself, recursively, for any sync after upgrading to v4.0.0 Windows Desktop Client

DenisLu · October 23, 2025, 1:37pm

github.com/nextcloud/desktop

[Bug]: V4.0.0 - a folder, a subfolder with the same name as the parent folder is created

opened 09:16PM - 21 Oct 25 UTC

closed 07:31AM - 30 Oct 25 UTC

vagner-dias

4. to release bug Prio: high os:

Windows feature:

virtual filesystem

### ⚠️ 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](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions. - [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/) ### Bug description In NC Client 4.0.0, in a fresh install, After proceeding with the the initial sync, if the user enters a folder, a subfolder with the same name as the parent folder is "created" ### Steps to reproduce 1. Install the desktop client V4.0.0 (it must be a fresh install) 2. connect an account 3. Start entering any folder structure. the issue will start to manifest ### Expected behavior No subfolder should be created. ### Which files are affected by this bug Folders only ### Operating system Windows ### Which version of the operating system you are running. Windows 11 ### Package Official Windows MSI ### Nextcloud Server version 31.0.8 ### Nextcloud Desktop Client version 4.0.0 ### 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? - [x] Default internal user-backend - [ ] LDAP/ Active Directory - [ ] SSO - SAML - [ ] Other ### Nextcloud Server logs ```shell ``` ### Additional info _No response_

RonSchui · November 5, 2025, 9:39am

We still have the same problem, even with V4.0.1. The only solution so far has been to revert to V3.17.3.