Sync Client Uses Too Much CPU on Windows: OneDrive for Business Fix

Your Windows PC becomes sluggish, the fan spins loudly, and Task Manager shows the OneDrive sync process consuming 30 percent or more of your CPU. This problem often occurs after a large file sync, during a Known Folder Move operation, or when the sync engine is stuck on a corrupted file. The cause is usually a runaway sync loop, excessive file change detection, or a misconfigured Files On-Demand setting. This article explains why OneDrive uses excessive CPU and provides five proven fixes to restore normal performance.

Why OneDrive Sync Client Uses High CPU

The OneDrive sync client on Windows uses a background process called OneDrive.exe (or OneDriveStandaloneUpdater.exe) that monitors file changes in real time. When you add, delete, or modify a file, the sync engine detects the change, uploads or downloads the delta, and updates the local file state database. High CPU usage occurs when this detection-and-sync loop runs continuously without completing.

Common Technical Root Causes

The most frequent triggers for sustained high CPU usage include:

• Large sync backlog: After a long offline period or after enabling Known Folder Move, OneDrive must process thousands of file changes at once. The sync engine queues them and works through the list, causing a temporary CPU spike that can last several hours.
• Corrupted file in the sync folder: A single file with a name that exceeds the character limit, contains unsupported characters, or has a permission conflict forces the sync engine to retry repeatedly. Each retry consumes CPU.
• Files On-Demand misconfiguration: When Files On-Demand is disabled, OneDrive downloads every file to the local drive. Large files or many files cause constant disk I/O and CPU usage.
• Third-party antivirus interference: Security software that scans every file change in real time can cause a feedback loop with OneDrive. The sync client detects a change, the antivirus locks the file, and OneDrive retries.
• Multiple sync clients running: Having both the personal OneDrive client and the OneDrive for Business client active on the same machine can double the CPU load.

How to Diagnose and Fix High CPU Usage in OneDrive

Before applying any fix, confirm that OneDrive is the cause. Open Task Manager with Ctrl+Shift+Escape, click the CPU column header to sort by highest usage, and look for the OneDrive.exe process. If it consistently shows above 20 percent for more than five minutes while you are not actively syncing files, proceed with the steps below.

1. Step 1: Pause and Resume OneDrive Sync
   Right-click the OneDrive cloud icon in the system tray. Select Pause syncing and choose 2 hours. Wait 30 seconds, then right-click the icon again and select Resume syncing. This stops the current sync queue and forces OneDrive to re-evaluate all pending changes. Check Task Manager after two minutes. If CPU drops below 10 percent, the issue was a temporary backlog.
2. Step 2: Disable and Re-enable Files On-Demand
   Right-click the OneDrive icon and select Settings. Go to the Sync and backup tab. Click Advanced settings. Under Files On-Demand, toggle the switch to Off. Wait 30 seconds, then toggle it back to On. This clears the local file state cache and rebuilds the placeholder file list. CPU usage should normalize within one minute.
3. Step 3: Reset OneDrive Sync Client
   Press Windows+R, type onedrive.exe /reset, and press Enter. A command prompt window opens briefly and the OneDrive icon disappears from the system tray. Wait 60 seconds. Press Windows+R again, type onedrive.exe, and press Enter. The sync client restarts and performs a full re-sync of all files. This clears the local sync database without deleting any files from your PC or the cloud. Monitor Task Manager for the next five minutes. CPU should stay under 15 percent after the initial scan completes.
4. Step 4: Exclude OneDrive Folders from Antivirus Real-Time Scanning
   Open your antivirus software settings. Add an exclusion for the OneDrive folder. The default path is C:\Users\[YourUsername]\OneDrive - [CompanyName]. Also exclude the OneDrive cache folder at C:\Users\[YourUsername]\AppData\Local\Microsoft\OneDrive. After adding the exclusions, restart the OneDrive process by right-clicking the icon and selecting Close OneDrive, then launch it from the Start menu.
5. Step 5: Unlink and Re-link Your OneDrive Account
   Right-click the OneDrive icon and select Settings. Go to the Account tab and click Unlink this PC. Confirm the prompt. After unlinking, sign in again with your work or school account. This rebuilds the entire sync relationship and clears any corrupted account tokens. CPU usage should return to normal after the initial sync completes.

If OneDrive Still Uses Too Much CPU After the Main Fix

If none of the above steps reduce CPU consumption, the problem may be related to a specific file, a group policy conflict, or a corrupted OneDrive installation. Check the following scenarios.

OneDrive Stuck on Processing Changes for a Single File

Open File Explorer and navigate to your OneDrive folder. Sort by Status to find files with a sync error icon such as a red X or a yellow triangle. Rename the problematic file by adding .old to its extension. Wait 30 seconds. If the sync client resumes normal CPU usage, delete the renamed file from your OneDrive folder and upload a clean copy.

Group Policy Forces Continuous Sync

Your IT administrator may have configured a group policy that disables Files On-Demand or forces all files to sync immediately. Contact your help desk and ask them to check the policy setting at Computer Configuration > Administrative Templates > OneDrive > OneDrive Files On-Demand. If the policy is set to Disabled, you cannot reduce CPU usage locally and must request a policy change.

Corrupted OneDrive Installation

When the reset command does not resolve the issue, the OneDrive client files themselves may be damaged. Download the latest OneDrive for Business installer from the Microsoft 365 admin center. Run the installer in repair mode. After the repair completes, restart your computer. CPU usage should drop to under 5 percent at idle.

Files On-Demand vs Always Keep on This Device: Performance Comparison

Item	Files On-Demand (Recommended)	Always Keep on This Device
CPU usage at idle	0-3 percent	5-15 percent
Local disk space required	Minimal (placeholder files only)	Full file size of all synced items
File change detection overhead	Low — only placeholders are monitored	High — every file is watched by the file system
Sync completion speed	Faster for initial sync	Slower because all files must download
Best use case	Most users with stable internet	Offline workers or compliance requirements

You can now diagnose and fix high CPU usage caused by the OneDrive for Business sync client on Windows. Start with the pause-and-resume method, and escalate to the reset or antivirus exclusion if needed. For persistent issues, check for a single stuck file or ask your IT team to review group policies. After applying the fix, verify that the OneDrive process in Task Manager stays below five percent when no files are actively syncing.