Your team restores a file from OneDrive for Business but gets an older or incorrect version. This problem often happens when multiple users edit a file at the same time and the restore point selected does not match the intended version. The OneDrive restore feature works on the entire file history, not individual edits, so picking the wrong point in time can roll back changes from other users. This article explains why the restore returns the wrong version and gives precise steps to identify and select the correct restore point.
Key Takeaways: Restoring the Correct File Version in OneDrive for Business
- Version History in OneDrive web app: Right-click a file and select Version history to see all saved versions before performing a restore.
- Restore point selection in the Restore dialog: Use the date/time picker to choose a specific moment, not a broad range, to avoid including unwanted edits.
- SharePoint Admin Center > Restore settings: Adjust the default retention period and restore window for large teams to prevent truncated history.
Why OneDrive Restores the Wrong Version for Team Files
OneDrive for Business stores file versions based on save events. When a team member saves a document, OneDrive creates a new version. The Restore feature lets you roll back a file to any version within the retention period. The problem occurs when you select a restore point that does not align with the specific edit you need. For example, if three people edited a file between 10:00 AM and 10:05 AM, and you restore to 10:03 AM, you get the version from that moment, which may include edits from two users but not the third. The restore does not merge changes; it replaces the current file entirely with the chosen version. Large teams with overlapping edits are most affected because the version list can be long and confusing.
Another root cause is the default retention period. OneDrive for Business keeps file versions for 30 days unless an admin increases it. If a team needs to restore a version older than 30 days, the restore may fail silently or return the oldest available version, which could be the wrong one. The OneDrive sync client also caches versions locally, so if a team member restores from their local sync folder instead of the web app, they might get a stale cache copy rather than the true server version.
Version History vs Restore Points
Version History shows every saved version with a timestamp and the user who saved it. A restore point is the exact moment you select during the restore process. If you choose a restore point that falls between two saves, OneDrive picks the version that was active at that time. This is not always the version you want. Large teams should always review Version History before initiating a restore.
Steps to Identify and Restore the Correct Version
- Open the file in the OneDrive web app
Go to onedrive.com, sign in with your work account, and navigate to the file that was restored incorrectly. Do not use the local sync folder for this step. - View Version History
Right-click the file and select Version history. A pane opens listing all saved versions with timestamps and the user who made each save. Note the exact timestamp and user for the version you need. - Open and verify the target version
Click the three dots next to a version and select Open file. This opens a read-only copy in your browser. Confirm it contains the correct content. If it does not, check earlier or later versions until you find the right one. - Restore the correct version
After identifying the correct version, click the three dots again and select Restore. A confirmation dialog appears. Click Restore again to apply. The file now shows the chosen version as the current one. - Check audit logs for large teams
If you cannot identify the correct version by browsing, ask a SharePoint admin to check audit logs. Go to Microsoft 365 admin center > Audit > Search. Filter by the file name and date range. Look for File modified events to see which user made each change.
Restoring a File That Was Deleted and Replaced
If a team member deleted the file and uploaded a new one with the same name, OneDrive treats the new file as a separate item. Version History for the original file is lost. To restore the original, go to the OneDrive Recycle bin, find the deleted file, and select Restore. Then compare the two files manually.
If the Restore Still Returns the Wrong Version
OneDrive Restore Feature Returns a Blank or Corrupted File
A blank file after restore usually means the version you selected was never fully saved. This can happen if the user closed the file while an auto-save was in progress. Check Version History for the version immediately before or after the blank one. If the file is corrupted, use the Open in app option from Version History to open it in the desktop version of Word, Excel, or PowerPoint and use the application’s built-in repair tool.
Restore Window Shows No Versions for a File That Was Edited
This occurs when the file version retention period has expired. By default, OneDrive for Business keeps versions for 30 days. If the file was edited 31 days ago, those versions are gone. A SharePoint admin can increase the retention period in the SharePoint Admin Center under Settings > OneDrive > Storage limits and retention. Set Retain versions for to a higher number, up to 100 days. Note that this change applies to all users in the tenant.
Multiple Users Restore the Same File and Create Conflicting Versions
When two team members restore the same file at nearly the same time, OneDrive processes each restore as a separate save. The last restore overwrites the previous one. To prevent this, coordinate restores with your team. Use a shared communication channel or a temporary file lock. In the OneDrive web app, you can check the Info pane to see who has the file open.
| Item | Version History Method | Audit Log Method |
|---|---|---|
| Description | Shows all saved versions with timestamps and user names | Records every file modification event with details |
| Access | Right-click file > Version history | Microsoft 365 admin center > Audit > Search |
| Best for | Identifying the exact version to restore | Tracing who made changes when Version History is incomplete |
| Retention | 30 days by default, configurable up to 100 days | 90 days by default with audit log retention policy |
Both methods are available to users with at least read permissions on the file. Audit logs require an admin role or audit log search permissions.
You can now identify the correct version using Version History or audit logs and restore it without overwriting other team members’ work. Next, ask your SharePoint admin to extend the version retention period to 100 days so older versions remain available. For frequently edited files, instruct your team to use the Check out feature in the OneDrive web app to prevent overlapping saves during critical edits.