OneDrive recovery limits

A OneDrive filename with a cloud icon may be a placeholder—not proof that the file's content exists on the computer.

Files On-Demand can show names and metadata for online-only content without storing the file bytes locally. Locally available and always-available files have downloaded content, while unsynced changes, conflicts, deletion, account loss, or disk failure create different recovery paths.

Understand the symptom

Cloud namespace, local placeholder metadata, and hydrated file content are separate layers.

WHY

What is happening

Microsoft documents that online-only files use no local content space and download when opened. A blue cloud entry may therefore provide a name without recoverable file bytes on the disk; green status indicates locally available content.

What you may see

Symptoms that change the recovery path.

01

Blue cloud file will not open

The placeholder needs cloud access and may have no local content.

02

Red X or sync conflict

A local or cloud change failed to reconcile.

03

Folder exists after account removal

Names may remain while hydration and permissions no longer work.

04

Recent edits appear on one device only

Changes may be unsynced and recoverable from that endpoint.

Protect the source

Actions that can make the situation worse.

01

Reset can discard sync diagnostics

Logs and local state help distinguish cloud-only from unsynced content.

02

Free up space removes local content

A hydrated file can become online-only.

03

New sync can propagate deletion

Reconnect only after preserving every endpoint and cloud recycle state.

Do this now

Safe steps before evaluation.

01

Record status before changes

Capture icons, errors, account, path, dates, and affected filenames.

02

Preserve the full local folder

Copy local data and metadata without forcing hydration or cleanup.

03

Check authorized cloud sources

Review OneDrive web, recycle bin, version history, retention, and shared libraries.

04

Isolate unsynced devices

Keep other computers offline until their local changes are preserved.

NEPFOSYS process

How a data-first evaluation proceeds.

01

State classification

NEPFOSYS separates online-only placeholders, hydrated files, unsynced changes, conflicts, and deleted items.

02

Endpoint preservation

Readable local content, caches, logs, and alternate device copies are collected safely.

03

File validation

Recovered files are checked for content, size, timestamps, versions, and expected application readability.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can an online-only placeholder be recovered from the SSD?

Usually not if its content was never downloaded; cloud or another endpoint is the relevant source.

Does a filename prove the file exists?

No. Placeholder metadata can remain without local content bytes.

Should I unlink and relink OneDrive?

Not before preserving local and cloud state, especially when unsynced work may exist.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case