Permissions changed to "Deny All" on Nextcloud sync folder after a reboot

I’m getting tired of this. Starting with Windows client version 3.14.2, maybe earlier, 3.13.0 I think was the last one that didn’t have this problem, randomly after a reboot permissions are changed to “Deny All” on Nextcloud sync folder so the client fails to sync. Permissions need to be fixed by hand. I have 6 Windows 11 PCs, it happens randomly on all of them, at least once a day. Always after a reboot, not sure if it happens after wakeup too (I turn them off for the night). I’m currently on client 3.15.0. I also have, well had for a month, a Fedora 41 KDE PC and this never happened with the Linux client, only on Windows.

This only happens to the Nextcloud sync folder (inCloud in the screenshots, not related to the inCloud company, just a name for my instance), I have no other permission issues with anything else, it’s clearly Nextcloud related.

Any ideas? Thank you.

Windows 11 Pro 23H2
Nextcloud Desktop 3.15.0
Nextcloud Hub 8 29.0.3
Ubuntu 24.04.1

Do you use other sync solutions to sync the same folder?

Which “security” products do you use, do they restrict something because they think Nextcloud client is bad?

I found this issue on the bug tracker:

Nope, only Nextcloud, no other sync solutions. No third party antivirus either, just Windows 11 stock Defender. Yes, Defender was the first thing that I though of, but that doesn’t seem to be it, as it normally pops up notifications when it blocks something and there were no warning or error notifications from Defender on any of these machines for months, and I’d rather not exclude 800GB of files from security scans. Yes, this is exactly the same issue as the one you linked to. I added to the report on Github, thanks for the link!

No idea what’s going on, but I bet it’s a bug in the client as it started some months ago immediately after upgrading the clients on all machines.

So I rolled back to an older client version and it stop happening, didn’t happen for months. Then I updated few weeks ago because they added dark mode and I’m a sucker for dark mode. Now I regret it but I’m not sure if it’s a good idea to downgrade to much older client at this point.

Same issue here - it’s driving me batty.

AdamAnon - which version of client were you running that did not do this? I will likely downgrade back until this gets solved.

I have a note that says 3.13.0 was the last version that wasn’t doing this.

However, I’ve updated my clients last week to 3.15.3 (I was running 3.15.0 at the time I started this thread) and it hasn’t happened since. It used to happen every single day. Crossing fingers.

I am running 3.15.0 as well - thanks for the info, I will bump up to 3.15.3 and hopefully it goes away.

1 Like