Delayed syncing issues on Windows (possible antivirus related) - Problem with 34.0.2/3: worked perfectly with 3.0.7
- Dominant language
- C++
- Stars
- 3.9k
- Forks
- 1k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 123
Description
### ⚠️ 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 have searched for 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
I have NextCloud installed on two different computers:
- One at my office,
- and one at home, where I work remotely.
NextCloud 34.0.3 works perfectly at home. However, it barely works on my work computer. The main difference between the two is that they don’t have the same antivirus software: Malwarebytes on my personal computer and Microsoft Defender on my work computer.
-------
J'ai NextCloud d'installé dans 2 PC différents
- Un sur mon bureau professionnel,
- un à mon domicile où je télétravaille
Nextcloud 34.0.3 fonctionne parfaitement à mon domicile. Par contre, il ne fonctionne quasiment pas sur mon PC professionnel. La difference notable entre les deux : il n'ont pas le même anti-virus : Malwarebite sur mon perso, Microsoft defender sur mon Pro.
### Steps to reproduce
I worked all day on my work computer yesterday. Today, I’m working remotely, and when I went to check my files, nothing had been saved since the last update at 12:00 p.m. the day before, so all my work from the afternoon wasn’t saved to the servers via NextCloud on my work computer (Microsoft Defender).
I noticed that on my work computer, the antivirus was triggering frequently and using a lot of memory and CPU resources while running numerous scans. It seems that this is where the problem stems from. But I’m not knowledgeable enough to go into the details. I found an old error report for version 34.0.1—perhaps the issue hasn’t been resolved? (Translated with DeepL)
>https://github.com/nextcloud/desktop/issues/10580
Historique :
https://github.com/nextcloud/desktop/issues/10464
### Expected behavior
https://github.com/nextcloud/desktop/issues/10463
### Which files are affected by this bug
All
### Operating system
Windows
### Which version of the operating system you are running.
Windows 11 sur les 2 PC
### Installation method
Official Windows MSI
### Nextcloud Server version
3 differents
### Nextcloud Desktop Client version
34.0.1 puis 2 puis 3
### Did this occur after an update or on a clean installation?
Minor version update (i.e. 33.0.0 → 33.0.1)
### Are you using the Nextcloud Server Encryption module?
No
### Are you using an external user-backend?
- [x] Default internal user-backend
- [ ] LDAP or Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
```shell
```
### Additional info
_No response_
Contributor guide
Research direction
Start by reviewing the linked issues 10580, 10464, and 10463, then reproduce the delayed syncing on Windows 11 with Nextcloud Desktop 34.0.1–34.0.3 and Microsoft Defender enabled. The report provides no affected file, logs, or test; done would require isolating the cause and documenting a reproducible fix or confirmed interaction with antivirus scanning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100