Yellow bird looking on Reconnect your File History drive toast notification

Fixing “Your File History drive was disconnected for too long” errors

Windows Backup in Windows 10, intermittently known as File History since Windows 8, can get a bit grumpy if you abruptly disconnect your backup drive or interrupt backups. Here is how to resolve issues with Windows Backup resulting in hourly prompts to reconnect the backup disk.

As with many error messages in Windows, this one can be quite misleading. The full toast notification message reads:

“Reconnect your drive. Your File History drive was disconnected for too long. Reconnect it and then tap or click to keep saving copies of your files.”

If you follow the prompt and click on the toast notification, you will instruct Windows Backup to try backing up again. This may trigger the same toast notification to reappear again and again.

The error will pop up every hour, or more often if you’ve configured more frequent backup runs, when Windows attempts to run the scheduled backup process. The error says the drive has been “disconnected”, but it could also mean that the either the disk or the file system is corrupt.

Reconnect your File History drive.

Reconnect your drive, toast notification

You may still get this error message even if your backup disk is connected and even if it has remained connected for days or weeks. If you’ve checked that the disk is in fact connected and that you an open it from the list in This PC (formerly My Computer) in the Windows File Explorer, then what the error actually means is that there is an undefined problem with the disk or file system.

Assuming your backup disk is indeed connected and you can access it through This Computer, than the disk may be corrupt or otherwise be in a failed state. The disk and file system problems that affect File History can be divided in to two main categories:

  • Permissions
    You can get problems with permissions if another user have tried to force-entry to your backup disk, after you’ve connected it to another PC, or when ongoing backups are interrupted.
  • Corruption
    Disk corruption can happen when you connect the backup disk to another PC, disconnect it while a backup is in progress, or if it’s getting old.

Luckily, the fix for both issues is the same so we don’t need to identify which issue your disk may be experiencing to proceed. To attempt to resolve any disk or permission problems, follow these steps:

  1. Right-click on the Start menu and choose Command Prompt (Admin) from the menu
  2. Type in “chkdisk.exe /F B:” (without quotes, where B is the drive letter of your backup disk; you can find this by looking for your disk in This PC/My Computer)
  3. Press Enter and allow the command time to run

The command can take quite some time to finish depending on the size of the backup disk, network conditions, etc. When the command has finished, look through the text on the screen and look for “bad sectors”. The value in front of it should be 0. If you do have bad sectors on your disk (a value higher than 0), then the disk may be physically damaged or have started to deteriorate from old age. Disks with bad sectors should not be used for backup purposes and needs to be replaced.

Other critical disk errors may be shown in the output from the command you run, so skim through the output and look for anything saying “critical” or “warning”.

Unless you see any bad sectors or critical problems, you can try backing up again by opening the Settings app and going to Updates & security: Backup: More options, and clicking the ‘Back up now’ button.

If the problem persists then it may not be a fault with the backup disk, but rather a problem with the staging area directory where Windows temporarily copies files to be backed up prior to copying them over to your backup disk. You can clean the staging area, but you will then loose any files from your backup that haven’t yet been copied over to your backup disk. This can clear up some problems that

Press the Windows key and R, type in “%LOCALAPPDATA%\Microsoft\Windows\FileHistory\” (without quotes), and press Enter. Confirm that you have one Configuration and one Data directory on screen. Open up the Data directory, select all the contents within it, and press Delete. Restart your PC, and try backing up again.


If the problem still persists, then you can try formatting the backup disk, and configuring Windows Backup from scratch. This will delete all previous versions of your documents and remove all backups! However, it may be required as a last resort if the above troubleshooting didn’t resolve your problem.


The error discussed in this tutorial will appear in the Windows Event Log Viewer with the following entry:

Event ID: 204 issued from Microsoft-Windows-FileHistory-Core
Message: Unusual condition was encountered during finalization of a backup cycle for configuration C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config

Feature image based on a photo © 2016 Boris Smokrovic.

3 thoughts on “Fixing “Your File History drive was disconnected for too long” errors”

    1. But don’t you want it to be automated? and include revision control and file versioning?

      Windows Backup is quite lacking, but it’s much better than manually having to remember to backup and keep different versions of your files.

      1. yeah, well, i have a script which runs by cron and uses magic of `rsync –link-dest` – I can’t explain in one sentence, but it’s basically incremental-like backups (which transfers and keeps only new and modified files), where I can delete any single version without affecting other versions – because unchanged files are copied as hardlinks from previous backup.

        The idea is well explained in rsync’s man page (search for link-dest), but I also tried to explain it in this blog post:
        http://alexey.shpakovsky.ru/en/rsync-backups.html

        Yes, in case of Windows machine, it requires you to install cygwin, rsync, and start it via Windows Task Schedulter, but hopefully with Windows 10 Linux subsystem it would be better. 🙂

        The point of my previous comment was that it seems that in this case solution is more robust than in case of Windows Backup. However, that script already have several bugs fixed, one of which just wiped the whole backup folder for me when I ran out of space. Quite handy, but I’m contradicting myself here. Copying files by cron is not as easy as it looks!

Leave a Reply

Your email address will not be published. Be courteous and on-topic. Comments are moderated prior to publication.