File History says reconnect your drive: resume and verify backups
What to do first
A reconnected drive does not by itself confirm that files are protected. Identify the original destination, run File History, then check an actual saved version.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Windows
- Versions and conditions
- File History on Windows 11 / Windows 10, with an external or network destination
Symptoms
- Windows asks to reconnect the backup drive
- Recent edits are missing from saved file history
Causes and conditions
The configured backup destination may have been unavailable for an extended period. Check connectivity and whether File History still points to the intended drive.
Before you start
- Have the previously used drive or network destination available
- Choose a known file inside a folder covered by File History
Precautions
- A normal restore replaces the current file; use a separate location for a test
- Do not keep retrying backups onto storage that makes unusual noises or repeatedly disconnects
Tools and official pages used in this guide
Step-by-step instructions
Search Start for Control Panel, open System and Security, and choose the File History backup option. Record the destination label, location and last run time.
Confirm this is File History and that the requested destination is the one you recognize. Dismissing the notification does not run a backup.
For an external drive, check its power and cable, then see whether File Explorer can open it. For network storage, test the known shared folder through the normal network connection.
Compare its label and contents as well as its drive letter. If Windows requests initialization, stop this reconnection procedure.
Official links for this step
If storage is accessible but the warning remains, use Select drive in File History to choose the original external drive or network location.
Check the selected location before confirming. Keep the existing history while testing; a warning alone is insufficient reason to replace the backup set.
Choose Run now and leave the destination connected until the operation finishes. This gives you an observable result without waiting for the next scheduled run.
Check the run time and any new error. Record a capacity or access error exactly, rather than assuming the cable is still the cause.
Official links for this step
Right-click the original containing folder and open its previous versions. Select a recent entry and use the Open menu to inspect it in File History.
If you restore a sample, use the Restore menu to choose another location. Open that copy and compare the expected content without replacing the working file.
Check the result
- The manual run completes and its timestamp advances
- A recent version of the sample file can be opened
If the problem continues
- While the destination is inaccessible, copy important new work to separate working storage
- If only one folder lacks history, check whether it is included in a backed-up library
Scope of this guide
Troubleshooting guide — A symptom-specific procedure based on official documentation. Follow the branch that matches the observed state and verify the result.
Frequently asked questions
Does reconnecting immediately make the backup current?
Verify a completed run and a recent saved version; connectivity alone is not confirmation.
Why is the file absent from previous versions?
Check the backed-up folder scope and whether a saved version exists from when the file was present.
Official sources and dates
- Reconnect your File History drive in Windows ↗
- Backup and restore with File History ↗
- Move your files to a new Windows PC using an external storage device ↗
Source publication or resolution date: Not specified. Sources checked: 2026-09-12. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
Windows errors and troubleshooting →