OneDrive for Business file restore troubleshooting for document cleanup: restores the wrong version

OneDrive for Business includes a file restore feature that lets you roll back files to a previous state. However, during a document cleanup operation, the restore may return a version that does not match what you expected. This mismatch typically occurs because the restore point selected does not correspond to the actual file state before the cleanup began. This article explains why OneDrive restores the wrong version after a cleanup event and provides the steps to identify the correct restore point and fix the issue.

Why OneDrive Restores the Wrong Version After a Document Cleanup

When you use the OneDrive file restore feature, the system rolls back all files in a folder or site to a specific point in time. The restore point is based on the file state as it existed at that timestamp. If you performed a document cleanup that deleted old versions, the restore may jump to the nearest version that still exists in the version history. This is not a bug — it is the expected behavior when version pruning has removed the exact version you need.

Document cleanup operations often involve deleting old file versions to free storage space. When you run a cleanup, OneDrive removes versions that are older than a retention threshold you set. Later, when you attempt a restore, the system cannot go back to a version that no longer exists. Instead, it restores the next available version, which may be newer than the one you wanted.

Another cause is the restore scope. The file restore feature works at the folder or library level. If you select a restore point that is too broad, it may apply to many files at once. A single file inside that scope might have had its own independent version history that diverged from the folder-level state. The restore will apply the folder-level version, not the file-level version you expected.

Steps to Identify the Correct Restore Point and Recover the Intended Version

To fix a restore that returns the wrong version, you must first determine the exact timestamp of the file version you need. Then, perform a targeted restore using either the file version history or a granular restore point.

Check the Version History of the Affected File

1. Open the file in OneDrive on the web
   Sign in to https://onedrive.live.com and navigate to the file that was restored incorrectly. Right-click the file and select Version history from the context menu.
2. Identify the correct version
   The version history pane lists every saved version with a timestamp and the user who made the change. Scroll through the list and locate the version that matches the state before your cleanup operation. Note the exact date and time displayed next to that version.
3. Restore the specific version
   Click the three dots (ellipsis) next to the correct version and select Restore. This action restores only that file to that version without affecting any other files in the folder.

Use the File Restore Feature with a Precise Restore Point

If multiple files need restoration, use the file restore feature with a carefully chosen point. Do not rely on the suggested restore points — create a custom one.

1. Open the OneDrive recycle bin and version history logs
   Go to the OneDrive web interface and click Recycle bin in the left navigation pane. Check the recycle bin for any files that were deleted during cleanup. Also, open the Activity log from the gear icon to see the exact times when files were modified or deleted.
2. Calculate the correct restore point
   Find the timestamp of the last version you want to keep. This should be a time before the cleanup started. For example, if the cleanup ran at 3:00 PM on March 10, choose a restore point of 2:55 PM on March 10.
3. Run a custom file restore
   In the OneDrive web interface, click the gear icon and select Settings > Restore your OneDrive. Click Choose a different date and enter the timestamp you calculated. Click Restore and confirm the operation. OneDrive will roll back all files in the folder to that exact point in time.

If OneDrive Still Restores the Wrong Version After These Steps

OneDrive version history shows the version I want, but the restore skips it

This usually means the version you see in the history pane was deleted from the server-side version store during the cleanup. The version history pane may cache metadata even after the actual version data is removed. To confirm, try downloading the version instead of restoring it. If the download fails, that version is no longer available. In that case, you must recover the file from a backup or ask your IT admin to check the Microsoft 365 retention policies.

The file restore feature restores files that were not modified during cleanup

The file restore feature applies to all files in the selected folder or library. If you only wanted to restore one file, do not use the folder-level restore. Instead, use the version history method described above. For a library with many files, consider using a library-level restore but exclude folders that do not need changes.

OneDrive restore completes successfully but the file content is still wrong

This can happen if the file was opened and saved by another user after the restore point but before the restore operation. The restore will overwrite the file to the point you selected, but co-authoring or sync conflicts may reintroduce changes. After the restore, lock the file by sharing it with Can view permission only. Then check the version history again to ensure no new versions were created after the restore.

File Version History vs Folder-Level Restore: Key Differences for Document Cleanup

Item	File Version History	Folder-Level Restore
Scope	Single file only	All files in the folder or library
Granularity	Restores one specific version of one file	Restores all files to a single point in time
Best for	Recovering a single file after cleanup	Rolling back an entire folder after bulk cleanup
Impact on other files	None — only the selected file changes	All files in the scope revert to the restore point
Version pruning effect	Skips deleted versions — restores the nearest surviving version	Skips deleted versions — restores the nearest surviving version for each file

After a document cleanup, use file version history when you need to recover a single file. Use folder-level restore only when you are certain that all files in the folder should return to the same point. Verify the restore point timestamp against the cleanup log to avoid restoring the wrong version.