OneDrive Admin Checklist: shared library sync loops after restart for managed Windows PCs
🔍 WiseChecker

OneDrive Admin Checklist: shared library sync loops after restart for managed Windows PCs

When managed Windows PCs restart, users may see OneDrive enter a sync loop for shared libraries. The sync icon spins continuously, files fail to sync, and the OneDrive process consumes high CPU. This problem occurs because the OneDrive sync engine reinitializes its connection to each shared library during startup, and a misconfigured policy, stale token, or network delay prevents the handshake from completing. This article provides an admin checklist to identify and resolve the root cause of shared library sync loops after a restart.

Key Takeaways: Shared Library Sync Loop Admin Checklist

  • Group Policy: Computer Configuration > Administrative Templates > OneDrive > Sync settings: Controls whether shared libraries sync automatically; disabling auto-sync for all shared libraries breaks the loop.
  • OneDrive Known Folder Move policy: If enabled, verify that the policy points to a valid SharePoint site URL and that the user has permissions on the target library.
  • Windows Credential Manager > Windows Credentials > OneDrive Cached Credentials: Clearing stale cached tokens for OneDrive forces a fresh authentication on next sign-in.

ADVERTISEMENT

Why Shared Library Sync Loops Occur After Restart

When a Windows PC restarts, OneDrive reinitializes all sync relationships. For shared libraries, the sync engine must authenticate the user, verify permissions on the SharePoint site, and download the file metadata. If any step fails or times out, OneDrive retries the sync immediately, creating a loop. The most common triggers are:

  • Stale authentication tokens that require re-sign-in but the user is already logged in with cached credentials.
  • Network connectivity changes during boot — the sync engine starts before the network stack is fully ready.
  • Group Policy settings that disable or restrict shared library sync for the tenant, causing OneDrive to repeatedly attempt and fail.
  • Large shared libraries with millions of items that exceed the sync engine scan time, causing a timeout and retry.

In managed environments, group policy misconfigurations are the leading cause. The following checklist addresses each layer.

Admin Checklist: Diagnose and Fix the Sync Loop

Step 1: Verify OneDrive Group Policy Settings

  1. Open the Group Policy Management Console
    On a domain controller or management workstation, open GPMC.msc. Locate the GPO applied to the affected computers.
  2. Navigate to OneDrive policies
    Go to Computer Configuration > Administrative Templates > OneDrive > Sync settings. Confirm the following values:
    – “Prevent users from syncing personal OneDrive accounts” — set to Enabled.
    – “Silently sign in users to the OneDrive sync app with their Windows credentials” — set to Enabled.
    – “Use OneDrive Files On-Demand” — set to Enabled (recommended).
  3. Check the “Shared libraries” policy
    Find “Prevent users from syncing files and folders on this PC to other PCs” — this should be Not Configured or Disabled. If Enabled, shared library sync is blocked entirely, causing the loop on startup.
  4. Run gpupdate /force on a test machine
    Open an elevated Command Prompt and run gpupdate /force. Restart the machine and observe the sync behavior.

Step 2: Clear Stored Credentials for OneDrive

  1. Open Credential Manager
    Press Win+R, type control keymgr.dll, and press Enter.
  2. Locate OneDrive entries
    Click Windows Credentials. Look for entries that contain “OneDrive” or “MicrosoftOffice16” in the name. Common names include:
    MicrosoftOffice16_Data:ADAL:...
    OneDrive Cached Credential
  3. Remove each entry
    Click the arrow next to the entry, then Remove. Confirm the deletion. Remove all OneDrive-related credentials.
  4. Restart OneDrive
    Right-click the OneDrive icon in the system tray and select Close OneDrive. Restart OneDrive from the Start menu. Sign in again and check the shared library sync status.

Step 3: Disable Shared Library Auto-Sync via Registry (Temporary Fix)

If the loop persists and you need immediate relief for all managed PCs, disable shared library auto-sync through a registry setting. This prevents OneDrive from trying to sync shared libraries at startup.

  1. Open Registry Editor
    Press Win+R, type regedit, and press Enter.
  2. Navigate to the OneDrive key
    Go to HKEY_CURRENT_USER\Software\Microsoft\OneDrive\Accounts\Business1. If the key does not exist, create it.
  3. Create a DWORD value
    Right-click in the right pane, select New > DWORD (32-bit) Value. Name it DisableSharedLibrarySync. Set the value to 1.
  4. Restart OneDrive
    Close and restart OneDrive. Shared libraries will no longer sync automatically. Users must manually sync them by opening the SharePoint site in a browser and clicking Sync.

Step 4: Check Network Connectivity and Proxy Settings

  1. Test connectivity to OneDrive endpoints
    From the affected PC, open a browser and navigate to https://portal.office.com. If the page loads, basic connectivity works. Then test https://sync.live.com — the sync endpoint.
  2. Verify proxy configuration
    Open Internet Options > Connections > LAN settings. If a proxy is configured, ensure it does not block sharepoint.com and all subdomains. OneDrive sync requires direct access to SharePoint domains.
  3. Disable IPv6 temporarily
    Open Network and Sharing Center > Change adapter settings. Right-click your network adapter, select Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6). Restart the PC. If the sync loop stops, IPv6 misconfiguration is the cause. Re-enable IPv6 after confirming.

ADVERTISEMENT

If the Shared Library Sync Loop Still Occurs

OneDrive Sync App Version Is Outdated

An outdated OneDrive sync app may have bugs that cause sync loops. Verify the version on the affected PC. Right-click the OneDrive icon in the system tray, select Settings, go to the About tab, and note the version. Compare with the latest production version listed in the Microsoft 365 admin center. If outdated, update through Windows Update or by downloading the latest OneDrive installer from https://www.microsoft.com/en-us/microsoft-365/onedrive/download.

Shared Library Contains Over 300,000 Items

OneDrive sync has a known limitation: libraries with more than 300,000 items may cause sync loops on restart because the sync engine exceeds its metadata scan time. To confirm, check the library item count in SharePoint admin center. If the count exceeds the limit, archive old files to a separate library or use a migration tool to split the library.

User License or Site Permissions Are Inconsistent

If the user’s SharePoint site permissions were modified while the PC was offline, the sync engine may fail to validate access. Verify the user’s license in the Microsoft 365 admin center: go to Users > Active Users, select the user, and confirm they have a SharePoint Online license assigned. Then check site permissions: navigate to the shared library in a browser, click the gear icon > Site permissions, and confirm the user is a member of the appropriate group (Members or Owners).

Shared Library Sync Loop vs. Personal OneDrive Sync Loop: Key Differences

Item Shared Library Sync Loop Personal OneDrive Sync Loop
Root cause Group policy, stale SharePoint token, or library size limit Corrupted local cache, file name conflicts, or large file size
Primary fix Clear Credential Manager entries or disable auto-sync via registry Reset OneDrive sync app (run onedrive.exe /reset)
Affected users Managed PCs with group policy applied Any user, managed or unmanaged
Diagnostic tool Group Policy Result (GPResult) or RSOP snap-in OneDrive sync activity center or sync log

After following the admin checklist, you can identify whether the loop is caused by a policy misconfiguration, stale credentials, or a library size issue. Start with the group policy verification and credential clearing. If the loop continues, disable shared library auto-sync temporarily using the registry setting. For large libraries, consider archiving old content. The registry setting DisableSharedLibrarySync gives immediate relief while you investigate the root cause.

ADVERTISEMENT