How to Set Up Automatic Backups with File History on Windows

File History continuously backs up versions of files in your personal folders to a separate drive, letting you restore not just a deleted file but a specific previous version of one that’s still there but was edited or corrupted.

Step 1: connect a drive to back up to

File History needs a destination separate from your system drive — an external USB drive or a network location both work.

Step 2: turn on File History

Settings → System → Storage → Advanced storage settings →
  Backup options → Add a drive (or use Control Panel →
  File History on older Windows versions)

Step 3: select the backup drive

Windows will detect connected external drives and network locations automatically — select the one you want to use as the destination.

Step 4: confirm which folders are included

Control Panel → File History → Exclude folders

By default, File History covers your standard personal folders (Documents, Pictures, Desktop, and similar) — review the exclusion list if there are large folders in that scope you don’t actually want backed up (large media libraries, local development caches).

Step 5: configure how often backups run and how long versions are kept

Control Panel → File History → Advanced settings
  Save copies of files: every 10 minutes (adjustable)
  Keep saved versions: Forever (adjustable)

More frequent backups mean finer-grained version history at the cost of more space consumed on the backup drive over time — the right balance depends on how actively your files change and how much backup storage you have available.

Step 6: restore a previous version of a specific file

Right-click the file in File Explorer → Restore previous versions

Or through File History’s own interface:

Control Panel → File History → Restore personal files →
  browse by date, select the file, click Restore

Step 7: restore an entire folder to a previous point in time

The same “Restore personal files” interface lets you navigate to a folder (rather than a single file) and restore its entire contents as they existed at a specific backup point — useful for undoing widespread accidental changes or deletions across many files at once, not just a single file.

Step 8: verify backups are actually running as expected

Control Panel → File History →
  check the "last backed up" timestamp shown at the top

Confirm this timestamp updates as expected over time — a File History configuration that silently stopped working (a disconnected drive, a permissions issue) provides no protection at all, so periodically confirming it’s actually current is worth doing rather than assuming it’s working indefinitely once configured.

Why version history matters beyond just “having a backup”

An ordinary backup that simply mirrors your current files protects against losing a file entirely, but not against silently saving over a good version of a file with a bad one — File History’s versioned approach protects against both failure modes, letting you reach back to any previous version within its retention window, not just the most recent backup snapshot. That distinction is exactly why File History is a meaningfully different tool from a simple file-copy backup, even though both ultimately protect the same personal files.

Adding a folder outside the default personal-folder scope

Settings → System → Storage → Advanced storage settings →
  Backup options → More options → Add a folder

File History’s default coverage (Documents, Pictures, Desktop, and a handful of other standard personal folders) doesn’t automatically include every location that might genuinely need version history — a project folder living outside the default profile structure, for instance, or a folder on a secondary internal drive. Explicitly adding these locations through the “More options” screen extends File History’s coverage to exactly the folders that matter for your specific workflow, rather than either accepting the default scope as sufficient or manually relocating important working folders just to bring them under File History’s default coverage umbrella.

Understanding what happens when the backup drive fills up

Once a File History destination drive reaches capacity, File History begins removing the oldest saved versions automatically to make room for new ones — a “Keep saved versions: Forever” setting is aspirational rather than a hard guarantee once the physical drive itself runs out of space, and it’s worth checking the destination drive’s remaining capacity periodically (Control Panel → File History → Advanced settings shows current usage) rather than assuming “Forever” literally means every version will remain available indefinitely regardless of the drive’s actual physical limits.

Migrating File History to a new or larger destination drive

Control Panel → File History → Turn off File History →
  (with the old drive still connected) Select drive →
  choose the new destination → confirm migration

Windows offers to migrate existing File History data to a newly selected drive rather than starting version history over from scratch, provided the original drive is still connected and accessible during the switch — worth doing deliberately when upgrading to larger backup storage, since simply disconnecting the old drive and pointing File History at a new one without this migration step loses the existing version history built up on the original drive entirely, starting fresh rather than carrying it forward.

Why File History alone isn’t a complete disaster-recovery plan

File History protects against file-level mistakes and deletions extremely well, but a backup drive that stays permanently connected to the same machine it’s protecting shares that machine’s exposure to theft, fire, or other events affecting the physical location as a whole — the same limitation covered in this blog’s Time Machine coverage for macOS applies identically here. Pairing File History with a genuinely offsite or cloud-based backup, or periodically rotating a second backup drive kept physically elsewhere, closes the gap File History alone was never actually designed to cover.

Related:

Sources: