Setup · Windows 11 · File History
Back up a Windows 11 PC to an external drive — and restore a file to prove it
Windows already ships with a perfectly good file backup tool. File History quietly copies your libraries — Documents, Pictures, Videos, Music, Desktop — to an external drive, keeping older versions as it goes. Most people who turn it on never test it. This guide does the setup and then the part that matters: pulling one file back out, on purpose, while nothing is wrong.
Before you start
- An external drive, at least as big as the files you care about — and two to three times bigger if it will keep versions for years. Our 3-2-1 plan guide shows the sizing arithmetic.
- Know what File History covers. By default it backs up your libraries: Documents, Music, Pictures, Videos, and the Desktop, plus any custom libraries. A folder that lives outside a library is not covered until you add it to one — right-click the folder, choose Show more options > Include in library, and pick or create a library.
- Fifteen unhurried minutes. The first backup can take far longer than that, but it runs in the background while you work.
Turn File History on
- Plug the drive in. Connect the external drive and confirm it shows up in File Explorer with a drive letter. If the drive is brand new, this is also the moment to give it a recognizable name — "Backup A" beats "USB Drive".
- Open File History. Open the Control Panel, go to System and Security, and select Save backup copies of your files with File History. (File History still lives in the Control Panel in Windows 11; the Settings app's backup pages lead elsewhere.)
- Choose the drive. Select Select drive on the left, pick your external drive from the list, and confirm with OK. If you skip this, Windows may choose a drive you did not intend.
- Turn it on. Back on the main File History page, select Turn on. Windows starts the first backup straight away. Leave the drive connected and let it finish — the page reports progress, and unplugging mid-run just leaves the copy incomplete.
- Run one more copy now. Once the first pass completes, click Run now once to be sure the mechanism, not just the first run, works end to end.
Set how often and how long
Select Advanced settings on the File History page. Two decisions live there:
- Save copies of files: hourly is the sensible default. Shorter intervals protect fast-moving work at the cost of drive space; daily is fine for machines that mostly hold photos and archives.
- Keep saved versions: "forever" sounds safe and fills drives. Keeping versions for one to two years is a practical middle ground for most home machines — long enough to notice a file went bad, short enough that the drive is not a museum. If you deliberately want an archive, that is a different job than backup; let the backup drive roll.
Save the changes. From here the whole thing is automatic whenever the drive is attached — which is why the drive should live plugged in, not in a drawer.
The test restore
Now prove it works. Pick a file you can afford to experiment with — an old photo or document — and restore a copy of it without touching the original:
- Open the folder the file lives in in File Explorer, right-click the folder (or the file itself), and select Restore previous versions. If the folder sat at the top level of a drive, right-click the drive instead.
- Pick a version. The list shows the saved versions with their dates. Choose the most recent one and use Open to look inside it first if you want to confirm it holds the file you expect.
- Restore to a different place. Use the dropdown beside Restore and choose Restore to…, then a scratch folder — the Desktop will do. This matters: a plain Restore replaces the current version in place, and as Microsoft's own guidance warns, that replacement cannot be undone. Restoring to a scratch folder keeps the experiment harmless.
- Open the restored file. Go to the scratch folder and open it. It should be the file, whole and readable, with the content you expected. Delete the scratch copy when you are done.
You have now done, once and calmly, the exact thing you would otherwise first attempt on the worst day of the year with the only copy of something precious. The restore path is no longer theoretical — you know the menus, the drive letter, and that the versions are real. Put the drill on a quarterly rhythm and the backup stops being an act of faith.
What File History does not do
- It is not a system image. File History protects your files, not Windows itself, your applications, or your settings. A dead system drive still means reinstalling Windows and your apps — then restoring your files from the backup.
- It does not protect the drive it sits on. Anything that takes the PC and the attached drive together — theft, fire, ransomware — takes this copy too. That is what the off-site copy in a 3-2-1 plan exists for.
- It only backs up while the drive is connected. A drive in a drawer is a snapshot growing stale. If you cannot leave it attached, set a fixed weekly appointment to plug it in and run a copy.
When it goes wrong
- The drive does not appear in Select drive. Reconnect it, confirm it has a letter in File Explorer, and check it is not a drive Windows considers a system drive. A different USB port rules out a flaky connection.
- "File History doesn't recognize this drive." The usual cause is a drive that was reformatted or had its backup folder deleted. Re-select it under Select drive and turn File History on again; it will start a fresh set.
- A folder you care about is missing from the backup. It is almost certainly not in a library. Add it with Include in library, then run a copy and confirm the folder appears on the backup drive under FileHistory.
- No previous versions are listed for a file. Either the file was created after the last backup run, or it lives outside the covered folders. Check the second possibility first — it is the common one.
Sources
- Microsoft Support, Backup and restore with File History — setup, the libraries it covers, restoring previous versions, and the warning that an in-place restore cannot be undone.
- Backblaze, The 3-2-1 Backup Strategy: Best Practices — why a local copy like this one is one leg of a wider plan, not the whole of it.