Your File History drive has disconnected because Windows lost the drive's registration, the network share is asleep, or the drive letter shifted. Reopen Control Panel > File History, click "Select drive," and re-add the exact drive; if it refuses to appear, run services.msc and restart the "File History Service." Most one-off drops clear at that point. The stubborn cases live in the registry and in how Windows tracks removable drives, and those are the ones worth understanding before you click anything.
The short version: File History is a Windows 8-era backup tool that Microsoft still ships in Windows 10 and Windows 11, but it has not received meaningful development in years. According to Microsoft's own File History documentation, the feature watches Libraries, Desktop, Contacts, and Favorites by default and writes copies every hour. It stores those copies on a separate drive, and when that drive vanishes from Windows' view — unplugged, remounted under a new letter, or blocked by a sleeping NAS — File History stops backing up and shows a "reconnect your drive" warning. Keep that architecture in mind, because every fix below follows from it.
What "Reconnect Your Drive" Actually Means in File History
The message is literal. File History keeps a database on the destination drive that records which files it has copied and when. Windows stores the drive's identity alongside it, tied to the volume, not just the letter.
When you plug the drive back in and File History still complains, the disconnect is usually one of four things: the drive is mounted under a different letter than the one File History remembers, the network share is offline or the credentials expired, the drive is full or write-protected, or the File History Service has stopped. Microsoft's support pages for Windows 10 and Windows 11 describe the same four causes, and the order matters because the cheap fixes come first.
One detail Microsoft's pages gloss over: File History will not use a drive that is also holding your Windows installation. If you partitioned a single internal disk and pointed File History at the second partition, that configuration can work initially and then fail after a Windows update reassigns disk numbers. An external USB drive or a network location avoids the problem entirely.
Also worth knowing before you troubleshoot: File History is not the same as System Restore, and it is not the same as a full disk image. It copies files, not the operating system. If your goal is a bare-metal restore, File History alone will not get you there, and no amount of reconnecting changes that.
Reconnect Your File History Drive in Six Steps
Work through these in order and stop as soon as the warning clears. Each step addresses a different failure layer, from the user interface down to the service.
1: Open Control Panel (not Settings) and go to System and Security > File History. Check whether the drive appears under "Select drive." 2: If the drive is listed but marked disconnected, select it and click "Turn on." Windows re-registers the drive without touching your existing backup history. 3: If the drive is missing, click "Select drive" > "Refresh," then pick the drive from the list. Do not click "Add network location" unless the drive genuinely lives on a share. 4: Confirm in File Explorer that the drive letter matches what File History expects. If the letter changed, reassign the original letter in Disk Management before retrying. 5: Open services.msc, find "File History Service," and restart it. Set its startup type to Automatic if it is set to Manual. 6: Reboot once. A reboot forces Windows to re-enumerate removable drives and often clears a stale mount.
If none of that works, the problem is almost certainly in the registry, and the next section covers it. Do not delete the FileHistory folder on the destination drive while troubleshooting — that folder holds your version history, and removing it turns a fixable connection problem into permanent data loss.
One failure case worth flagging: on some systems, step 2 succeeds visually but the backup never resumes because the drive's free space has dropped below the threshold File History needs. File History does not warn you clearly about this. Check free space on the destination before assuming the reconnect failed.
The Registry Key That Keeps Forgetting Your Drive
File History stores its drive configuration under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\FileHistory in a value called ProtectedRoots and a related set of drive entries. When these entries point at a volume that no longer exists, Windows keeps showing the reconnect prompt even after you re-add the drive.
Before editing anything, export the key. Right-click the FileHistory folder in Registry Editor, choose Export, and save the .reg file somewhere you'll remember. Then check whether the configured drive path matches the drive's current mount point. If the path is stale, you have two clean options: delete the stale entry through the File History interface by removing and re-adding the drive, or edit the registry value to point at the correct path.
Microsoft does not document this registry location in its consumer support articles, which is why most guides skip it. The safer route is always to remove and re-add the drive through Control Panel, because that forces Windows to rewrite the registry entries itself. Manual registry edits are for the case where the interface refuses to list the drive at all.
If you're on a domain-joined machine, Group Policy can override File History settings and re-point the drive to a share your account cannot reach. Check gpedit.msc under Computer Configuration > Administrative Templates > Windows Components > File History before assuming the problem is local. This is a common cause in managed workplace laptops and almost never mentioned in consumer troubleshooting threads.
Network Share vs External USB: Which Reconnects Cleanly
Network shares drop more often than USB drives, and the reason is credential and sleep behavior rather than File History itself. A NAS that spins down its drives, or a share that requires re-authentication after a password change, will break the connection silently while File History keeps reporting a healthy schedule.
| Factor | External USB drive | Network share (SMB) |
|---|---|---|
| Default reconnect reliability | High; re-enumerates on plug-in | Medium; depends on NAS sleep and credentials |
| Credential expiry risk | None | Yes; password changes break it |
| Drive letter stability | Changes if plugged into a different port | Fixed by UNC path |
| Typical failure symptom | "Drive not found" after reboot | Backup silently stops; warning appears later |
| Fix effort | Reassign letter or restart service | Re-enter credentials or wake the NAS |
The verdict is straightforward. If your machine stays in one place and you can keep a USB drive attached, use USB — it reconnects without credentials and survives reboots. If you need off-machine backup, a network share is the right call, but plan on re-entering credentials after any password change and disabling drive sleep on the NAS.
Windows 11 adds a wrinkle here that Windows 10 users don't hit: the Settings app surfaces some File History controls that Control Panel handles differently, and the two can disagree about which drive is active. When in doubt, trust Control Panel, because that is where File History's actual configuration lives regardless of what Settings displays.
When the Drive Is Full, Read-Only, or BitLocker-Locked
File History stops writing the moment the destination drive fills up, and the warning it shows is the same generic reconnect message. This is the most misdiagnosed cause on the list.
Check free space first. File History does not manage its own storage well; it keeps old versions until the drive is full unless you configure "Keep older versions" under Advanced settings. Microsoft's default is "Until space is needed," which means the feature will happily consume an entire drive. Set a retention period — six months or one year is reasonable — and the drive stops filling.
A read-only drive produces the same symptom. This happens with failing USB flash drives and with SD cards that have flipped their write-protect state. Test by copying a small file to the drive manually; if it fails, the drive is the problem, not File History.
BitLocker is the third case. If the destination drive is BitLocker-encrypted and the volume is locked after a reboot, File History cannot see it until you unlock it. Windows normally auto-unlocks BitLocker drives on the same machine, but that behavior depends on the "Automatically unlock this drive" checkbox being enabled. Verify it in BitLocker Drive Encryption in Control Panel.
Stop the Disconnect From Recurring: Power and Sleep Settings
The most common repeat offender is USB selective suspend. Windows powers down idle USB devices to save energy, and a suspended external drive looks disconnected to File History. The fix takes two minutes.
Open Power Options, choose "Change plan settings" for your active plan, then "Change advanced power settings." Under USB settings > USB selective suspend setting, set it to Disabled for both On battery and Plugged in. Then, under Hard disk > Turn off hard disk after, set a longer interval or "Never" if the machine is a desktop.
For laptops, this trades a small amount of battery life for a backup that actually runs. That is a reasonable trade if the drive holds your only copy of important files. If battery life matters more, schedule File History to run while the laptop is plugged in and accept that backups may skip while on battery.
Network shares need the equivalent treatment on the NAS side. Most consumer NAS units have a drive hibernation setting that spins disks down after 20 to 30 minutes of inactivity. File History running hourly can be enough to keep them awake, but only if the share responds fast enough during the check. Disabling hibernation on the NAS resolves the intermittent "drive not found" pattern that appears roughly every few days.
Reading the Event Log to Find the Real Cause
When the obvious fixes fail, the Event Viewer tells you what actually happened. Open Event Viewer and navigate to Windows Logs > System, then filter for source "FileHistory" or "disk." You'll see entries recording when the drive was connected, when File History last ran a successful backup, and what error code accompanied the failure.
The error codes are specific enough to be useful. A disk error followed by a File History error points at hardware. A credential error points at a network share. A service-start error points at the File History Service itself, which sometimes fails to start after a Windows update and needs its startup type reset manually.
This step is worth the five minutes because it prevents you from applying fixes blindly. The post-update service failure in particular looks identical to a drive problem from the interface but resolves in a completely different place. Windows update history is worth checking alongside the event log — if the failure began right after a cumulative update, that is your likely trigger.
File History vs OneDrive vs Third-Party Backup
File History still works, and it costs nothing beyond the drive. But it has real limits that Microsoft's own documentation acknowledges: no cloud copy, no bare-metal restore, no protection if the destination drive sits next to the machine in a fire, and no ransomware protection worth the name, because a connected drive is writable.
| Tool | Cost model | Protects against drive failure | Protects against ransomware | Restore granularity |
|---|---|---|---|---|
| File History | Free; requires a drive you own | Yes, if the drive is separate | Weak; connected drive is writable | Individual files and versions |
| OneDrive (Microsoft 365) | Subscription | Yes, cloud copy | Yes, with version history | Individual files and versions |
| Third-party image backup | One-time or subscription | Yes | Yes, with offline or immutable copies | Full system or files |
Use File History if you want a free local version history and you already keep the drive separate from the machine. Skip it if you need ransomware resilience or off-site protection — a backup that sits plugged into the same PC does not survive a theft, a fire, or an encryption attack. The sensible combination for most people is File History to a USB drive plus a cloud copy of the irreplaceable files.
FAQ
Why does File History lose my drive after every reboot?
Windows reassigns drive letters to removable devices based on enumeration order, so a drive plugged into a different USB port can come back as a different letter. File History remembers the volume identity, but the interface often fails to remap it automatically. Assigning a fixed letter in Disk Management for that specific drive solves it permanently.
Can I use a partition on my main drive for File History?
It can work, but it is fragile. File History refuses drives that hold the Windows installation, and a second partition on the same physical disk shares that disk's failure risk and can lose its disk number after updates. An external drive is the safer choice.
Does File History still exist in Windows 11?
Yes. Microsoft has kept File History in Windows 11 through the Settings and Control Panel interfaces, and it functions the same as in Windows 10. It has not received major new features, and Microsoft's broader guidance now points users toward OneDrive for cloud backup, but the local feature remains available.
What happens if I delete the FileHistory folder on the drive?
You lose every previous version stored there. File History will start a new backup set from that point forward, but older copies of files are gone. Never delete that folder while troubleshooting a connection problem.
Why does File History say my drive is disconnected when it shows in File Explorer?
File Explorer and File History check drives differently. File History verifies the volume's identity and write access, so a locked BitLocker volume, a read-only card, or a full drive can appear connected in Explorer while failing File History's check. Test by writing a file to the drive manually.
How much space does File History need?
There is no fixed minimum, but plan for at least twice the size of the folders you back up, because File History keeps multiple versions. Microsoft's default retention is "Until space is needed," which consumes the whole drive over time. Set a defined retention period in Advanced settings to cap growth.
Does File History back up to a NAS reliably?
It can, but expect credential and sleep problems. Re-authenticate after any password change, disable drive hibernation on the NAS, and confirm the share uses a UNC path rather than a mapped letter. A mapped letter breaks whenever the mapping is recreated.
Can I run File History and OneDrive together?
Yes, and many people should. File History covers local Libraries and Desktop to an external drive, while OneDrive syncs selected folders to the cloud. They write to different locations and do not conflict, though backing up the same folder twice wastes space.