Forum Discussion
Inefficient OneDrive Synchronization Causes Windows Explorer Slowdowns
Hi, I agree this can be painful when Explorer is waiting on sync/status overlays. A few practical things to check: pause OneDrive sync and see if Explorer becomes fast immediately, then look for a stuck file, very large folders, or folders with thousands of small files. Also try enabling Files On-Demand, excluding build/cache folders, updating OneDrive, and running onedrive.exe /reset. If it is reproducible, sending feedback with OneDrive logs is worth doing because performance issues need trace data to be fixed properly.
- NiltonGMJul 10, 2026Brass Contributor
Thank you for the response. I think it's important to rule out a few possibilities that do not apply in my case:
- When I pause OneDrive synchronization, Windows Explorer immediately returns to normal behavior, which strongly suggests that the issue is directly related to the synchronization process.
- The problem is not related to folders containing thousands of files or to file size. The slowdown occurs when a single file is updated, regardless of whether it is small or large. In the past, only the file being synchronized would remain temporarily locked. Today, however, I notice that the entire Windows Explorer is affected, becoming slow or unresponsive for several seconds—and sometimes even minutes—until synchronization is complete.
- Approximately 80% of my OneDrive content already uses Files On-Demand on Windows 11.
- Build folders, cache folders, and development-related temporary files are kept outside of OneDrive, specifically to avoid this type of impact.
- I have already run onedrive.exe /reset multiple times throughout 2025 and 2026, with no noticeable improvement.
For these reasons, my impression is that this is not a local configuration issue, but rather a limitation, regression, or inefficiency in the synchronization engine itself and/or in the integration between OneDrive and Windows Explorer.
What I would really like to understand is whether Microsoft officially acknowledges this behavior and whether there are any plans for optimization or a fix. Similar reports have been raised by users for years, yet there appears to be no clear resolution or public update on the matter.