Windows 11 File History Backup Not Working

Windows 11 File History Backup Not Working

You turned on File History expecting it to quietly back up your files to an external or network drive on a regular schedule, and now something about that isn’t happening the way it should — it won’t turn on at all, it throws an error the moment you try to enable it, or it seemed to be running fine for a while and then just stopped without telling you.

This is a completely separate feature from OneDrive. OneDrive syncs files to the cloud in something close to real time; File History is Windows’ own local backup tool, saving versioned copies of your files to a drive you plug in or connect to on your network, on whatever schedule you’ve set. A problem with one has nothing to do with the other, and the fixes don’t overlap.

Quick explanation: this guide covers File History failing to turn on or showing an error immediately, confirming the backup drive is actually connected and recognized correctly, permissions problems on the drive silently blocking backups, File History stopping in the background with no error shown, files that seem to be missing from a completed backup, and how to actually confirm a backup is trustworthy before you need it.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

File History backup problems on Windows 11 almost always trace back to the backup drive itself — it’s disconnected, running low on space, formatted with a file system File History can’t write to properly, or the account doesn’t have full write permissions on it. A backup that silently stops running in the background, with no error ever shown, is usually caused by exactly the same drive-connection issues happening quietly rather than File History itself being broken. Reconnecting the drive, confirming it has free space and correct permissions, and re-enabling File History from Settings > System > Storage > Advanced storage settings > Backup options resolves the large majority of cases.

File History Won’t Turn On or Errors Immediately

If File History refuses to turn on at all, or shows an error dialog the moment you try to enable it, the most common cause is that Windows can’t find a valid drive to use as the backup destination — either no external or network drive is currently connected, or the one you’re pointing it to isn’t formatted in a way File History can use.
File History needs an NTFS-formatted drive to work correctly; a drive formatted as FAT32 or exFAT, which is common on drives fresh out of the box or ones previously used with a Mac, will either be rejected outright or cause the feature to behave unpredictably once turned on. Reformatting the drive to NTFS, after confirming nothing important is on it that hasn’t already been backed up elsewhere, resolves this specific cause.
Fixyfier’s Windows Tools section includes a Disk Management shortcut, which shows exactly how a connected drive is currently formatted and lets you reformat it directly if that turns out to be what’s blocking File History from accepting it as a backup destination.

Confirming the Backup Drive Is Actually Connected and Recognized

A drive that looks connected — the light is on, it shows up in File Explorer — isn’t always actually reachable the way Windows’ backup services expect. A loose USB connection, a network drive that dropped off briefly, or a drive letter that changed after a reboot can all make File History quietly fail to reach a drive it was previously backing up to fine.
Checking the drive’s actual reported free space and connection details directly, rather than just glancing at it in File Explorer, is a fast way to confirm Windows genuinely sees it as healthy before assuming the problem is something more complicated with File History itself.
Get-CimInstance Win32_LogicalDisk | Select-Object DeviceID, DriveType, FreeSpace, Size
That command lists every drive Windows currently recognizes along with its free space, which quickly confirms whether the backup drive is actually visible to the system and has enough room left, rather than having silently run out of space or dropped off the connection entirely.

Permissions on the Backup Drive Silently Blocking File History

If the drive was previously used with a different Windows user account, plugged in on another PC, or had its permissions changed at some point, your current account may no longer have full write access to it — and File History can fail or silently stop running without clearly surfacing a permissions error as the cause.
This is easy to overlook because the symptom often just looks like File History “not working” in a general sense, rather than pointing specifically at permissions. Right-clicking the drive in File Explorer and checking its security settings to confirm your account has full read/write access is worth doing before looking anywhere else.
Fixyfier’s Windows Tools section includes an Open Advanced User Accounts tool, useful for confirming exactly which account you’re currently signed in with and what privilege level it has, which matters directly here since a standard account without administrator rights can run into exactly this kind of silent permissions block.

File History Stops Running in the Background With No Error Shown

The most frustrating version of this problem is File History that seemed to work fine for weeks or months and then quietly stopped, with no error dialog, no notification, and no obvious sign anything had changed — you only find out when you actually need a backup and discover the most recent one is older than expected.
This almost always traces back to the same drive-connection and permissions causes covered above happening intermittently rather than File History’s own scheduling breaking — a drive that was disconnected during a scheduled backup window, a sleep or hibernate cycle that interrupted a backup mid-run, or a network drive that briefly dropped off the network at the wrong moment.
Checking the last successful backup time under Settings > System > Storage > Advanced storage settings > Backup options and comparing it against when the drive was actually connected and awake is the most direct way to spot the pattern behind an intermittent stoppage like this.
NordVPN
One Thing Worth Knowing

Backing Up to a Network Drive on an Unfamiliar Connection

If your File History backup target is a network drive you sometimes reach over an unfamiliar Wi-Fi network — a shared workspace, a hotel, a friend's router — NordVPN keeps that connection encrypted while your backup, which can contain years of personal files, is actually in transit.

Secure This Connection

Files That Seem to Be Missing From a Completed Backup

File History runs successfully and reports no error, but when you go looking for a specific file or folder in the backup, it isn’t there. This is usually not a sign of backup failure — File History only backs up folders you’ve explicitly added or that fall under its default set (things like your user profile’s Documents, Desktop, and Pictures folders), and anything outside that scope simply never gets included.
Files actively open and locked by another program at the exact moment a scheduled backup runs can also get skipped silently for that one cycle, picked up correctly on the next run instead — which can look like a missing file if you check right after closing something you were working on.
Fixyfier’s Fix & Repair section includes a Save System Logs tool, useful for checking whether File History logged anything about a skipped file or folder during a specific backup run, which helps confirm whether something was actually excluded on purpose versus genuinely failing to back up.

Confirming a Backup Actually Works Before You Need It

A backup that runs on schedule without errors isn’t automatically a backup you can trust — the only real confirmation is actually restoring a file from it and checking that it opens correctly, which is a step most people skip until the moment they urgently need a backup to work.
Using File History’s own restore interface to pull back a file you don’t currently need — something low-stakes, just to test the process — confirms both that backups are actually completing and that the files inside them are intact and usable, rather than assuming everything’s fine because no error has appeared.
Doing this check periodically, not just once when you first set File History up, catches a drive or permissions problem that developed later on before it turns into a real loss rather than after.

Frequently Asked Questions

Is File History the same thing as OneDrive backup?

No, they’re separate features entirely. OneDrive syncs files to Microsoft’s cloud storage in close to real time and requires a Microsoft account and internet connection; File History backs up versioned copies of your files locally to an external or network drive on a schedule, with no cloud account involved at all. A problem with one doesn’t affect the other, and they can be used together or independently.

Why did File History suddenly ask me to choose a new drive?

This typically happens when Windows can no longer find the drive it was previously configured to use — most often because it’s disconnected, was reformatted, or its drive letter changed. Reconnecting the original drive usually resolves it without needing to actually pick a new one, unless that drive is genuinely gone or failed.

Does File History back up everything on my PC?

No. By default it covers your user profile’s main personal folders — Documents, Desktop, Pictures, and similar — not your entire drive or installed applications. Additional folders can be added manually, but a full system backup or drive image is a different kind of backup that File History isn’t designed to provide.

Let Fixyfier Help You Confirm Your Backup Setup Is Solid

Fixyfier’s Windows Tools section puts Disk Management a click away for checking a backup drive’s format and health, the same section includes Open Advanced User Accounts for confirming account permissions, and its Fix & Repair section covers Save System Logs for spotting exactly what happened during a backup that didn’t go as expected.
Get Fixyfier from the Microsoft Store