When you restore a OneDrive for Business library to a previous point in time, you may notice that some recently edited or added files are missing from the restored state. This happens because the file restore feature uses version history snapshots, not the live file system. The restore operation may skip files that were modified within the last few minutes before the restore was initiated. This article explains why the restore process can miss recent changes and provides the exact steps to recover those missing files.
Key Takeaways: Restoring OneDrive Files Without Losing Recent Edits
- OneDrive admin center > Restore OneDrive: Restores files to a selected point in time but only includes versions that existed at that exact moment — recent edits made after the restore point are excluded.
- Version history on individual files: After a restore, you can open each file and use Version History to recover edits that were made after the restore point but before the restore was triggered.
- OneDrive recycle bin: Files deleted during a restore move to the recycle bin and can be recovered there for up to 93 days, depending on your tenant settings.
Why OneDrive File Restore Misses Recent Changes
The OneDrive for Business file restore feature works by reverting the entire library to a snapshot from a specific date and time. This snapshot is built from the version history of each file and folder at that exact moment. If a user edited a file or created a new document after the chosen restore point but before the restore operation started, those changes are not part of any snapshot. The restore process does not merge changes — it replaces the current state with the snapshot state.
Another factor is the time delay between when a change is saved and when it is indexed for version history. In most cases, OneDrive saves a new version within a few seconds. However, if the restore is triggered while a file is still being synced or processed, that file may not have a version captured at the restore point. The restore operation then treats that file as if it did not exist at that point in time.
The restore feature also moves any files that were added or changed after the restore point into the recycle bin. These files are not lost — they are simply removed from the restored library view. The same applies to folders that were created after the restore point. The restore operation does not delete these items permanently unless they are manually purged from the recycle bin.
Version History Snapshot Limitations
The restore point you select must be at least 30 minutes in the past. OneDrive cannot restore to a point within the last 30 minutes because version snapshots are not created continuously. This means any changes made in the last 30 minutes before the restore are automatically excluded from the restored state. Users who edit files right before a restore will always see those edits missing afterward.
Co-Authoring and Real-Time Edits
When multiple users edit the same file simultaneously, OneDrive saves separate versions for each save action. If a restore is triggered during active co-authoring, some user saves may not be captured as distinct versions. The restore point may include only the last fully saved version before the co-authoring session started. The missing edits are still present in the file’s version history but are not reflected in the restored library.
Steps to Recover Files Missing After a OneDrive Restore
Follow these steps to recover files and changes that were missed during the restore operation. Perform these steps immediately after the restore completes to avoid permanent data loss.
- Check the OneDrive Recycle Bin
Open your OneDrive library in a web browser. On the left navigation pane, click Recycle bin. Sort by Deleted Date to find files that were moved during the restore. These are files created or edited after the restore point. Select the files you need and click Restore. The files reappear in their original locations in the restored library. - Review Version History for Each Missing File
Navigate to the folder where the file was originally located. Right-click the file and select Version history. A pane opens listing all saved versions. Look for versions dated after the restore point but before the restore started. Click the three dots next to that version and select Restore. This brings back the recent edits without undoing the entire library restore. - Use OneDrive Sync Client to Recover Local Copies
If you have the OneDrive sync client running on your computer, open File Explorer and go to the OneDrive folder. Check if the missing files are still present locally under the original folder structure. If the sync client has not yet processed the restore, local copies may still contain the recent changes. Copy those files to a safe location outside the OneDrive folder, then let the sync client finish restoring. After the sync completes, paste the copies back into the OneDrive folder. The sync client uploads them as new versions. - Search the Second-Stage Recycle Bin
If you do not find the files in the standard recycle bin, click the link at the bottom of the recycle bin labeled Second-stage recycle bin. This holds items deleted by the restore that are older than 30 days or that were already in the first-stage bin. Restore any files you find there. - Contact Your Microsoft 365 Administrator
If the files are not recoverable through the previous steps, ask your admin to check the audit log in the Microsoft 365 admin center. The audit log records all file modifications, deletions, and restores. Your admin can identify the exact time of the restore and which files were affected. They can also use the eDiscovery tools to recover files from backups if retention policies allow.
If the Restore Still Misses Recent Changes
Files were deleted during restore and are not in recycle bin
This can happen if the files were already in the recycle bin before the restore started. The restore operation does not move items that are already deleted — it only moves items that exist in the library at the time of the restore. To recover these files, use the Version History method described above for the parent folder. Right-click the parent folder, select Version history, and restore a version of the folder from before the restore. This brings back the folder’s contents, including files that were deleted before the restore.
OneDrive sync client shows errors after restore
After a restore, the sync client may display sync errors for files that were moved or deleted. These errors appear because the local copy no longer matches the server state. To fix this, pause and resume syncing. Right-click the OneDrive icon in the system tray, select Pause syncing, choose 2 hours, then right-click again and select Resume syncing. The sync client re-evaluates the file list and resolves conflicts automatically.
Version history shows the edit but restore does not work
If you can see the version in the history but the Restore button is grayed out, the version may be corrupted or the file may be checked out. Ask the user who last edited the file to check it in. After the file is checked in, the Restore button becomes active. If the user is unavailable, an admin can force-check-in the file through the SharePoint admin center.
OneDrive File Restore vs Manual Version Restore: Key Differences
| Item | OneDrive File Restore | Manual Version Restore |
|---|---|---|
| Scope | Entire OneDrive library | Single file or folder |
| Time required | Minutes to hours depending on library size | Seconds per file |
| Recent change handling | Moves recent changes to recycle bin | Does not affect other files |
| Undo capability | Can be reversed by running another restore | Each version restore is permanent unless you revert again |
| Impact on co-authoring | Disrupts all active editing sessions | Only affects the file being restored |
You can now recover files that were missed during a OneDrive file restore by using the recycle bin, version history, and local sync copies. After completing the recovery steps, verify that all critical files are present by comparing the file count in the library before and after the restore. To avoid missing changes in future restores, schedule restores during low-activity periods and inform users to save and close all files 30 minutes before the restore time. As an advanced tip, use the Microsoft 365 admin center audit log to generate a report of all file modifications made in the 30 minutes before the restore — this gives you a definitive list of files that need manual recovery.