[Bug]: Updated client to 3.15.1 and getting error The Virtual filesystem feature does not support a drive as sync root

[ThaDaVos]

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

For a few computers I am using the VIrtual Filesystem, the mountpoint is C:\{SYNC_DIR} - this used to work but now suddenly the applications throws the below error:
The Virtual filesystem feature does not support a drive as sync root

Just to note, it was setup before.

Steps to reproduce

Have virtual filesystem set up in a directory on de C:\ drive - and update to 3.15.1

Expected behavior

It should just sync

Which files are affected by this bug

All

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Official Windows MSI

Nextcloud Server version

30.0.4

Nextcloud Desktop Client version

3.15.1

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

No response

[mayonezo]

Same here. I tried turning off virtual file support, but that only made the client crash.

Edit: Reverting to client version 3.15.0 got rid of the error.

[mayonezo]

Nevermind, 3.15.0 now crashes as does 3.14.3

[ThaDaVos]

I downgraded from 3.15.1 to 3.15.0 and it fixed it for me, so your crash may have a different cause

[mayonezo]

Maybe because I tried to turn off virtual file support.

[ThaDaVos]

Ah maybe it didn't convert the files back so now it tries to sync files pointing to itself

[claudiocandio]

same error here, it works ok with the 3.15.0

[tame47]

same issue, worked well before upgraded to 3.15.1

[ner00]

Have you tried using NOT NextCloud? It'll probably work better.

[WHIFAN]

Same issue, resolved with downgrading.
Seems 3.15.1 crashes if i try to delete folder and if i try to log out.
[ner00], have you tried answering, only if someone asks you? It'll probably work better.

[syurev]

Same issue

[Quasarrs]

Also the whole disk is full of errors. Downgraded the version to 3.15.0
Installed over 3.15.1. Everything works correctly.

[EagleonePrimo]

same here use "F:\Nextcloud" has the problem and rollback to 3.15.0 it work perfectly fine.

[bernhardkaindl]

Seems 3.15.1 crashes if i try to delete folder and if i try to log out.

Same here, and also crashes when trying to remove the account after the update in order to workaround the error message from

• [Bug]: 3.15.1 Multiple accounts sharing a folder - NOT! #7657

I choose to reinstall 1.14.3, remove the folder and the account.

I then re-installed 1.15.1, re-added the account and then got the virtual filesystem error. As a workaround, I resorted to add some of the top-level directories instead of the top-level "Nextcloud" folder.

This workaround would be fine, but now clicking on a cloud-only file opens the Windows explorer download/progress window as usual, but the download download progview is stuck at 0% until a the very end of the file download next to 100%. When selecting "Always keep on this device" on the in-transfer file in the Explorer in parallel to the running download makes the download progress graph snap into action.

I'm curious how so many regressions creeped into the 1.15.1 "bugfix" release.

[Eisteed]

Same issue here, rolled back to 3.15.0 got so many errors updating nextcloud client and having to rollback to previous version recently.. is there any real test before pushing updates (real production usage) ??

I guess it's just best to wait a month before updating to any new version now..

[PilaScat]

Same but with D: drive

[Styx13]

Same issue after updating to 3.15.1 , using VFS and my nextcloud folder is in C:\Nextcloud
Please do more testing before pushing updates (and BTW, updates of the client are way to frequent)

[dxma]

same issue here, my folder is e:\Nextcloud.
version 3.15.1

[adi-dev]

Just updated to 3.15.1 and some of the folders are showing this error. I have two different accounts - one is syncing okay (5 folders), the other only 1 out of 4 folders (the smallest one). Both accounts have roughly the same amount of data (qty/GB)

[sebaxakerhtc]

Same error 3.15.1

Downgrading to 3.15.0 helped
https://github.com/nextcloud-releases/desktop/releases/tag/v3.15.0

[knot-split]

I had the same problem. Using the earlier version once more and to solve the problem.

[kuchenmann]

Same here. I tried turning off virtual file support, but that only made the client crash.

Edit: Reverting to client version 3.15.0 got rid of the error.

Same here.
Why is such SHIT distributed to users?

[xjzsq]

I found the same bug in owncloud's client issue, so I created a PR to fix it. Waiting for review & merge.

[Phils80]

Same issue here, additionally after update of Android client I was blocked due to unsuccessful login interpreted by NC as brutforce attack, not sure if related. I was forced to manually correct it in mysql and unblock admin user.

[neoacevedo]

What's more buggy is the fact the error says multiple accounts are sharing the Nextcloud folder but the PC us used by an only one account.

[Schmidtjanroman]

Same issue here. A downgrade to 3.15.0 solved this one for me now.
The last few updates of NC client and hosts really got me with many issues, it's always like gambiling and makes me as a user really worrying about my data.
Seems like they're focusing more and more to run NC for big companies and not anymore for single users with an easy-to-use aspect. Remembering the #OwnYourData time "back then".

[sassanix]

I too have this issue, I have followed these commands:

occ ‘files:scan --all’ occ ‘files:cleanup’

And that didn't fix it.

I have re-installed the desktop program for windows, and the same exact error.

I re-installed 3.15.0 and the error has stopped.

For those looking to downgrade, go here: https://download.nextcloud.com/desktop/releases/Windows/

[Krautmaster]

how can such a bug make it into production?

[naiz0]

how can such a bug make it into production?

the better question is, why is such an update released on a Friday?

[regs01]

Was just offered to upgrade and same error after upgrade. It would be better to call out 3.15.1 and remove it from releases.

[M3psipax]

Can we just ignore the error? Will it keep synchronising the files in spite of it?

[camilasan]

Can we just ignore the error? Will it keep synchronising the files in spite of it?

It won't synchronize.

[Nerodacles]

+1

Just downgrade!

[JoseRamirezMoreno]

Incredible how this incredibly bad update got to stable channel. I can't believe it.

I got the virtual filesystem error. So I did the following:

1. Tried to remove the accounts (2 accounts). It crashed without removing the account.
2. Tried to remove the folder sync connection. Crashed without removing it.
3. Long story short.. I had to uninstall, clean directories, clean Windows registry manually.
4. Reinstalled clean. Same error.
5. Tried adding each folder I have in root as sync connection (8 folders). Lots of errors. Some folders worked ok, others not.
6. I said F it.
7. Uninstalled and cleaned everything once again.
8. Installed 3.15.0 and it is Ok now.
9. First thing 3.15.0 does is notify me of 3.15.1 update.
10. I said F your update. Disabled automatic update.
11. I said many times F whoever let this thing into stable release.
12. Bye

[SofianeLasri]

I don't know how you manage to regress with each update you publish...
Anyway, here is my path:

[JoseRamirezMoreno]

You will have to downgrade to 3.15.0

[SofianeLasri]

Yes, like every time...

[Rello]

fyi: the update was just removed from the update server and will not be announced anymore. fix in progress

[JoseRamirezMoreno]

Nice. Thanks for the fast reaction.

[Sieboldianus]

Temporary fix with:

choco install nextcloud-client --version 3.15.0 --allow-downgrade

[MrBLif]

same here. downgraded to 3.14.3 (was the last setup i have here)

[Rello]

3.15.2 was released.
We are sorry for the inconvenience caused

[A1exan10er]

3.15.2 was released. We are sorry for the inconvenience caused

Hello Rello, my nextcloud client is on Windows and its version is 3.15.1. I want to update it but it showed my version is the latest and cannot update. How to solve this problem?

[Sieboldianus]

3.15.2 was released. We are sorry for the inconvenience caused

I know that testing on Windows is difficult. But there must be a way to maybe just add integration testing in CI on some Windows VM to avoid these issues in the future. For the size of the Nextcloud client user base, it would definitely make sense to test before releasing. This was not the only issue that could have been avoided with proper testing. There have been others recently, such as the symlinked/mklinked folders suddenly syncing again after the issue was fixed 3 years ago.

[Rello]

Hello,
please try again now. we had an issue with the signature of a package. 3.15.2 should be announced now

[Ancillius]

Good news, 3.15.2 seems so resolve the issue (didn't downgrade and waited for a solution from the devs)

Thanks!

[Catriks]

Hello, please try again now. we had an issue with the signature of a package. 3.15.2 should be announced now

Thank you, that fixed it!

I'm just curious, was it not possible to have users not need to install 3.15.1 and just update straight to 3.15.2?
I got the error some 15 minutes ago after updating to 3.15.1, and was almost downgrading my install as per previous tips, but I half accidentally went to the client settings and saw that there was another update already.

[Sieboldianus]

On choco, I had to specify the exact version, as otherwise 3.15.1 would be installed (I guess due to caching or some sort of package lag):

choco install nextcloud-client --version 3.15.2