Virtual File System - How to exclude certain folders (as it is possible in classic mode)

Hi Folks

My default Folder Sync Connection (FSC) targets to E:\Local\OwnCloud on my Windows 10 PC.
Virtual File System (VFS) is activated. Everything works as it should.

I now wanted to add an additional (classic not VFS) Folder Sync Connection to sync my standard Windows 10 Documents folder which is part of my profile to a remote folder \Profile\Documents of the same OwnCloud Account.

First of all the Desktop client tells me:

Warning: You are already syncing /, which is a parent folder of /Profiles

Okay. The desktop client is clever and informs me about the conflict. So my next step was to exclude the /Profiles folder from syncing in the default FSC as I would do it in classic mode.

I was very surprised when I learned that it is not possible to exclude certain folders in my default Folder Sync Connection (which has Virtual File System enabled).

I ignored the warning and did create the new Folder Sync Connection for the Documents folder.
The synchronization works but all the synced files from Documents reappear in the default Folder Sync Connection under E:\Local\OwnCloud\Profiles\Documents as Virtual Place-Holder files.

I mean it doesn’t harm but it is not very nice.

Did I make something wrong ? How can I exclude a specific folder from syncing in VFS-Mode ?
I mean this should definitely be possible as it is in classic mode. There is no obvious and technical reason to me why this should not be possible.


Not implemented yet, but could be improvements for the future…

1 Like

Thank you for the quick answer.

Sounds to me like an important feature. As lot’s of users maybe don’t want to clutter their local disk with thousands of Place-Holder files :slight_smile:


Importance and urgency are always relative. Just FYI, these 4 issues will be probably implemented before an exclusion feature:

I hope I’ll find a way to make the roadmap more transparent…

1 Like