lejvin
September 20, 2026, 10:19am
6
After some digging I found this old closed github issue:
opened 01:28PM - 07 Jun 24 UTC
closed 07:26AM - 20 Jun 24 UTC
0. Needs triage
### ⚠️ 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
The title says it all. Windows client syncs the root folder to the local PC, although during setup, root folder (all folders) has been unticked and only one subfolder has been selected for syncing. The intended folder gets synced fine as well, but i don't want the files from the root folder.
### Steps to reproduce
Install Nextcloud client, select to choose what to sync, unselect all, select only one subfolder
### Expected behavior
Only the selected subfolder should be synced
### Which files are affected by this bug
not needed
### Operating system
Windows
### Which version of the operating system you are running.
Windows 10
### Package
Appimage
### Nextcloud Server version
28.0.6
### Nextcloud Desktop Client version
3.13.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?
- [ ] Default internal user-backend
- [X] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
_No response_
### Additional info
_No response_
It seems like this behavior I’m seeing is intentional. I feel like this is counter-intuitive and is also not explained anywhere in the documentation. Does anyone know the reason for why they have implemented it like this?
The only two fixes currently are: