You restore a project folder from the OneDrive recycle bin or version history, but the files that come back are not the correct versions. This problem occurs when multiple users edit the same folder or when the restore process pulls from a scope that does not match your intended point-in-time. This article explains why OneDrive returns the wrong version during folder-level restore and provides specific steps to recover the correct file versions without losing recent changes.
Key Takeaways: Restoring the Correct Version in Project Folders
- OneDrive web > Recycle bin > Second-stage recycle bin: Files deleted by other users may bypass the first-stage bin and require checking both stages before restore.
- Version history > Restore option on individual files: Folder-level restore does not always pick the version you expect; restore each critical file separately to ensure version accuracy.
- OneDrive > Settings > Account > Restore your OneDrive: This point-in-time restore applies to the entire OneDrive and may overwrite newer files if you do not exclude the current project folder first.
Why OneDrive File Restore Returns the Wrong Version in Project Folders
OneDrive for Business stores version history for each file independently, but folder-level restore operations do not let you pick a specific version for each file. When you restore a folder from the recycle bin, OneDrive restores the most recently deleted version of each file in that folder. If a file was deleted, re-uploaded, and then deleted again, the restore might bring back the second version instead of the first one you actually need.
The same issue occurs with the Restore your OneDrive feature. This feature scans all changes in your OneDrive over the last 30 days and lets you roll back to a specific point in time. However, the restore applies to every file and folder in your OneDrive. If you select a time before a coworker added new files to the project folder, those new files are removed. If you select a time after a coworker deleted important files, those deletions are undone and the old versions return. The result is a folder that contains a mix of versions from different dates rather than a single consistent snapshot.
Another common cause is the two-stage recycle bin. When a user deletes a file from a shared project folder, the file goes to the first-stage recycle bin of the folder owner. If the owner empties that bin, the file moves to the second-stage recycle bin, which is not visible in the regular OneDrive web interface. A restore from the first-stage bin may appear to succeed but actually returns an older version because the most recent deletion was already purged from that bin.
Steps to Identify and Restore the Correct File Version in a Project Folder
Follow these steps in order. Do not skip the inspection step — it prevents you from overwriting the wrong files again.
- Inspect the current state of the project folder
Open OneDrive in your browser. Navigate to the project folder. Compare the file names and last modified dates with the team’s records. Write down which files are missing and which files show the wrong version. This list tells you exactly what needs to be restored. - Check the first-stage recycle bin
In the left navigation pane of OneDrive web, click Recycle bin. Look for files from the project folder. If you see the files you need, right-click each file and select Restore. Do not restore the entire folder at once unless you are certain every file in that folder is the version you want. - Check the second-stage recycle bin
Scroll to the bottom of the recycle bin page and click Second-stage recycle bin. This bin contains files that were deleted from the first-stage bin. Restore individual files the same way. If the second-stage bin is empty, the files may have been permanently deleted by the folder owner or an admin. - Use version history on individual files
Navigate to the file that has the wrong version. Right-click the file and select Version history. A panel opens showing all saved versions with timestamps. Find the version that matches the correct date and content. Click the three dots next to that version and select Restore. This replaces the current file with that exact version without affecting other files in the folder. - Use Restore your OneDrive with a specific date
If multiple files in the project folder are wrong and you know the exact date when they were correct, go to OneDrive settings > Restore your OneDrive. Select a date and time from the activity chart. OneDrive shows a preview of which files will be changed. Before you click Restore, exclude the project folder if any files in it should stay at their current version. To exclude a folder, click Exclude files and select the project folder. Then click Restore. This rolls back only the files that were changed on that date while leaving the excluded folder untouched. - Use the Microsoft 365 admin center for tenant-wide recovery
If you are an admin and the user’s OneDrive recycle bin is empty, go to the Microsoft 365 admin center > Users > Active users. Select the affected user. Click OneDrive > Restore OneDrive. Choose a date and time. This method restores the entire OneDrive to that point. After the restore, the user must re-share any files that were shared externally because sharing links are reset.
If Restoring the Project Folder Still Returns the Wrong Version
Files restored but show an older version than expected
This happens when a file was overwritten multiple times and the restore brought back the second-to-last version instead of the intended one. Use version history on each file individually as described in step 4 above. If the correct version is not listed, check whether the file was moved or renamed. Moving or renaming a file does not preserve its version history in the new location. In that case, ask the team member who moved the file to provide the original version from their own OneDrive recycle bin.
Restore your OneDrive removed files that should have stayed
The Restore your OneDrive feature applies to your entire OneDrive unless you exclude folders. If you did not exclude the project folder, the restore may have deleted files that were added after the restore date. To get those files back, open the recycle bin and restore them individually. Then use version history on the project folder files to bring back the versions you originally wanted. This two-step process avoids losing new work.
Another user’s changes are missing after you restore
OneDrive restore only affects your own OneDrive. If the project folder is shared and another user deleted or changed files, those changes are not reverted by your restore. The other user must perform their own restore or use version history on the files they changed. Coordinate with the team to agree on a single restore point so that everyone restores to the same date.
Recycle Bin vs Version History vs Restore Your OneDrive: Key Differences for Project Folders
| Item | Recycle Bin | Version History | Restore Your OneDrive |
|---|---|---|---|
| Scope | Individual files or folders | One file at a time | Entire OneDrive (with folder exclusions) |
| Version selection | Restores the most recently deleted version | You pick the exact version from a list | Restores all files to a point in time |
| Retention | Files stay 30 days in first-stage bin, 30 more in second-stage | Up to 500 major versions per file | Activity log covers the last 30 days |
| Effect on other files | Only the restored files are affected | Only the selected file is affected | All files in the OneDrive are rolled back unless excluded |
| Best for | Recovering accidentally deleted files quickly | Restoring a specific file to a known good version | Rolling back many files after a bulk error or ransomware attack |
Now you can identify why a folder restore returned the wrong version and apply the correct method for your situation. For project folders with frequent edits, use version history on individual files instead of folder-level restore. To prevent this issue in the future, ask your team to enable OneDrive > Settings > Sync and backup > Advanced settings > Version history and set a retention period longer than 30 days if your organization supports it.