Everyday IT · SharePoint & OneDrive

Make sure you are fixing the real sync path.

A folder in File Explorer may be a SharePoint library sync, a OneDrive shortcut, an old disconnected folder, or a local copy.Browser first. Identify the path. Then repair only the broken sync relationship.

The practical sync path

Do not unlink or delete folders until you know what they represent.

01

Verify the library online

Open the expected SharePoint site in the browser. Confirm the library and folders exist and that the user can open them.

02

Identify shortcut versus Sync

Check whether the user added a OneDrive shortcut or used SharePoint's Sync action. Those are different relationships and can create confusing duplicates when mixed.

03

Check OneDrive state

Confirm the correct work account is signed in, OneDrive is running, and there are no unresolved sync errors or paused operations.

04

Let large changes finish

Large libraries can take hours to reconcile. If the change count is falling, avoid creating a second sync relationship while the first one is still processing.

When a clean re-sync is justified

Use a rebuild only after the cloud copy is verified and the local relationship is clearly wrong.

Known issue

Old shortcut is pointing at the wrong thing

Remove the incorrect cloud shortcut first, then start the intended SharePoint library sync from the actual site.

Known issue

Disconnected local folders remain

Old File Explorer entries can survive after unlinking. Confirm they are no longer active sync locations before removing local remnants.

Known-good signal

“Use the existing folder” appears

When the intended SharePoint Sync process recognizes the matching local folder, it can indicate the correct library relationship is being re-established.

Verify

Check cloud and local again

Confirm the expected folders populate in File Explorer and that OneDrive eventually reports a healthy, current state.

Do not create a second sync problem while the first one is still finishing.