01 · Cloud
Prove the exact content works online
Open the intended site, library, folder, or file in the browser with the user's normal work account. Confirm the user can see and use the actual resource, not just the SharePoint home page.
Everyday IT · SharePoint & OneDrive
Browser works. File Explorer does not. That difference is useful evidence.
If the user can open the same SharePoint or OneDrive content in the browser, cloud access is already partly proven.Do not restart with permissions. Move to the local sync path.
Use the browser as your known-good checkpoint
The browser result tells you where not to start.
02 · Account
Confirm OneDrive is using the same identity
Check which work account the OneDrive client is signed into. A browser session and a local sync client can be using different identities without the user realizing it.
03 · Relationship
Identify how the content reached File Explorer
Determine whether the item is a SharePoint library sync, a OneDrive shortcut, a stale disconnected folder, or a local copy. Do not repair a path you have not identified.
04 · State
Read the client before changing it
Look for paused sync, credential prompts, sync errors, large pending changes, storage issues, or a client that is not running. Capture the state before resetting anything.
05 · Local path
Compare what exists online with what File Explorer shows
Check whether the local entry is missing, stale, duplicated, pointing to an old location, or showing only part of the library. The mismatch itself helps identify the broken relationship.
06 · Next test
Choose the smallest safe action
Resume, sign in, correct the intended sync relationship, or let pending changes finish before considering unlink, reset, or a clean re-sync.
Browser → Account → Relationship → Client state → Local path → Next test.
When browser access works, treat the cloud copy as the known-good source and isolate the workstation-side path.
What common result patterns mean
Each comparison narrows the failure.
Browser works, OneDrive is signed out
This is client identity state
Restore the intended work account in the OneDrive client before touching SharePoint permissions or recreating folders.
Browser works, OneDrive is healthy, folder is missing
Inspect the sync relationship
The library may no longer be synced, a shortcut may have been removed, or the local relationship may be disconnected even though cloud access is healthy.
Browser works, duplicate folders appear
Do not guess which one is current
Identify shortcut versus Sync, compare paths and status, and determine which relationship is active before removing anything.
Browser works, local changes are pending
Protect unsynced work first
Do not unlink or delete the local folder until you know whether files are still waiting to upload or exist only on the workstation.
Browser works for one user, not another
Return to access and scope
If the browser comparison differs between users, the problem may still be permissions, group membership, account state, or the exact resource rather than local sync.
Browser works everywhere, several PCs fail locally
Look for a shared client or policy issue
Compare OneDrive version, account state, Windows policy, endpoint configuration, and recent changes before rebuilding each workstation independently.
When repair becomes a rebuild
A re-sync can be appropriate, but only after you know what is safe to discard and what must be preserved.
Before unlinking
Prove the cloud copy is complete
Verify the expected files and recent changes online. If the browser does not contain the user's latest work, stop and protect the local copy first.
Before deleting remnants
Prove the folder is no longer an active sync location
Old File Explorer folders can look disposable while still containing local-only data. Confirm the relationship is disconnected and the data is represented elsewhere.
Before creating a new relationship
Know whether the user used Sync or Add shortcut to OneDrive
Mixing methods can create duplicate paths and user confusion. Re-establish one intentional relationship instead of layering another on top.
After repair
Verify the user's real workflow
Open the expected folder in File Explorer, confirm current files appear, create or modify a safe test item if appropriate, and verify it reaches the cloud.
What not to do
Browser-working cases are easy to make worse with broad changes.
Avoid
Changing permissions because File Explorer is broken
If the exact content works online for the same user, permissions are not the first place to spend effort.
Avoid
Unlinking OneDrive as the first diagnostic step
Unlinking changes the environment and can obscure pending-sync evidence before you understand the failure.
Avoid
Deleting duplicate folders based on names alone
Determine which path is active, cloud-backed, shortcut-based, or stale before removing local content.
Escalate
When policy, tenant configuration, or business-critical data is involved
Pause when the fix requires broad OneDrive policy changes, tenant-wide configuration, large library restructuring, unclear data preservation, or privileged administrative changes.
Next Test
Move into the specific branch only after the broad comparison has narrowed the layer.
Relationship is wrong
Shortcut, Sync, or stale folder needs repair
Use the sync-specific guide to rebuild only the broken relationship after protecting pending work. Troubleshoot the sync relationship
One variable differs
Use a known-good comparison
Compare user, device, account, library, and path one dimension at a time. Use a known-good comparison
Reset is proposed
Protect data and define rollback first
Document what can be lost, what is verified online, and how success will be measured before unlinking or rebuilding. Plan the change safely