Technical Case · KT-000004

SharePoint Worked in the Browser but File Explorer Was Incomplete

The user could open the correct SharePoint library online, but File Explorer showed only part of what should have been there.The browser proved cloud access. The failing layer was the local OneDrive relationship.

Documented by Published

Case ID

KT-000004

Category

SharePoint / OneDrive

Status

Resolved

Technologies

SharePoint Online / OneDrive / File Explorer

Problem

What happened?

A SharePoint document library worked correctly in the browser, but the user's File Explorer view was incomplete. Files and folders expected from the cloud library were missing locally.

Because the exact library was available online, the investigation did not begin by changing SharePoint permissions. The browser result was used as the known-good checkpoint.

Public-safe context

What was removed?

Customer identity

Organization and user names are omitted.

Tenant details

Site, library, folder, and tenant names are generalized.

File contents

No customer documents, filenames, credentials, or private paths are published.

Technical sequence

The real troubleshooting sequence and resolution pattern are preserved.

Symptoms

What did the technician know?

Known good

The exact library worked online

The user could reach the intended SharePoint content in the browser.

Still broken

File Explorer was incomplete

The local folder did not represent the full library the user could see online.

Important clue

A pre-existing OneDrive relationship was already present

The local path was not assumed to be the same thing as the active SharePoint library sync.

Investigation

How was the problem narrowed?

Step 1

Use the browser as the source of truth

Confirm the same files and folders existed in SharePoint Online. That proved the user's cloud access and shifted attention to the workstation-side sync path.

Step 2

Identify what File Explorer was actually showing

Determine whether the local entry was a real SharePoint library sync, a OneDrive shortcut, or an older stale relationship.

Step 3

Find the conflicting relationship

A pre-existing OneDrive shortcut conflicted with the intended library sync and left File Explorer showing incomplete contents.

Step 4

Remove the stale relationship and establish the intended sync

The stale link was removed, then sync was started from the correct SharePoint library so one intentional relationship represented the cloud content locally.

Step 5

Allow the local view to converge before judging the result

Large sync activity can produce temporary duplicate or incomplete-looking folders. The local client was allowed to finish before the final verification.

What We Tried

Do not create another sync relationship just because one looks wrong.

The local folder name was not enough evidence

A File Explorer entry can look like the intended SharePoint library while actually being a shortcut, stale relationship, or disconnected local remnant.

The useful move was to identify the relationship type before changing or adding another sync path.

Root Cause

What was actually wrong?

The local OneDrive relationship did not match the intended SharePoint sync

A pre-existing OneDrive shortcut conflicted with the real library sync. The browser copy was healthy, but File Explorer was representing the wrong local relationship and therefore showed incomplete content.

Resolution

How was service restored?

The stale shortcut relationship was removed and the intended SharePoint library was synced from the correct cloud location.

After the new relationship completed its initial synchronization, File Explorer represented the expected library content again.

Verification

Compare the intended SharePoint library in the browser with File Explorer and confirm the expected folders and files appear locally.

Then verify the local relationship is the intended sync path and allow pending changes to finish before declaring the repair complete.

Lessons Learned

When the browser works, stop troubleshooting the wrong layer.

If the exact content works in the browser, use that as the known-good source and isolate the local sync relationship.

The case was resolved by separating cloud access from local presentation, identifying the relationship type, and rebuilding only the broken local relationship instead of changing permissions or layering another sync on top.

Related Resources

Turn the case into a repeatable method.

Broad authority

SharePoint & OneDrive

Start here when the failure layer between access and sync is not yet known.