When you are looking for Excel AutoSave failures, the first clue is usually not the Recent list. It is the gap between the last edit, the app's recovery folder, and any cloud draft that existed before the next save. Work from copies so a promising workbook can be tested without changing the source.
First move: For Excel AutoSave failures, close replacement drafts and copy every workbook candidate into a labeled holding folder before opening it.
Protect the clues before clicking
Stop creating new versions for a moment. Close any replacement file with the same name, leave Trash or Recycle Bin alone, and avoid cleanup tools. If the file matters, capture the error message and write down the last device, app, folder, and edit time.
The note gives the recovery a direction. If the app crashed, start with recovery folders. If a cloud file changed, check web history. If the file is damaged, preserve the original before every repair attempt.
Check the places that still keep versions
Check the most likely owner of the newest copy first, then widen the search. For this case, start with:
File > Info > Manage Workbook > Recover Unsaved WorkbooksFile > Info > Version Historyfor OneDrive or SharePoint workbooks- Excel AutoRecover location from
File > Options > Save - Copy workbook candidates before enabling repair or recalculation
Before opening a candidate, duplicate it and add the source to the filename. That small label prevents a confusing pile of almost-identical documents.
Move candidates into a safe folder
- Sort candidates by modified time, then by file size.
- Copy each likely file into the holding folder.
- Open copies read-only when the app allows it.
- Compare the first page, the last edited section, and any formulas, comments, or images that matter.
- Restore only after the best copy is clear.
You are protecting against the second mistake. The first loss already happened; the avoidable loss is saving, restoring, or syncing over the best remaining clue.
The recovery path I would use here
For Office files, start with the built-in recovery trail before creating another version. Check the app recovery picker, AutoRecover path, and browser-based version history before trusting a synced desktop folder.
If time is tight, do the reversible part first: copy the current file or folder, open the web version if a cloud service is involved, and download a candidate instead of restoring over the live copy.
A real-world recovery pass
A laptop restarts after a long editing session. The user opens Office, sees no useful Recent entry, and almost starts a new workbook with the same name. The safer sequence is to close the replacement, make a recovery-candidates folder, check the recovery picker, then copy any .asd, .tmp, or cloud draft before opening it. If one candidate has the last paragraph and another has the formatting, both copies are preserved for comparison.
Quick triage table
| What you see | Best first check | Risk to avoid |
|---|---|---|
| The app crashed before a save | AutoRecover, unsaved files, and temp locations | Reopening and saving a blank replacement |
| The file was deleted from a synced folder | Web Trash or recycle bin for the cloud service | Letting the synced deletion become the only story |
| The content is older than expected | Version history and downloaded copies | Restoring over the live file before comparing |
| The file opens with errors | Duplicate first, repair only the duplicate | Damaging the only original with repeated repair attempts |
| Search finds many odd names | Sort by date, extension, and size | Opening every result and accidentally saving changes |
What makes recovery harder
- Restoring the first visible result because the filename looks right.
- Trusting Recent files instead of checking the actual storage location.
- Opening candidates directly from a temp folder and then saving over them.
- Running third-party recovery tools before copying cloud and backup evidence.
- Waiting until cloud Trash, version history, or backup retention windows expire.
Signs you should pause
Stop if the missing workbook is legally important, business-critical, the only copy of a major project, or stored on a drive that is making noise or disconnecting. Also stop if every repair attempt makes the file smaller or less readable. At that point, a clean handoff with copied candidates and notes is more valuable than another random tool.
Record the trail you already checked
Keep a small recovery log. It should name the missing file, the likely folder, the device, the service, and every candidate you copied so the next attempt does not start from zero.
This record helps even when the recovery works. If the restored workbook later turns out to be incomplete, you can return to the candidate list instead of starting over. It also makes a professional handoff cleaner because the next person can see what was already checked and which version looked strongest.
Sources and further reading
- Microsoft Support: recover Office files
- Microsoft Support: view previous versions of Office files
- Google Drive Help: find or recover a file
The point to remember
The safest recovery is not the fastest click. It is the version where every promising clue is copied, named, and still available if the first choice fails.