● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows 11 File History settings panel on a modern laptop showing backup status and drive selection menu with external USB drive connected
Fix It Yourself · Troubleshooting

Windows 11 File History not backing up automatically

Updated 7 June 202614 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

File History worked fine for months, then one day the automatic backups just stopped. You click 'Run now' and it works, but the scheduled hourly backups? Silent failures, cryptic errors like 'unknown error' or 'We can't copy files to your File History drive', or worse - nothing at all. After 15 years fixing backup issues remotely, I can tell you this isn't the drive failing. It's configuration drift, permissions, or a corrupted cache that's sabotaging your backups. The good news: most of the time you can fix it in 25 minutes without losing a single backup file.

TL;DR

File History not backing up automatically usually stems from a disconnected backup drive, corrupted configuration, or missing permissions. Start by assigning a fixed drive letter, reselecting the backup drive, and running a manual backup. If that doesn't work, reset the File History cache by deleting C:\\Users\\<username>\\AppData\\Local\\Microsoft\\Windows\\FileHistory, restart, and reconfigure. Check NTFS permissions (Full Control for your user and SYSTEM) and verify the File History Service is running and scheduled tasks are enabled.

⏱️ 14 min read✅ 70-80% success rate📅 Updated May 2026

Key Takeaways

  • Automatic backups fail silently when the backup drive is unavailable, drive letter changes, or configuration gets corrupted
  • Manual 'Run now' works but scheduled backups don't because they depend on the File History Service and scheduled tasks triggering correctly
  • Reselecting your backup drive after assigning it a fixed drive letter fixes 70-85% of issues in under 10 minutes
  • If problems persist, resetting the File History cache clears corrupted configuration without deleting your actual backup files
  • Permission errors (Error 80070005) require checking NTFS permissions on the backup drive for both your user account and SYSTEM
  • Network backup targets need consistent connectivity, proper SMB support, and correct share/NTFS permissions to work reliably

At a Glance

  • Difficulty: Easy to Intermediate
  • Time Required: 25 minutes (most fixes under 10)
  • Success Rate: 70-85% of users with the first solution

What Causes File History Not Backing Up Automatically?

The core issue is that Windows File History has two separate execution paths. Manual 'Run now' commands execute immediately in your session, under your user context, with your drive connected and your network active. Automatic backups, by contrast, trigger via the Windows Task Scheduler at times you're not actively using your PC - and if anything in that chain breaks, the backup silently fails.

Most commonly, your backup drive is either disconnected or powered off when the scheduled backup fires. USB drives sleep after inactivity. External drives get unplugged. Network shares go offline due to Wi-Fi disconnects, VPN timeouts, or a NAS shutdown for maintenance. When Windows Task Scheduler tries to run the File History backup task and the target isn't available, it logs a quiet failure and moves on.

Less obvious: drive letters change. You connect your external backup drive and Windows assigns it letter E:. You restart with other USB devices plugged in, and suddenly File History's target drive is now F:. File History was configured to back up to E:, so it can't find the drive at the scheduled time. Or your configuration file becomes corrupted - rare, but happens after Windows feature updates, unexpected shutdowns during a backup, or disk errors. When File History tries to read its configuration, it fails to identify the target or hangs trying to initialize.

Permissions are another silent killer. Your user account lost Full Control on the backup drive (sometimes from a Windows update resetting inheritance). The SYSTEM account - which File History Service runs under - doesn't have write access. Network shares have overly restrictive permissions. Error 80070005 (Access Denied) appears in Event Viewer but not to you directly, so you think the backup is happening when it's being rejected.

Finally, the File History Service itself can stop running, or scheduled tasks get disabled by a third-party cleanup tool, a Group Policy update, or a failed Windows update that rolls back task configuration.

File History Not Backing Up Automatically: Quick Fix

Before diving into cache resets and permission debugging, try this: reassign a fixed drive letter to your backup drive and reselect it in File History. This fixes the majority of cases in under 10 minutes, especially if your drive letter drifted or you swapped USB ports.

1

Assign Fixed Drive Letter and Reselect Backup Drive Easy

  1. Open Disk Management
    Press Win + X, select 'Disk Management'. Wait for it to load (usually takes a few seconds).
  2. Locate your backup drive
    Find your external drive or USB in the list. Note its current drive letter (e.g. E:) and volume name. Right-click the volume (not the unallocated space above it).
  3. Assign a fixed drive letter
    Select 'Change Drive Letter and Paths'. Click the 'Change' button. Choose a letter near the end of the alphabet - Z: or Y: works best because they rarely conflict with other devices. Click OK. Windows may ask for administrator confirmation.
  4. Open File History settings
    Open Control Panel (search 'Control Panel' from the Start menu). Navigate to System and Security → File History.
  5. Stop using the current drive
    In the File History window, click 'Stop using drive' in the left sidebar. Wait for confirmation that File History is disabled. This doesn't delete backups - it just disconnects the current configuration.
  6. Reselect your backup drive
    Click 'Select drive' in the left sidebar. Your backup drive should now appear in the list with its new fixed letter (Z:). Click it, then click OK.
  7. Turn on File History and test
    Click the 'Turn on' button. Once enabled, click 'Run now' immediately to perform a manual backup. Monitor the window until it completes. If successful, you'll see a timestamp and a green checkmark.
  8. Verify automatic backup schedule
    Click 'Advanced settings'. Confirm 'Save copies of files' is set to your desired frequency (default: Every hour). Close the window. Wait for the next scheduled time and check if the 'Last run' timestamp updates.
✓ If manual backup succeeds and 'Last run' timestamp updates on schedule after this, your File History is working again. No cache reset needed.

More File History Solutions

Solution 2: Reset File History Cache and Corrupted Configuration

If reselecting the drive didn't fix automatic backups, your File History configuration or cache is likely corrupted. This happens after Windows feature updates, interrupted backups during shutdowns, or disk errors. The good news: resetting the cache clears the corrupted files without touching your actual backups stored on the drive.

2

Clear File History Cache and Reconfigure Intermediate

  1. Turn off File History
    Open Control Panel → System and Security → File History. Click 'Turn off' button and wait for confirmation.
  2. Enable viewing hidden files
    Open File Explorer. Click the View menu → Show → Hidden items. This reveals the AppData folders.
  3. Navigate to File History configuration
    Go to C:\\Users\\<your-username>\\AppData\\Local\\Microsoft\\Windows. You'll see a 'FileHistory' folder here.
  4. Delete the FileHistory folder
    Right-click the 'FileHistory' folder and select Delete (or rename it to 'FileHistory_old' for safety). If prompted for administrator permission, click Continue. This removes corrupted local cache and configuration.
  5. Optionally clean backup drive configuration
    On your backup drive, open the 'FileHistory' folder. Inside, you'll see a 'Configuration' folder and a 'Data' folder. Rename 'Configuration' to 'Configuration_old'. Leave 'Data' untouched - that contains your actual backup files and version history.
  6. Restart your computer
    Restart Windows 11 fully. This ensures all File History services are cleared from memory and ready to reinitialize.
  7. Reconfigure File History from scratch
    After restart, open Control Panel → File History. Click 'Select drive', choose your backup drive, click OK. Click 'Turn on'. Then immediately click 'Run now' to perform the initial backup after cache reset.
  8. Monitor automatic operation
    Wait for the next scheduled backup time (check Advanced settings for the frequency - default is 1 hour). Check if 'Last run' timestamp updates. You can also check Event Viewer: Applications and Services Logs → Microsoft → Windows → FileHistory-Core → Operational. Look for successful backup events (Event ID 201).
✓ Cache reset clears corrupted configuration. Your actual backup files remain on the drive, though File History's version interface needs to rebuild its database. Manual backups should work immediately after reconfiguration.
⚠️ Warning: Deleting the FileHistory folder removes File History's ability to display old file versions in its interface for about 24 hours (until it rebuilds the database). However, your actual backed-up files are safe on the backup drive and can be manually recovered if needed. Do NOT delete the 'Data' folder on the backup drive - that contains your actual backup files.

Solution 3: Fix Permissions and Verify File History Service

If cache reset didn't work, the problem is likely permissions or the File History Service not running. Error 80070005 ('Access Denied') in Event Viewer confirms this. Your user account or the SYSTEM account lacks write permissions on the backup drive, or the backup drive is set to read-only.

3

Fix NTFS Permissions and File History Service Advanced

  1. Check Event Viewer for specific errors
    Press Win + X, select Event Viewer. Navigate to Applications and Services Logs → Microsoft → Windows → FileHistory-Core → Operational. Look for recent red Error entries. Note any error codes (particularly 80070005 for Access Denied, or 0x80070005). This tells you if the problem is permissions or something else.
  2. Fix NTFS permissions on backup drive
    Right-click your backup drive in File Explorer → Properties → Security tab. Click Edit. Select your user account and tick 'Full Control'. Click Apply. Repeat for the SYSTEM account (if not present, click Add, type SYSTEM, click Check Names, then OK, and set Full Control). This ensures File History Service has permission to write backups.
  3. Take ownership if permission changes fail
    If you can't modify permissions, click Advanced on the Security tab. Click the 'Change' link next to Owner (currently probably TrustedInstaller or Administrator). Type your username, click 'Check Names', then OK. Tick 'Replace owner on subcontainers and objects', click Apply. This makes your account the owner so you can modify permissions. Then return to Security tab and set Full Control as above.
  4. For network drives: verify share and NTFS permissions
    On the NAS or network PC hosting the share, access share settings. Ensure your Windows user (or Everyone for home networks) has Read/Write permissions at the share level. Then check NTFS permissions on the shared folder itself - ensure Read/Write for your user. Also confirm the share is not at quota limit (check available space).
  5. Verify File History Service is running
    Press Win + R, type services.msc, press Enter. Scroll to 'File History Service'. Check Status - should say 'Running'. Check Startup Type - should be 'Manual (Trigger Start)' (this means Windows starts it on-demand when scheduled tasks trigger). If stopped, right-click → Start. If Startup Type is Disabled, right-click → Properties, change Startup Type to Manual (Trigger Start), click Apply, then click Start.
  6. Check File History scheduled tasks
    Press Win + R, type taskschd.msc, press Enter. Navigate to Task Scheduler Library → Microsoft → Windows → FileHistory. You should see several tasks like 'File History (maintenance mode)'. Verify all are Enabled (not grayed out). If any are Disabled, right-click → Enable. Right-click 'File History (maintenance mode)' → Run to test immediately. Check 'Last Run Result' - should show success (0x0) or a low number.
  7. Test automatic backup
    Note the current time and 'Last run' timestamp in File History settings. Wait for the next scheduled backup interval (usually 1 hour). Refresh File History or check Event Viewer FileHistory-Core logs. If 'Last run' updates and Event Viewer shows Event ID 201 (successful backup), permissions and service are fixed.
  8. Check for security software interference
    If backups still fail, temporarily disable third-party antivirus (Windows Defender can stay on). Try a manual 'Run now' backup. If successful, antivirus is blocking File History. Add C:\\Windows\\System32\\FileHistory.exe to your antivirus exclusions list, re-enable antivirus, and test again.
✓ Once 'Last run' timestamp updates after scheduled backup time and Event Viewer shows successful events, File History automatic backups are working. Permissions and service are correctly configured.
ℹ️ Tip: For corporate or domain-joined PCs, Group Policy might override local File History settings. If you're on a corporate network and automatic backups still fail after these fixes, contact your IT department - they may have disabled File History via policy or restricted backup locations.

Preventing File History Automatic Backup Failures

Once you've fixed automatic backups, keep them working with these preventive steps:

  • Assign fixed drive letters now. Go to Disk Management, right-click your backup drive, change its letter to Z: (or similar). This prevents Windows reassigning it and breaking File History when you reconnect after reboots or moving USB ports.
  • Disable USB Selective Suspend for backup drives. Press Win + R, type powercfg.cpl, press Enter. Click 'Change plan settings', then 'Advanced'. Expand USB settings and disable USB Selective Suspend. This prevents your backup drive falling asleep during scheduled backups.
  • Keep backup drive connected during backup windows. If you back up hourly and unplug the drive during work, it won't be available when the backup fires. For USB drives, leave them connected. For network drives, ensure the NAS is always on.
  • For network backup targets, ensure constant accessibility. If backing up to a NAS or network PC, they must be powered on when scheduled backups run. If that's not feasible, adjust your backup schedule to match availability (e.g. every 4 hours if NAS is only on business hours).
  • Check 'Last run' timestamp regularly. After File History is working, spend 30 seconds monthly opening Control Panel → File History and verifying the 'Last run' timestamp is recent (within your backup frequency - if set to hourly, should be within the last hour). This catches failures early before you lose data.
  • Monitor Event Viewer for warnings. Open Event Viewer → FileHistory-Core monthly. Look for any Warning or Error events. These indicate developing problems before backups silently stop.
  • Maintain minimum free space. File History may fail silently if the backup drive is nearly full. Keep at least 20-30% free space on your backup drive. Check periodically in File Explorer: right-click backup drive → Properties, look at 'Used space' vs 'Total size'.
  • Test after Windows updates. After major Windows 11 feature updates (released a few times per year), File History sometimes resets. Open File History, verify settings are still correct, and click 'Run now' to confirm it's working. If not, reselect the drive using Solution 1.
  • For network shares, use IP address instead of computer name. If backing up to \\\\NAS-name\\backups, change it to \\\\192.168.1.10\\backups (use your NAS's actual IP). DNS resolution delays can cause backup timeouts. IP addresses are more reliable for scheduled backups.
  • Document your configuration. Write down: backup drive letter, network path (if applicable), backup frequency, and the date you set it up. If File History resets or corrupts, you can quickly reconfigure from these notes instead of guessing.

Why Manual Backups Work But Automatic Ones Don't

Understanding the difference helps troubleshoot faster. When you click 'Run now' in File History, Windows launches the backup immediately in your user session. Your drive is connected (you're using the computer). Your network is active. File History runs with elevated privileges and finds its configuration files instantly. Any temporary hiccup gets reported back to you in real-time because you're watching.

Automatic backups are scheduled via Windows Task Scheduler to run at specific times (default: hourly). The backup runs in the SYSTEM account context, not your user context. If you're away, asleep, or the computer is in sleep mode, the backup still fires - but if your USB drive is unplugged or your NAS is offline, the backup fails silently. Windows Task Scheduler logs the failure internally (visible in Event Viewer), but doesn't notify you. This is why many users discover the problem weeks later when they actually need to restore a file.

Common File History Error Codes and What They Mean

Error 80070005 (Access Denied): Your user or SYSTEM account lacks write permissions on the backup drive. Solution 3 (Fix Permissions) addresses this. Check NTFS permissions on the backup drive's Security tab and ensure Full Control for both your user and SYSTEM.

'We can't copy files to your File History drive': Usually means the backup drive is full, write-protected, or disconnected. Verify free space on the drive (use File Explorer → Properties). If write-protected, check the drive's physical write-protect switch (common on some USB drives). If disconnected, reconnect and reselect via File History settings.

'Unknown error': Typically indicates corrupted File History configuration. Solution 2 (Reset Cache) clears this. Delete the FileHistory folder under AppData and reconfigure from scratch.

'Failed to initiate user data backup': File History Service didn't start or a scheduled task failed to execute. Check services.msc to verify File History Service is Running, and taskschd.msc to verify FileHistory tasks are Enabled.

File History vs. Windows 11's Backup App: Which Should You Use?

Windows 11 includes both File History (legacy, local-only versioning) and a newer Backup app (Settings → System → Storage → Backup, integrating OneDrive cloud backup). For most users relying on automatic local backups to an external drive, File History remains simpler and more transparent. You control exactly where backups go and when they run. However, if you want cloud redundancy or prefer Microsoft's newer backup infrastructure, the Backup app or OneDrive integration works well too. You don't need both - pick one and configure it properly. If you choose File History, follow the fixes above to ensure it's actually running.

ℹ️ If File History continues to fail even after trying all three solutions above, and you need reliable automated backups without ongoing troubleshooting, consider using dedicated backup clone software. These tools handle scheduling, versioning, and drive management more robustly than File History's built-in mechanisms, and recover from drive disconnects more gracefully.

File History Not Backing Up Automatically: Summary

File History not backing up automatically is almost always fixable in under 30 minutes. Start with Solution 1 (reselect your backup drive after assigning it a fixed drive letter) - this solves 70-85% of cases. If that fails, Solution 2 (reset the File History cache) clears corrupted configuration. If you're still seeing failures, Solution 3 (fix permissions and verify File History Service) addresses permission and service issues. Check Event Viewer for specific error codes to guide your next step. Once fixed, follow the prevention tips to keep automatic backups working: assign fixed drive letters, keep your backup drive powered on during backup windows, and monitor 'Last run' timestamps monthly. File History automatic backups are reliable once properly configured - they just need the right diagnosis when they break.

Frequently Asked Questions

Manual 'Run now' executes immediately while you're present, but automatic backups depend on scheduled tasks and the File History Service triggering correctly. Common causes: backup drive unavailable at scheduled time (USB asleep or network unreachable), File History Service not starting, or scheduled tasks disabled. Check Task Scheduler for FileHistory tasks and verify they're enabled.

No. Deleting the cache at C:\\Users\\<username>\\AppData\\Local\\Microsoft\\Windows\\FileHistory removes only local configuration and metadata. Actual backed-up files remain in FileHistory\\Data on your backup drive. File History may not display old versions in its interface until it rebuilds the database, but files themselves are safe and recoverable manually from the backup drive.

Windows assigns drive letters dynamically based on connection order. Fix this: Open Disk Management (diskmgmt.msc), right-click your backup drive, select 'Change Drive Letter and Paths', click 'Change', and assign a letter near the alphabet end (Y: or Z:) that won't conflict. This persists across reboots and reconnections. Then reselect the drive in File History settings.

Yes. File History supports network shares via UNC paths (\\\\NAS-name\\backup-folder). Requirements: network location must be accessible when backups run, you must have Read/Write permissions, share must support SMB 2.0 or later, and credentials must be saved in Windows Credential Manager. For reliability, use IP address rather than computer name and ensure NAS is always powered on.

Error 80070005 is 'Access Denied', meaning File History lacks write permissions to the backup location. Causes: your user account lacks Full Control NTFS permissions, SYSTEM account lacks permissions, network share permissions too restrictive, or backup drive is write-protected. Fix by verifying both your user and SYSTEM have Full Control in the backup drive's Security tab properties.