Windows File History Stopped. Don't Wipe the Backup Drive.

Written and maintained by the Desert Data Recovery lab team. · Updated October 16, 2026

We already wrote about a backup that is actually a second copy, about OneDrive files that were never on the disk, and about a Storage Spaces pool you should not delete. This page is the Windows feature that was supposed to be the local history. It still lives in Control Panel. It does not announce, in a way most people notice, the day it stopped writing.

The panel can say on while the copies stopped

Microsoft's current File History article still applies to Windows 11 and Windows 10. Setup is Control Panel, System and Security, "Save backup copies of your files with File History," then Turn on. The same company's known-issue note for the September 8, 2026 security update KB5124008 uses the path Control Panel > System and Security > File History, and it names the field to read: the Last Backup timestamp.

That note is specific. KB5124008 is the update for Windows 11 versions 24H2 and 25H2, OS builds 26200.9445 and 26100.9445. Microsoft says that after installing it, some customers using File History might be unable to create or update backups. Affected devices might show "Reconnect your drive" even when a compatible backup drive is connected and working. The Last Backup timestamp might not update. Previously backed-up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll. Microsoft does not name which Event Viewer log those crashes land in on that page, so we will not invent a click-path under Applications and Services Logs.

Microsoft's resolution, added to that page on September 22, 2026, says the issue is resolved in Windows updates released on and after that date, such as KB5124010. KB5124010 is the September 22, 2026 preview for the same two versions (OS builds 26200.9550 and 26100.9550), and its notes say it addresses File History failing to back up or restore to an external drive or network location, including the false reconnect message. The same KB5124008 page says Windows 11 version 24H2 Home and Pro reach the end of updates on October 13, 2026. If that PC has not taken an update from September 22 or later, check Windows Update. Installing the fix lets new copies run again. It does not write the weeks the feature already skipped.

The reconnect wording is older than this bug. Microsoft's reconnect article, for Windows 11 and Windows 10, says you may see that the File History drive has been disconnected for too long. The steps there are: plug the external drive back in, or reselect the network location, then wait for the next scheduled backup or open File History and choose Run now. A drive that spent a month in a drawer produces the same stale Last Backup time without any September update involved. The message is not the diagnosis. The timestamp is.

The copies are a folder, with the date in the filename

File History writes ordinary files to the drive or network location you selected. The tree is FileHistory\<user name>\<computer name>\Data. Under Data, a folder named for the source drive letter holds the original path. A Microsoft Q&A answer that walks through a live backup shows the shape: F:\FileHistory\Ramesh\OPTIPLEX-7010\Data\C\Users\Ramesh\Desktop, and names like CMD (RunAsSystem) (2025_04_28 04_25_58 UTC).lnk. The stamp is UTC, inserted before the extension: year, month, day, then hour, minute, second.

That stamp is independent of the Control Panel clock the September bug can freeze. Use both. File History saves copies of files that changed, so one old document does not prove the job died. Pick a file you saved last week. If the newest stamp on it, and the newest stamps elsewhere in Data, are from August, August is the backup. A folder named $OF directly under Data is part of the same set: copies whose full destination path was too long to store under the normal name, kept there under numbered names. It is not leftover junk. Leave it.

Microsoft's File History page says the feature backs up libraries: Documents, Pictures, Videos, and Music, plus custom libraries. The setup steps on that same page name Documents, Pictures, Videos, and Desktop, and say other folders are added by including them in a library. It is not an image of the disk. Windows itself, installed programs, and a folder you never included are not in that tree. A file that lived only as an online-only OneDrive placeholder was never on the PC to be copied. That is the cloud-icon problem, and the account is where you check it.

Settings is a different product. Microsoft's Windows Backup article says you turn folders on in Settings > Accounts > Windows backup, or in the Windows Backup app, and those folders sync to OneDrive. A healthy Windows Backup page does not update the File History timestamp, and it does not fill the FileHistory folder. OneDrive can also mirror a deletion. The separate copy, on another device, with one of them offsite, is what we mean by 3-2-1.

Formatting the backup drive is how the history disappears

The older versions are the files in that FileHistory folder. Formatting the drive, wiping it, or deleting the folder removes them. Microsoft's setup page says that if you are prompted while selecting a drive, you can move existing files to the new drive or start fresh. Start fresh begins a new set. It does not import the old copies into it. People choose it, or they format the disk, because the panel is stuck on reconnect and a forum post called that a reset. The error can clear. The August copies are what went with it.

Two quieter ways to lose the same files. File History's Clean up versions control, under Advanced settings, deletes older saved versions. Changing how long versions are kept, including letting the drive delete the oldest copies when it fills, does the same job on a delay. Neither one repairs a backup that stopped. Both of them target the copies you would want if the PC's disk fails next month.

The configuration on the PC is a different folder. An older Microsoft support article documents File History's configuration under the user profile at AppData\Local\Microsoft\Windows\FileHistory\Configuration. Deleting that resets the PC's record of the job. It does not recreate missed days, and it is the step that usually comes just before Select drive and start fresh. Leave it. Beside Data on the backup drive, the Configuration folder is File History's catalog for that target. The files you can open are under Data. Do not delete either catalog to "rebuild" the backup.

If Windows offers to initialize or format the backup disk when you plug it in, cancel the dialog. Initialize Disk writes a new partition table. The FileHistory folder is on the volume that table currently describes. A disk Windows does not recognize is not an empty disk.

Microsoft's restore steps are a write in the other direction. Restore previous versions, then Restore, replaces the current file or folder on the computer, and Microsoft says that replacement cannot be undone. On a healthy PC, restoring one file you just overwrote is what the feature is for. On a drive that is already failing, restoring a tree onto it writes the failing disk. Copy the FileHistory folder to a third disk instead. Copy, do not move. Do not copy it onto the drive that is dying.

If the main drive is failing, stop reading it

Run now is the right button on Microsoft's reconnect page when the PC is fine and the backup drive was simply unplugged. It reads the files on the PC and writes new copies to the backup target. If the main drive is clicking, grinding, freezing, disappearing, or showing RAW, that read is another pass over a drive that is getting worse. Power it down. Unplug an external drive. Shut the PC off if the failing disk is internal. Do not reboot to see if File History will catch up. See what a clicking drive means.

The backup drive is a separate question. If that drive spins up, mounts, and you can open the FileHistory folder, those files are readable data. Copy the folder to a third disk before you change File History settings, reselect the target, or let a cleanup run. The copy is the insurance against the next click on the PC and against a reset of the backup. If the backup drive is also clicking, not spinning, or not staying detected, stop. It is a second failing drive, not a folder you should keep retrying. Power it down too.

A few dialogs that show up in the same afternoon, and that do not fix a stale history:

• CHKDSK, Scan and repair, Error Checking. Those write the failing filesystem. CHKDSK /f is a write.
• Startup Repair. Preparing Automatic Repair writes boot and filesystem metadata on a disk that was only trying to boot. Startup Repair is a write.
• Delete Pool, if the backup target was a Storage Spaces pool. A Failed pool is not an empty pool, and Delete Pool writes the members. That is the Storage Spaces page. File History's folder, if it was on that virtual disk, is inside the pool. Do not delete the pool to "free" the drive for a new File History target.
• A new backup onto the same disks after a format. That uses the only remaining copies as blank media.

What to do right now

1. Read the date before you change anything. Control Panel > System and Security > File History. Write down the Last Backup time, the target drive or network path, and any reconnect text. If the PC's own drive is already failing, skip the rest of the clicks on that PC and go to the next step you can do from another machine.
2. Open the FileHistory folder on the backup drive or the network share. Look under your user name, the computer name, and Data. Sort by the timestamps in the filenames. Note the newest stamp on a file you know you changed recently. That pair of dates — the panel, and the filenames — is the backup you actually have.
3. Copy that FileHistory folder to a third disk if the backup drive is healthy. A normal file copy. Not a format, not a move, not a restore onto the PC, not Clean up versions, not start fresh. Open two or three of the copied files and confirm they open.
4. If the main drive is healthy and you only discovered the history was stale, install the latest Windows update Microsoft is offering. KB5124010 is the preview Microsoft names for the September File History bug on 24H2 and 25H2. Afterward, read the Last Backup time again once a new run has finished. The gap between the old stamps and today is still a gap.
5. If the main drive is failing, leave it off. Do not click Run now, do not run CHKDSK, do not let Startup Repair finish, and do not initialize either disk. Photograph the File History screen if you can still see it. Pack the failing drive, and the backup drive if you are not sure it is healthy. How to ship a failed drive. If BitLocker is on, bring the key. The key unlocks the volume. It does not fill in copies File History never made.

How a lab handles it

We do not turn File History back on against a dying disk to "let it finish." We do not format the backup drive, delete the FileHistory folder, or start a new set on those platters so the Control Panel error goes away. We do not run CHKDSK or Startup Repair on the drive that failed.

If the PC's drive is failing, it gets imaged write-blocked, as far as it will read, and the file work happens on the copy. The FileHistory folder is a separate pile of files. When the backup drive is healthy, copying that folder off is a file copy, and it should happen before the failing drive is asked to do anything else. When the backup drive is failing too, it is a second image, with the same rule: stop retrying it. A backup that stopped in August can still hold the August copies. It cannot hold the files that only ever existed on the PC after that date. Those are on the failing disk, or they are gone.

The public case log has no File History job. We will not invent one. We don't advertise a success rate, and we can't promise a turnaround from a Last Backup line. The evaluation is at Desert Data Recovery, in the Phoenix area. The number on this page is (602) 686-2622. For the drive itself, see laptop data recovery and external hard drive data recovery.