File History can stop saving your backups for many reasons, but most problems are fixable. If File history doesn’t work in Windows 10, this article shows the 11 most common causes and step-by-step fixes so you can get your backups running again.
You’ll learn what typically breaks File History, how to diagnose the exact cause, and clear instructions (menus, commands, and options) to restore normal operation.
Key Takeaway
If File history doesn’t work in Windows 10, first check your backup target (drive availability and free space), then ensure the File History service and configuration are healthy—most problems are fixed by reconnecting or reselecting the drive, repairing disk errors, or resetting File History’s configuration.
Quick Fix Guide
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| File History is turned off | Turn on File History in Settings > Update & Security > Backup or Control Panel > File History. |
| Backup drive missing or disconnected | Reconnect the external USB/NAS and ensure Windows recognizes it in This PC. |
| Not enough free space on target drive | Free space or choose a larger/clean drive in File History > Select drive. |
| Target drive format or permissions issue | Format drive to NTFS or update permissions to allow your account to write. |
| File History service or related services stopped | Start/Restart File History Service via Services.msc or run net start fhsvc. |
| Corrupted FileHistory configuration | Reset File History by deleting FileHistory folder and reconfigure backup. |
| Antivirus or third-party backup conflicts | Temporarily disable antivirus or exclude FileHistory processes and retry. |
| Network drive or mapped drive issues | Map network drive with persistent credentials or use a UNC path like \server\share. |
| Excluded folders or file type limitations | Check Advanced settings in File History and remove exclusions. |
| Windows updates or system file corruption | Run sfc /scannow and DISM; install pending updates and restart. |
| Corrupted user profile or account permission problems | Test with a new local/admin user account and transfer settings if it works. |
Detailed Fixes for “File history doesn’t work in Windows 10”
Below are the 11 reasons with clear explanations and step-by-step fixes. Each subsection uses beginner-friendly steps and exact menu names.
1) File History is turned off
Why it causes the problem:
- If File History is not enabled, Windows won’t create or update backups.
Step-by-step solution:
- Open Settings > Update & Security > Backup.
- Under Back up using File History, click Add a drive if none selected, then choose your drive.
- If a drive is already selected but status shows Off, click More options and then Back up now.
- Alternatively, open Control Panel > File History and click Turn on.
Notes:
- If Add a drive lists no drives, ensure the disk is connected and visible in This PC.
2) Backup drive missing or disconnected
Why it causes the problem:
- File History needs a reachable target (external HDD, USB, or network share). If it disappears, backups cannot run.
Step-by-step solution:
- Physically reconnect the external USB drive and check This PC for the drive letter.
- If it’s a network location, ensure the network is reachable and you can browse \server\share.
- In Control Panel > File History, click Select drive and re-select the correct drive.
- If Windows assigns a different drive letter, reselect the new letter or map the network path.
Tips:
- Use a powered USB hub or connect directly to PC USB ports for reliability.
3) Not enough free space on target drive
Why it causes the problem:
- File History can fail when the destination runs out of space for new versions.
Step-by-step solution:
- Open This PC, right-click the backup drive, choose Properties to view free space.
- In Control Panel > File History > Advanced settings, under Versions, adjust how long to keep saved versions to reduce retention.
- Delete older version folders manually: go to the backup drive and remove dated folders in FileHistory if safe.
- Or choose a larger drive using File History > Select drive.
Notes:
- Keep a margin of free space to avoid repeated failures.
4) Target drive format or permissions issue
Why it causes the problem:
- File History expects NTFS for certain features; exFAT or FAT32 may cause permission or file size issues. Wrong NTFS permissions block writes.
Step-by-step solution:
- Check drive format: Right-click drive in This PC > Properties and confirm File system: NTFS.
- If not NTFS, backup any data on the drive, then format to NTFS: right-click drive > Format… > choose NTFS > Start.
- Fix permissions: right-click drive > Properties > Security > ensure your user account (or Everyone) has Full control. Click Edit to change permissions.
- Apply ownership if needed: open Command Prompt (Admin) and run takeown /f X:\ /r /d y (replace X: with drive letter) then icacls X:\ /grant %username%:F /t.
Warnings:
- Formatting erases data; back up first.
Why it causes the problem:
- The background service must run to schedule and write backups.
Step-by-step solution:
- Press Win + R, type services.msc, press Enter.
- Find File History Service (or fhsvc) or check related services like Workstation and Remote Procedure Call (RPC).
- Right-click the service > Start or Restart. If the startup type is not Automatic, double-click and set Startup type: Automatic.
- Alternatively open Command Prompt (Admin) and run: net start fhsvc.
Notes:
- If service fails to start, check the Event Viewer for error logs (see next fix).
6) Corrupted FileHistory configuration
Why it causes the problem:
- Corrupt config or cache files under the user profile can prevent File History from functioning.
Step-by-step solution:
- Stop the service: open Command Prompt (Admin) and run net stop fhsvc.
- Navigate to your FileHistory folder on the backup drive and delete the Configuration and Catalog files (path usually X:\FileHistory\
). Also consider renaming the FileHistory folder to keep a copy. - On the PC, delete local config at %LocalAppData%\Microsoft\Windows\FileHistory (rename rather than delete for safety).
- Restart the service: net start fhsvc, then reconfigure File History in Control Panel > File History > Turn on.
Tips:
- Renaming keeps a backup you can restore if needed.
7) Antivirus or third-party backup conflicts
Why it causes the problem:
- Security or backup software may lock files or block File History processes.
Step-by-step solution:
- Temporarily disable third-party antivirus or real-time protection: open the antivirus UI and turn off shields for a short time.
- Add exclusions for File History folders and executables: exclude FileHistory.exe or the FileHistory target folder.
- Attempt Back up now in Control Panel > File History.
- If it works, reconfigure exclusions and enable antivirus again.
Caution:
- Don’t leave security disabled; only test briefly.
8) Network drive or mapped drive issues
Why it causes the problem:
- Mapped drives aren’t always available to the system account; credential/persistence problems can block scheduled backups.
Step-by-step solution:
- Use a UNC path: in Control Panel > File History > Select drive, choose Add network location and enter \server\share.
- Ensure persistent mapping: open Command Prompt (Admin) and run net use Z: \server\share /persistent:yes /user:DOMAIN\username password. Replace Z: and credentials.
- Save credentials in Credential Manager: Control Panel > Credential Manager > Windows Credentials > Add a Windows credential and enter the server address and account.
- Test accessing the UNC path in File Explorer to confirm connectivity.
Notes:
- For NAS devices, enable SMB and ensure the NAS firmware supports Windows File History.
9) Excluded folders or file type limitations
Why it causes the problem:
- File History excludes certain folders or file types by configuration; system folders may be intentionally excluded.
Step-by-step solution:
- Open Control Panel > File History > Advanced settings.
- Click Exclude folders and verify no important folders are listed; remove unwanted exclusions.
- In More options, check Back up my files frequency and size limits.
- Ensure the folders you want are under This PC > Libraries or are included by File History; add files to Libraries if needed.
Tip:
- File History backs up files in user libraries, Desktop, Contacts, and Favorites by default.
10) Windows updates or system file corruption
Why it causes the problem:
- OS bugs or corrupted system files can break File History behavior.
Step-by-step solution:
- Run system file check: open Command Prompt (Admin) and run sfc /scannow.
- If SFC reports issues, run DISM: DISM /Online /Cleanup-Image /RestoreHealth then rerun sfc /scannow.
- Install all pending Windows updates: Settings > Update & Security > Windows Update > Check for updates and restart.
- After updates and repair, test File History.
Notes:
- Keep backups before large updates; system repair can take time.
11) Corrupted user profile or account permission problems
Why it causes the problem:
- If the user profile is damaged, File History may not access the profile folders correctly.
Step-by-step solution:
- Create a new local admin account: Settings > Accounts > Family & other users > Add someone else to this PC, then choose I don’t have this person’s sign-in information and create a new user with admin rights.
- Sign in to the new account and set up File History in Control Panel > File History.
- If it works, migrate your data to the new profile: copy files from C:\Users\OldUser to the new user folder (do not overwrite system files).
- Optionally repair the old profile using Microsoft account troubleshooting or user profile service fixes.
Tips:
- Create a Test user before deleting the original profile.
Preventions and Best Practices
- Always keep your backup drive formatted as NTFS and maintain at least 10–20% free space.
- Use a dedicated external drive for File History; avoid using the system drive as a target.
- Configure File History frequency and retention in Control Panel > File History > Advanced settings to balance disk use and recovery points.
- Regularly check File History logs in Event Viewer: Event Viewer > Applications and Services Logs > Microsoft > Windows > FileHistory-Service for errors.
- Keep Windows and your device drivers updated to avoid incompatibilities.
- Consider alternative backup tools (Windows Backup and Restore (Windows 7), third-party backup apps, or cloud backup) if you need full image backups or more granular scheduling.
FAQ
What should I check in Event Viewer for File History errors?
Look in Event Viewer > Applications and Services Logs > Microsoft > Windows > FileHistory-Service for error or warning entries; review the details and Event ID to guide troubleshooting.
Can File History back up system files or installed programs?
No — File History only backs up user files (libraries, desktop, contacts, favorites). For system images use Backup and Restore (Windows 7) > Create a system image or third-party imaging tools.
How do I move File History to a new drive without losing older versions?
Stop File History, copy the entire FileHistory folder from the old drive to the same location on the new drive, then select the new drive in File History settings and turn File History back on.
Is there a way to force File History to run immediately?
Yes — open Control Panel > File History, then click Run now or Back up now depending on the view. You can also run schtasks /run /TN “\Microsoft\Windows\FileHistory\File History” in an elevated Command Prompt to trigger the scheduled task.
What if File History keeps losing my network credentials?
Store them in Control Panel > Credential Manager > Windows Credentials and add the network share credentials, or map the drive with net use /persistent:yes so credentials persist across reboots.
Conclusion
File History problems usually come down to a disconnected or incompatible backup target, permissions/service issues, or corrupted configuration—most fixes involve reconnecting the drive, repairing disk or system files, or resetting File History. If File history doesn’t work in Windows 10, follow the checks above in order (drive, space, services, permissions, config) and you’ll resolve the majority of issues.
