The File History drive disconnected error often does not mean your drive is unplugged. The message “Your File History drive was disconnected for too long” can be misleading, and it can also point to a corrupt disk or file system. [1] It also helps to read How to Reconnect a File History Drive in Windows 11 and 10.
The warning can come back every hour, or more often if you have set File History to back up more frequently, because that is when Windows tries to run the scheduled backup. [1] You may see it even when the drive has been connected for days or weeks and opens normally from This PC in File Explorer. [1]
The quick fix is to unplug the drive, plug it back in, click the notification, and reselect the drive in File History. The rest of this article covers the cable, drive letter and drive health checks to try if the message keeps returning.
Could the cable, port or power be the problem?
Yes, a loose cable, a flaky port or a drive that loses power can trigger this error, and the fix is usually quick. File History can get “grumpy” when you abruptly disconnect the backup drive or interrupt a backup in progress. [1] A drive pulled out mid-backup, or one that drops off when a laptop sleeps, is enough to start the warnings.
Try a different cable, port or connection
Rule out the hardware path first, one change at a time:
Swap the USB cable for another one, ideally a short one that you know works.
Move the drive to a different port. A port directly on the computer is a better test than one on the front of a case.
Skip any USB hub or dock and plug the drive straight into the computer. Hubs can share power between devices, so a drive that works on its own may drop out behind one.
If the drive has its own power adapter, make sure it is plugged in and switched on.
After each change, give Windows a few seconds to detect the drive before you test again.
Check the drive appears in File Explorer
Open File Explorer, choose This PC, and look for the drive in the list. If it shows up and you can open it, Windows sees it and the connection is probably fine. [1]
If it appears and opens but you still get the message, the problem is not the cable. The error can appear even when the disk has stayed connected for days or weeks, and it may point to a problem with the disk or its file system. [1]
If the drive does not appear at all, keep trying other cables and ports, and try the drive on another computer. A drive that fails everywhere is a drive problem, not a cable one.
Did the drive letter change?
A changed drive letter can make File History treat a plugged-in drive as missing, so check the letter first. If the drive was E: yesterday and shows up as F: today, File History may no longer find it.
Check the letter
Open File Explorer, choose This PC, and look at the letter next to your backup drive. If you want a second view, right-click Start, open Disk Management, and find the drive in the volume list. The letter appears in parentheses beside the volume name.
If the drive does not show up in either place, the problem is more likely the connection than the letter. That case belongs to the cable and port checks.
Reselect the drive if File History does not recognize it
When the drive is visible but File History still reports a problem, tell File History to use it again. Search for File History in the Start menu, open it, and choose the drive from the drive list, as you would when selecting a destination for the first time. A drive that was switched off or not recognized can leave File History unable to back up until you do this. [2]
If File History says it is off, a quick fix is to open File History from Start, click Configure File History settings if you see “No file history was found”, and then click Turn on. [2]
Network and mapped drives can drop too
Backups stored on a network location can fail for the same reason. The disconnected message is tied to external drives, but also to mapped and network drives. [3] A mapped drive can vanish if the other computer sleeps, the network connection drops, or the share is renamed.
For example, if your backups live on a shared folder mapped as Z:, open File Explorer and confirm that Z: opens before you reselect it in File History. If it does not open, restore the network connection first, then choose the drive again.
Is the drive itself failing or corrupted?
Yes, it can be. The “disconnected” message sometimes means the disk or its file system is corrupt, even when the drive is plugged in and shows up in File Explorer. [1] If you have already confirmed the connection, a drive check is the next step.
Run a disk check with chkdsk
Before you run a repair scan, copy the important files off the backup drive to another disk. A repair scan can change the drive’s file system, and if the drive is already unhealthy, you want a second copy of your data first.
Then open a Command Prompt as administrator and run this, replacing B: with your File History drive’s letter:
chkdsk.exe /F B:
The /F switch tells chkdsk to fix errors it finds on the drive. B: is the drive to scan. When it finishes, reselect the drive in File History so backups can resume. You may also find this useful: How to Switch File History to a New Drive in Windows.
What bad sectors tell you
Bad sectors are damaged spots on the disk that cannot reliably hold data. A repair can mark them so Windows avoids them, but it cannot make the disk healthy again.
A practical example: you run the scan, it finishes cleanly, and File History works for weeks. That points to a one-time file system problem, now fixed. If the scan reports bad sectors, or the error comes back soon after, plan to move your backups to a different drive rather than keep trusting this one.
How do I fix it step by step?
Work through these steps in order, and stop as soon as the warning goes away.
Reconnect the drive and click the notification. Unplug the backup drive, plug it back in, then click the toast that reads “Reconnect your drive.” Clicking it tells Windows to try the backup again. [1] If the same toast returns, move on to the next step.
Reselect the drive in File History. Open the File History settings and choose your backup drive again so Windows re-links to it. On Windows 11, search for File History in the Start menu, which opens the classic Control Panel page. On Windows 10, you can also reach it through Settings > Update & Security > Backup. [4]
Scan the drive for errors. The error can also mean the disk or file system is corrupt, even when the drive shows up in File Explorer. [1] Open a Command Prompt as administrator and run this command:
chkdsk.exe /F B:
Replace B: with your drive’s letter. The /F switch tells chkdsk to fix errors it finds on that drive. [1] When the scan finishes, reselect the drive in File History as in step 2.
Windows 11 versus Windows 10
Windows 11 has no separate File History page in Settings, so you reach it through Control Panel or search, as in step 2. [4]
Windows 10 includes File History under Settings > Update & Security > Backup, and the troubleshooting steps above apply there too. [1] Windows 10 has also reached its end of support, and Microsoft offers Extended Security Updates (ESU) enrollment for users who want to keep receiving updates. [5]
When should I replace the drive or get help?
Replace the drive, or ask for help, when the error keeps coming back after you have reseated the drive, checked the cable and port, and reselected it in File History. At that point the message is probably not about a loose connection at all.
Signs the drive is the problem
The error says the drive was “disconnected,” but it can also mean the disk or its file system is corrupt. [1] You may see it even when the drive has stayed plugged in for days or weeks and opens normally from This PC in File Explorer. [1] In that case, Windows is reporting an undefined problem with the disk or file system. [1]
If a chkdsk.exe /F B: scan reports bad sectors, treat the drive as unreliable. [1] A backup drive with bad sectors can fail without warning, so it is no longer a safe home for your only copy of your files.
Another sign is hourly prompts that keep returning. The error appears every hour, or more often if you set more frequent backup runs. [1] If clicking the notification only brings it back again and again, the quick fixes have not reached the cause. [1]
Moving File History to a new drive
The lasting solution for a drive that keeps failing is to point File History at a different drive. [1] Here is the general approach:
Connect the new drive and confirm it shows up in File Explorer.
Open the File History settings.
Turn File History off, then choose the new drive as your backup drive.
Turn File History back on so scheduled backups resume.
A drive that is large enough for your folders and used only for backups is a sensible choice. Backups made to a network share are not affected by this particular disk problem, so a network location is another option. [1]
If a brand-new drive shows the same error, or you cannot tell whether the drive or the computer is at fault, a local IT professional or the drive maker’s support can test both.
What should I remember?
Work from the simplest cause to the most serious: the connection first, then the drive letter, then the health of the drive. Most “disconnected” warnings are solved before the last step. The message can be misleading, since it can also point to a corrupt disk or file system rather than a missing drive. [1]
Once the drive is working again, reselect it in File History and click the notification so Windows tries to back up again. [1] Then watch for the next hourly run: if the prompt stays gone, your backups have resumed.
