This chapter covers Windows Backup and File History, two core backup technologies in Windows 10 and Windows 11 that are essential for data protection and recovery. For the 220-1102 exam, these topics appear in approximately 5-7% of questions, often integrated with broader backup and recovery scenarios. Understanding the differences between these tools, their configuration, and appropriate use cases is critical for selecting the right backup method in a given situation and for answering performance-based questions on the exam.
Jump to a section
Think of your computer's data as a vast library. Windows Backup is like having a comprehensive fire insurance policy with periodic off-site storage of all books. Every month, you pack up every book in the library and ship it to a secure warehouse. If the library burns down, you can rebuild the entire collection from the warehouse, but you lose any books added or changed since the last shipment. File History, on the other hand, is like having a clerk who, every time someone finishes reading a book and makes a note in it, immediately photocopies that page and files it in a cabinet. The clerk only tracks changes to books you've specifically marked as important. If a book gets damaged, you can retrieve the photocopy from yesterday, last week, or last month. You can even go back and see how a specific passage looked at different times. The fire insurance is for total disaster recovery; the daily photocopies are for quick fixes when you accidentally tear a page. In this analogy, Windows Backup is the insurance policy with periodic full shipments, while File History is the diligent clerk making incremental copies of only your designated documents. Both are needed for a complete protection strategy, but they serve different purposes and have different restoration speeds and granularity.
Windows Backup and File History are two distinct backup utilities built into Windows 10 and Windows 11. They are designed to protect user data but operate at different scopes and granularities. Windows Backup (legacy) is a full-system backup tool that can create a system image and backup of system files, while File History is a file-level backup tool that continuously protects files in user libraries, contacts, favorites, and desktop.
Why They Exist: Data loss from accidental deletion, file corruption, malware, or hardware failure is a common problem. Windows Backup provides a comprehensive recovery solution for the entire system, whereas File History offers granular versioning of individual files, allowing users to revert to previous versions quickly.
How They Work Internally
File History: File History uses the Volume Shadow Copy Service (VSS) to create point-in-time copies of files. It monitors designated folders (by default, all user libraries, contacts, favorites, and desktop) for changes. When a file changes, File History copies the previous version to a backup drive. By default, it saves copies every hour and retains them for a period based on available space. The backup destination can be an external drive, network location, or a separate internal drive. File History stores files in a folder structure that mirrors the original, with timestamps appended to folder names (e.g., Documents_2025-01-15_10-00-00). It does not compress or encrypt files by default, but BitLocker can encrypt the destination.
Windows Backup (Legacy): In Windows 10, Windows Backup (Control Panel > Backup and Restore (Windows 7)) creates system images and file backups. A system image is an exact copy of a drive, including Windows, system settings, programs, and files. It uses VSS to create a consistent snapshot. File backup allows selection of specific libraries, folders, and drives. Backups can be scheduled (e.g., daily at a specific time). The backup is stored in a VHDX file (system image) or a folder structure (file backup). Windows Backup does not support incremental backups after the initial full backup; it creates full backups each time (although it can be configured to keep only the latest versions).
Key Differences in Mechanism: - File History is incremental and continuous; Windows Backup is scheduled and typically full. - File History only protects user files (not system files or applications); Windows Backup can protect the entire system. - File History allows easy access to previous versions through File Explorer's 'Previous Versions' tab; Windows Backup requires the Backup and Restore interface or a system image recovery.
Key Components, Values, Defaults, and Timers
File History Defaults: - Backup interval: every hour (can be changed from 10 minutes to daily). - Retention: until space is needed (can be changed to 1 month, 3 months, 6 months, 1 year, 2 years, or forever). - Default folders: Libraries, Desktop, Contacts, Favorites, and OneDrive (if synced). - Cache size: uses up to 5% of the backup drive or 5 GB, whichever is larger.
Windows Backup Defaults: - No default schedule; user must configure. - System image includes the system drive (C:) and other drives as selected. - Backup location: external drive or network share; cannot be the same drive being backed up. - Retention: by default, Windows keeps only the latest backup (older ones are deleted when space is needed).
Configuration and Verification Commands
File History:
- Enable via Settings > Update & Security > Backup > Add a drive.
- Or via Control Panel > File History.
- Command-line: control /name Microsoft.FileHistory
- PowerShell: Enable-FileHistory -Drive D: (requires admin)
- To check status: Get-FileHistoryStatus
- To see backup targets: Get-FileHistoryTarget
Windows Backup:
- Access via Control Panel > Backup and Restore (Windows 7).
- Command-line: sdclt.exe opens Backup and Restore.
- To create a system image: wbadmin start backup -backupTarget:E: -include:C: -allCritical -quiet
- To check backup status: wbadmin get versions
Interaction with Related Technologies
Volume Shadow Copy Service (VSS): Both tools rely on VSS to create consistent snapshots. VSS coordinates with applications (like SQL Server) to ensure data integrity. Without VSS, backups might capture files in an inconsistent state.
Previous Versions: File History populates the Previous Versions tab in file properties. This allows users to restore a previous version without opening the backup tool. Windows Backup also contributes to Previous Versions if the file was included in a backup.
System Image Recovery: A system image created by Windows Backup can be used to restore a system to a working state using the Windows Recovery Environment (WinRE). This is useful for complete hardware failure or malware infection.
Important Exam Considerations
File History is only available in Windows 8.1, 10, and 11. It is not in Windows 7.
File History cannot back up to the same drive that contains the original files (except in Windows 10 version 1809 and later, where it can back up to a different partition on the same drive).
File History does not back up system files, program files, or temporary files.
Windows Backup (legacy) is deprecated in Windows 10 and may be removed in future versions. Microsoft recommends using File History for files and a third-party tool for system images, or using the 'Backup and Restore (Windows 7)' feature which still works.
In Windows 11, the 'Backup' settings page offers a simplified backup that includes OneDrive folder sync and remembers your settings for a new PC. This is not a full system backup.
Common Exam Traps
Trap: File History is the same as System Restore. Reality: File History protects user files; System Restore protects system files and settings.
Trap: Windows Backup creates incremental backups. Reality: It creates full backups each time (though it can be configured to keep multiple versions).
Trap: File History can back up the entire system. Reality: It only backs up selected user folders.
Trap: You can use File History to restore a system image. Reality: File History cannot restore a system image; only Windows Backup can.
Summary of Default Values
| Feature | Default Interval | Default Retention | Default Folders | |---------|------------------|-------------------|-----------------| | File History | Every hour | Until space needed | Libraries, Desktop, Contacts, Favorites, OneDrive | | Windows Backup | None (manual) | Keep latest only | User-selected |
Enable File History on a Drive
1. Connect an external drive or ensure a network location is available. 2. Open Settings > Update & Security > Backup. 3. Click 'Add a drive' and select the desired drive. Windows will automatically enable File History on that drive, copying default folders (Libraries, Desktop, Contacts, Favorites, OneDrive). 4. Alternatively, open Control Panel > File History and click 'Turn on'. 5. The first backup will begin immediately, copying all files in the monitored folders. Subsequent backups occur automatically every hour by default, copying only changed files using VSS. 6. To verify, open File History in Control Panel; it should show 'File History is on' and the backup drive.
Configure File History Advanced Settings
1. In Control Panel > File History, click 'Advanced settings'. 2. Under 'Versions', you can change the 'Save copies of files' interval from 10 minutes to Daily. 3. Change 'Keep saved versions' from 'Until space is needed' to a specific duration (1 month, 3 months, 6 months, 1 year, 2 years, or Forever). 4. Under 'Disk space', you can adjust the 'Offline cache' size (default 5% of drive or 5 GB). 5. You can also exclude specific folders by clicking 'Exclude folders'. 6. These settings affect how much history is retained and how often backups occur. A shorter interval increases disk I/O and storage usage.
Restore a File from File History
1. Navigate to the folder that originally contained the file (e.g., Documents). 2. Right-click the file (or folder) and select 'Restore previous versions'. 3. A list of available previous versions appears, with timestamps. 4. Select the desired version and click 'Restore' to replace the current file, or 'Open' to view it without overwriting. 5. Alternatively, open File History from Control Panel, browse to the file, and click the green 'Restore' button. 6. File History copies the selected version back to the original location. If the original file still exists, you'll be prompted to replace or skip.
Create a System Image with Windows Backup
1. Open Control Panel > Backup and Restore (Windows 7). 2. Click 'Create a system image' on the left. 3. Choose where to save the backup: on a hard disk (external), on one or more DVDs, or on a network location. 4. Select the drives to include in the image (by default, the system drive is included). 5. Confirm the settings and click 'Start backup'. 6. The process uses VSS to create a snapshot and writes a VHDX file containing the entire drive contents. 7. Depending on the size of the drive, this can take hours. 8. After completion, you'll be prompted to create a system repair disc (optional).
Restore from a System Image
1. Boot the computer from a Windows installation media or recovery drive. 2. On the initial screen, click 'Repair your computer'. 3. Select 'Troubleshoot' > 'Advanced options' > 'System Image Recovery'. 4. Windows will search for the most recent system image on the connected drives. 5. If it finds one, select it; otherwise, you can manually browse to the image file. 6. Choose additional restore options (format disks, install drivers). 7. Confirm and start the restoration. 8. The process will overwrite the entire system drive, restoring Windows, settings, programs, and files as they were when the image was created.
Scenario 1: Small Business File Server Protection
A small business runs a file server on Windows Server 2019 (though File History is a client feature, it can back up to a network share). They use File History on each client to back up user data to a central NAS. Each user's Documents, Desktop, and Favorites are automatically copied every hour. When an employee accidentally deletes an important spreadsheet, the IT admin restores the previous version from File History without needing to restore the entire server. The challenge is managing storage: with 50 users, each with 10 GB of data, and hourly backups, the NAS fills quickly. They set retention to 'Until space needed' and limit the offline cache to 2% per user. They also use Windows Backup on the server itself to create weekly system images. A common problem is that File History stops working if the network share is unavailable; they configure Group Policy to notify users if backup fails.
Scenario 2: Enterprise Desktop Rollout with System Images
A large organization deploys hundreds of identical desktops. They use Windows Backup to create a reference system image after installing Windows, drivers, and standard software. This image is stored on a network share. When a new employee joins, they deploy the image using deployment tools. For ongoing backup, they disable File History and instead use a third-party enterprise backup solution that supports incremental backups and centralized management. However, for a few high-value users (executives), they enable File History to a network share to allow self-service file restoration. The performance consideration is that File History can cause network congestion if many users back up simultaneously; they stagger backup intervals (e.g., different users start at different minutes past the hour).
Scenario 3: Home User with External Drive
A home user has a laptop with important family photos and documents. They connect an external USB drive once a week for a full Windows Backup system image. Additionally, they enable File History to that same drive, which runs continuously. When the laptop's hard drive fails, they buy a new laptop, boot from a recovery USB, and restore the system image. Then they use File History to restore any files that changed after the last system image. The common mistake is that the external drive is not always connected; File History will only back up when the drive is present. They learn to plug in the drive at least once a week. Another issue: if the external drive is formatted as FAT32, File History fails because it requires NTFS. They reformat to NTFS.
What the 220-1102 Exam Tests
Objective 1.2 (Operating Systems) includes 'Given a scenario, use Windows Control Panel utilities.' Under this, you must know File History and Backup and Restore (Windows 7). The exam expects you to:
Identify the correct tool for a given backup scenario (file versioning vs. full system recovery).
Know the default backup interval for File History (every hour).
Know that File History cannot back up system files or applications.
Understand that File History requires an external drive or network location.
Recognize that Windows Backup (legacy) creates system images.
Differentiate between File History, System Restore, and Backup and Restore.
Common Wrong Answers and Why Candidates Choose Them
Choosing System Restore for file recovery. Candidates confuse System Restore (system files/settings) with File History (user files). The exam may describe a scenario where a user accidentally deleted a document; the wrong answer is System Restore. Correct answer: File History or Previous Versions.
Selecting Backup and Restore (Windows 7) for continuous file versioning. This tool does not provide continuous versioning; it creates scheduled full backups. Candidates think it's the same as File History. Correct answer: File History for continuous versioning.
Thinking File History can restore the entire system. Candidates see 'backup' and assume it covers everything. The exam will present a scenario where the system is unbootable; the wrong answer is File History. Correct answer: system image recovery via Backup and Restore.
Believing File History works on the same drive as the original files. This is false; it requires a different drive (except for different partitions on the same drive in newer Windows versions). Candidates may think it's like a recycle bin.
Specific Numbers and Terms That Appear on the Exam
Default File History interval: every hour (60 minutes).
File History monitors: Libraries, Desktop, Contacts, Favorites, OneDrive.
File History destination: external drive or network location (cannot be the same drive).
System image includes: system drive (C:), system reserved partition, and any other drives selected.
Backup and Restore (Windows 7) is found in Control Panel.
Edge Cases and Exceptions
File History does not back up files that are open in exclusive mode (e.g., Outlook PST files in use). VSS may handle some, but not all.
If the backup drive runs out of space, File History will delete older versions (by default, 'Until space needed').
File History can be configured via Group Policy for domain-joined computers.
In Windows 10 version 1809 and later, File History can back up to a different partition on the same physical drive (not just external).
How to Eliminate Wrong Answers
If the scenario involves recovering an older version of a specific file, eliminate any answer that mentions system image, system restore, or backup and restore (unless it's about system recovery).
If the scenario requires restoring the entire system after a hard drive failure, eliminate File History (it only backs up user files).
If the question asks about continuous backup, eliminate Backup and Restore (Windows 7) because it is scheduled, not continuous.
Look for keywords: 'previous version' -> File History; 'system image' -> Backup and Restore; 'system settings' -> System Restore.
File History automatically backs up user files every hour by default.
File History only backs up Libraries, Desktop, Contacts, Favorites, and OneDrive.
File History requires a separate drive (external or network) or different partition.
Windows Backup (Backup and Restore) creates full system images or file backups.
System images include the entire system drive and can restore a computer to a working state.
File History provides versioning; Windows Backup provides full snapshots.
The 220-1102 exam tests the difference between File History, System Restore, and Backup and Restore.
Common wrong answer: using System Restore to recover a deleted document (correct: File History).
These come up on the exam all the time. Here's how to tell them apart.
File History
Continuous protection: backs up every hour by default.
Only protects user files (Libraries, Desktop, etc.).
Provides easy access to previous versions via File Explorer.
Stores backups in a folder structure with timestamps.
Requires external or network drive (cannot be same drive).
Windows Backup (Backup and Restore)
Scheduled full backups (user configures schedule).
Can protect entire system (system image) or selected files.
Restores via dedicated interface or system image recovery.
Stores system images as VHDX files; file backups in folder structure.
Can back up to external drive, network, or DVDs.
Mistake
File History backs up the entire system including Windows and applications.
Correct
File History only backs up user files in Libraries, Desktop, Contacts, Favorites, and OneDrive. It does not back up system files, installed programs, or Windows settings.
Mistake
File History is the same as System Restore.
Correct
File History protects user files by keeping previous versions. System Restore creates restore points for system files and settings, not user files.
Mistake
Windows Backup (Backup and Restore) creates incremental backups.
Correct
Windows Backup creates full backups each time. It does not support incremental backups. However, it can keep multiple versions of files (full copies) if configured to do so.
Mistake
File History can back up to the same drive that contains the original files.
Correct
File History requires a separate drive (external or network) or a different partition on the same physical drive (Windows 10 1809+). It cannot back up to the same partition.
Mistake
You can use File History to restore a system image.
Correct
File History cannot restore system images. System images are created and restored using Backup and Restore (Windows 7) or third-party tools.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The default backup interval for File History is every hour (60 minutes). You can change this in Advanced Settings from 10 minutes to daily. The exam expects you to know the default is every hour.
Yes, File History can back up to an external USB drive, as long as it is formatted as NTFS. It can also back up to a network location or a different partition on the same physical drive (Windows 10 1809+). It cannot back up to the same drive that contains the original files.
By default, File History backs up the Libraries (Documents, Music, Pictures, Videos), Desktop, Contacts, Favorites, and OneDrive (if synced). You can add or exclude folders via the 'Exclude folders' option.
Right-click the file or folder in File Explorer, select 'Restore previous versions', choose a version from the list, and click 'Restore'. Alternatively, open File History from Control Panel, browse to the file, and click the green 'Restore' button.
File History protects user files by keeping previous versions. System Restore creates restore points for system files, registry settings, and installed programs. They serve different purposes: File History for file recovery, System Restore for system stability.
No, File History only backs up user files. To restore an entire system, you need a system image created by Windows Backup (Backup and Restore) or a third-party imaging tool. System images can be restored using Windows Recovery Environment.
No, Windows Backup (Backup and Restore) creates full backups each time. It does not support incremental or differential backups. However, you can configure it to keep multiple versions of files, but each version is a full copy.
You've just covered Windows Backup and File History — now see how well it sticks with free 220-1102 practice questions. Full explanations included, no account needed.
Done with this chapter?