OneDrive Admin Checklist: shared library sync loops after restart for large document libraries

When users restart their computers, OneDrive for Business may enter a continuous sync loop for shared libraries that contain tens of thousands of files. The sync client repeatedly starts, processes changes, and restarts without ever completing synchronization. This behavior drains system resources, blocks file access, and frustrates end users. The root cause involves a combination of the sync engine’s file-change detection algorithm and the metadata refresh that occurs after every system restart. This article explains why the loop happens and provides a step-by-step admin checklist to resolve it.

Why OneDrive Sync Loops on Large Shared Libraries After Restart

OneDrive for Business uses a local sync database and a change-tracking mechanism to keep files in sync with SharePoint Online. When the computer restarts, OneDrive reinitializes its sync engine and rescans all configured libraries. For large shared libraries containing more than 30,000 items, this rescan process can trigger repeated file-change notifications. Each notification causes the sync engine to re-evaluate the entire library state, creating a loop that never settles into an idle state.

Two technical factors drive this behavior. First, the OneDrive sync engine uses a file watcher that monitors local file system changes. After restart, the watcher detects modifications to the sync database itself and treats them as new changes. Second, SharePoint Online returns metadata updates for large libraries in multiple batches. Each batch arrival triggers a new sync pass. Together, these factors cause the sync client to restart processing repeatedly without reaching a stable completion state.

The problem is most common in libraries with deep folder hierarchies, many small files, or frequent co-authoring activity. Users see the OneDrive icon cycling continuously in the system tray, with the status message “Processing changes” or “Syncing” never transitioning to “Up to date.” CPU usage from the OneDrive.exe process may stay above 20 percent for hours.

Admin Checklist to Stop the Sync Loop

Use the following checklist in order. Each step reduces the likelihood of a restart-triggered sync loop. Apply these settings through Group Policy, Intune, or direct registry edits where indicated.

1. Disable automatic sync for large shared libraries
   Open OneDrive Settings by right-clicking the OneDrive icon in the system tray and selecting Settings. Go to Sync and backup > Manage backup. Under Shared libraries, click Stop sync for any library that exceeds 30,000 items. This prevents OneDrive from automatically syncing that library on restart. Users can manually sync the library later using the OneDrive web interface.
2. Set a maximum library size for automatic sync via Group Policy
   Download the OneDrive Group Policy administrative templates from Microsoft. Navigate to Computer Configuration > Administrative Templates > OneDrive. Enable the policy “Set the maximum size of a SharePoint library to sync automatically.” Set the value to 5000 MB. This forces OneDrive to only auto-sync libraries under 5 GB in total size. Larger libraries require manual sync selection.
3. Delay OneDrive startup after user logon
   Open Registry Editor as Administrator. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run. Locate the OneDrive entry. Set the binary value to delay startup by modifying the associated scheduled task. Alternatively, use Group Policy to configure “Specify the delay in seconds before the OneDrive sync engine starts.” Set a delay of 120 seconds to give system processes time to initialize.
4. Enable Files On-Demand for all users
   In the OneDrive admin center, go to Sync and select the Files On-Demand setting. Enforce Files On-Demand for the entire tenant. This reduces the number of files that OneDrive must process locally after restart. Files appear as online-only placeholders until the user opens them, which cuts the initial sync workload dramatically.
5. Limit the number of shared libraries synced per user
   Use the OneDrive Group Policy “Limit the number of SharePoint sites that can be synced automatically.” Set the value to 5. This prevents users from syncing dozens of shared libraries, which multiplies the restart processing load. Users can still access additional libraries through the browser.
6. Clear the local OneDrive sync cache on affected machines
   Stop OneDrive by right-clicking the system tray icon and selecting Exit. Open File Explorer and navigate to %LocalAppData%\Microsoft\OneDrive. Delete all files in the settings folder except the ClientPolicy and ClientPolicy_backup folders. Restart OneDrive. This forces a fresh sync database rebuild and often breaks existing loops.
7. Monitor sync health with the OneDrive admin center reports
   Go to the Microsoft 365 admin center > Reports > OneDrive. Run the Sync health report for the affected users. Look for devices with high sync error counts or long sync durations. Use this data to identify which libraries or devices need the above policy adjustments.

If the Sync Loop Persists After the Checklist

OneDrive sync loop continues after clearing cache

If clearing the local cache does not stop the loop, the library may have a corrupted sync relationship. Remove the library from OneDrive entirely. Go to OneDrive Settings > Account > Choose folders for each shared library. Uncheck all folders in the problem library and click OK. Wait for OneDrive to remove the local files. Then re-add the library from the web interface. This creates a fresh sync relationship without accumulated change history.

High CPU usage persists even after sync appears idle

Some large libraries cause OneDrive to perform background indexing even when no files are actively syncing. This appears as a sync loop but is actually the search indexer processing file metadata. Open Task Manager and check if Microsoft Windows Search Indexer is using high CPU. If so, exclude the OneDrive sync folder from Windows indexing. Go to Settings > Privacy & security > Searching Windows. Under Excluded folders, add the OneDrive folder path.

Shared library sync fails with error 0x8007016a after restart

This error indicates that the local disk does not support the required file system features for OneDrive sync. The drive must be formatted as NTFS. If the user’s profile is on a FAT32 or exFAT drive, OneDrive cannot track file changes properly, leading to repeated sync attempts. Move the OneDrive folder to an NTFS drive. In OneDrive Settings > Account > Unlink this PC. Relink and choose a folder on an NTFS volume.

Item	Automatic sync of large libraries	Manual sync after restart
Trigger	OneDrive starts sync on user logon	User navigates to library in browser and clicks Sync
Processing load	Full library scan on every restart	Only syncs files the user selects
Risk of sync loop	High for libraries over 30,000 items	Low, because sync is on-demand
User awareness	May not know sync is running	User initiates sync intentionally
Admin control	Group Policy can limit library size	No automatic processing to control

The admin checklist in this article stops the restart-triggered sync loop for large shared libraries by disabling automatic sync, limiting library size, and delaying OneDrive startup. Start with the Group Policy settings to prevent new occurrences. For existing loops, clear the local cache or remove and re-add the affected library. Monitor sync health reports weekly to catch loops early. As an advanced step, configure a startup script that pauses OneDrive for 180 seconds using the command %localappdata%\Microsoft\OneDrive\OneDrive.exe /shutdown followed by a timed restart, which gives the system time to initialize before sync begins.