When a OneDrive file disappears from Windows, establish whether it was moved, deleted, made online-only or affected by a different sign-in or paused synchronization. Check the actual account online before treating the local folder as the only source. A missing local file is not proof that the cloud copy was deleted.
Compare the local path and online account
Record the expected Windows path and account. Check whether you are viewing another user profile, another OneDrive account or a folder that is no longer selected for synchronization. Search the service’s web view and relevant shared locations for the required item.
Do not unlink accounts, delete synchronized folders or repeatedly move files to force a repair before understanding the current state. A local action can affect the synchronized content. Preserve independent useful copies and coordinate managed-account changes with the administrator.
Understand the availability state
Microsoft’s Files On-Demand documentation distinguishes online-only content from locally available copies. A file can be listed without all of its content being present on the device. In File Explorer, inspect the Status column: a blue cloud marks an online-only item, an outlined green check marks a locally available item, and a solid green circle with a white check marks an item kept on the device. Microsoft explains these icons. These are current availability indicators, not proof of the file’s complete storage history. Check whether the account can open the online item.
If the cloud item is available, obtain a full authorized copy through the normal service controls and verify it. Downloading current content is not the same as recovering an older deleted version. If the cloud item is missing, inspect the account’s recycle bin and available history under its applicable conditions.
Decide whether local recovery applies
If the file remains readable in OneDrive, you can obtain it through the service or use XRecovery’s authorized OneDrive connection. If a complete file existed on the Windows disk and was later deleted, XRecovery’s local scan may find remaining data; ordinary scanning and supported original-file preview are free. It cannot recreate cloud-only bytes merely from a placeholder name. Treat any cached preview separately from the full original.
If a local recovery attempt is appropriate, reduce unnecessary source writes and export to another device. Identify the actual source disk rather than assuming a current synchronized folder path tells the entire history. If the device is unstable, assess that condition before continued scanning.
Verify the content, not just synchronization
Open the retrieved file and inspect the required version. Check project dependencies and complete media where applicable. A healthy synchronization indicator does not prove that the selected file contains the missing work.
Keep a note of the account, original and current paths, availability state and recovery route. If the mismatch remains unresolved, provide these details to the appropriate support contact with credentials removed. Preserve a verified independent copy before reorganizing synchronization, so that a later change does not become another only-copy incident.
For the next step, see Recover Cloud Files: Separate Account History from Local Copies.