CSIPE

Published

- 22 min read

Windows Fixed File History. Your Backup Still Needs a Restore Receipt

Windows Backups Online Safety

Books by the author

Compare all 5

As an Amazon Associate I earn from qualifying purchases. Buying through these links costs you nothing extra and helps pay for the blog.

Your backup drive can be plugged in, visible, and perfectly healthy while Windows quietly stops putting new copies on it. That is what some File History users found after installing the September 2026 Windows security update. The reassuring part is that Microsoft released a repair on 22 September. The useful part is what happens next: checking that your own files are moving again.

A green light on an external drive proves that the drive has power. It does not prove that yesterday’s family photos, tax folder, or half-finished novel reached it. File History normally handles that copying in the background, which is exactly why a failure can sit unnoticed. Automatic tools save effort when they work and hide stale results when nobody asks for a receipt.

This incident does not mean Windows backups are pointless, nor does it call for panic or an expensive new product. It gives home users a timely reason to learn one small habit. After installing the repair, create a harmless test file, run File History, confirm the backup time moved, and restore that file. Ten quiet minutes can replace a month of assumption.

What broke after the September update

On 8 September 2026, Microsoft released Windows 11 security update KB5124008 for versions 24H2 and 25H2. Microsoft later added a known issue to the update’s support page: some people using File History could no longer create or update backups after installing it. A connected, compatible drive could produce a false “Reconnect your drive” message, while the “Last Backup” time stopped advancing (Microsoft Support).

The fault could also affect the other half of a backup, getting a file back. Microsoft says previously backed-up files might show “No previous version available,” and some affected computers recorded crashes involving FileHistory.exe and KERNELBASE.dll. Those details matter because they separate this known Windows fault from the ordinary case of a loose cable or a sleeping network drive. The same warning on the screen can come from several different causes.

Independent testing reported the visible failure before Microsoft’s repair arrived. Windows Latest said its File History run failed after the September update and that the problem remained after an emergency update issued for a different Windows fault (Windows Latest). That account does not establish that every updated computer failed. It does confirm that the broken behaviour occurred outside Microsoft’s own description, on a real machine using the feature.

Microsoft released KB5124010 on 22 September 2026 for Windows 11 24H2 and 25H2. Its release notes say the update fixes File History failures involving external drives and network locations, including the incorrect reconnect warning (Microsoft Support). Microsoft published a corresponding 22 September update for Windows 11 26H1, KB5124006, with the same File History repair (Microsoft Support).

As of 23 September 2026, that is the dated shape of the story: the 8 September update introduced the known failure on affected systems, and updates released on or after 22 September carry the fix. Your computer may never have hit the bug. It may already have installed the repair. Neither possibility removes the need to look at the last successful backup, because an article cannot inspect the drive on your desk.

The headline version says Microsoft broke File History and then fixed it. The household version is more specific. A background copy job may have missed days or weeks, and installing repaired software does not travel back in time to create those missing copies. The next successful run closes the gap from this moment forward. Your receipt proves when that happened.

How File History can look present while doing nothing

File History is a Windows feature that keeps changing copies of personal files on another drive or a network location. Microsoft’s current guide describes it as automatic protection for libraries such as Documents, Pictures, Videos, and Music, along with custom libraries you have created (Microsoft Support). If you delete a file or save over a useful version, File History can let you browse back to an earlier copy.

Picture a filing clerk who visits your desk every hour and takes changed pages to a cabinet in another room. You do not watch each trip. You trust the routine, and the cabinet slowly collects older versions. File History plays that clerk for selected folders, while the external drive or network share is the second room.

The September fault interrupted the clerk, not necessarily the cabinet. Your old copies could still sit safely on the backup drive while new work stopped arriving. That distinction explains why seeing folders on the drive can be falsely comforting. A folder full of last month’s files proves last month’s run, not today’s.

It also explains the confusing reconnect warning. Under ordinary conditions, “Reconnect your drive” often means exactly what it says. Microsoft’s reconnect instructions tell people using a USB drive to connect it and people using a network location to reselect that network destination, then wait for the next scheduled backup (Microsoft Support). During this known issue, Windows could show the same message even when the destination was connected and working.

A warning is therefore a clue, not a diagnosis. If the drive is absent, reconnect it. If the drive is present but the last backup stopped around the September update, install the repair and test again. If the repaired computer still fails, you have evidence for a different problem instead of a reason to keep unplugging and reconnecting the same cable.

File History also has limits that the bug did not create. It is designed around personal files and folders, not a perfect image of every program, setting, and piece of Windows. Microsoft’s broader recovery guide presents File History beside Windows Backup, restore points, recovery drives, and installation media because those tools solve different recovery problems (Microsoft Support). A copy of Documents can rescue a deleted invoice; it cannot by itself rebuild every application after a dead system drive.

Cloud syncing adds another easy source of confusion. A file in OneDrive may exist on Microsoft’s servers and on another device, which can be useful protection. Sync also carries changes, including some unwanted changes and deletions, between places. A separate versioned copy on a drive answers a different question: can I recover the file as it existed before the mistake travelled elsewhere?

You do not need a perfect backup architecture before dinner. You need to know which important folders are covered, where the copies live, and whether one can come back. File History can serve that modest job well. The restore test is how it earns your trust again after a failure.

Why the repair alone is not the receipt

Windows Update can confirm that a package installed. That is valuable, but it answers a software question: is the code containing Microsoft’s repair present? It does not answer the household question: did this particular laptop copy this particular folder to this particular drive after the repair?

Imagine that a delivery company repairs a broken van. The workshop receipt proves the van was fixed. You still check whether today’s parcel reached your house, because repairing the route and completing your delivery are separate events. KB5124010 or KB5124006 is the workshop receipt. A fresh File History time and a successful restored file are the delivery receipt.

This difference matters most when an automatic task has been failing quietly. Suppose a parent edited hundreds of photos during September, a freelancer changed client files every day, or a student kept one dissertation folder on the laptop. An update installed on 22 September can let the next copy succeed. Until that run finishes, the newest versions may still exist in only one place.

The word “backup” also encourages a false sense of completeness. People say “I have a backup” as if backup were an object, like a spare key in a drawer. In practice it is a chain: Windows notices a changed file, the job starts, the destination answers, data is written, an older version remains readable, and the restore route can find it later. A failure anywhere in that chain can leave a drive that looks busy but cannot return the thing you need.

A restore test checks more of that chain than a status screen. It proves that File History can see a saved version, present it to you, and place a copy back where you can open it. The test does not prove that every file is perfect or that the drive will never fail. It gives strong, local evidence that the route you expect is working now.

Keep the test small. A text file containing today’s date is enough. There is no need to delete a precious photo to create drama, nor should you overwrite the only copy of a live document. A harmless test file lets you check the mechanism without making recovery itself risky.

This habit belongs to the same family as checking that a smoke alarm sounds when you press its test button. Nobody expects the button to recreate every possible fire. It confirms that the parts you rely on can complete one safe, representative action. For File History, that representative action is getting one known file back.

The Digital Fortress puts this bluntly: a backup you have never tried to restore is a hope, not a backup. The line gives you permission to stop after one sensible proof instead of turning the check into a weekend project or buying more storage because the current setup feels vague.

Install the fix without making a second problem

Begin with Windows Update rather than a download link from a forum, advertisement, or unsolicited support message. Open Settings, choose Windows Update, and select Check for updates. Let Windows identify the package that matches your own release. Microsoft’s support pages say the File History issue is resolved in updates released on and after 22 September 2026, including KB5124010 for Windows 11 24H2 and 25H2 and KB5124006 for 26H1.

The 22 September packages are described as non-security preview updates. That means they contain fixes that Microsoft is releasing before the next regular security rollup, rather than a new response to an active attack. If File History is failing on your computer and Windows offers the matching update, installing it is a direct way to obtain the repair. If the update is not offered, do not force a package for a different Windows version.

Check your version if you need to make sense of the names. Open Settings, choose System, then About, and look under Windows specifications. A person using Windows 11 25H2 should expect the update family Microsoft lists for 24H2 and 25H2, while a 26H1 device follows its own page. The letters and numbers are less important than matching what Windows Update offers to the version on the screen.

Allow the update to finish and restart if Windows asks. A download progress bar is not completion, and a package waiting for a reboot has not yet given every component a fresh start. After signing in again, return to Settings, Windows Update, then Update history. Look for the successfully installed entry and keep its KB number with the date.

Do not uninstall the September security update merely to make File History behave again. That older package contains security repairs as well as the fault. Microsoft’s chosen resolution is a later update that keeps the earlier protections and corrects File History. Rolling back a security update trades a known backup problem for older software exposure, and it may still leave you unsure about the copies missed during the gap.

Avoid “driver updater,” “registry cleaner,” and backup-repair downloads promoted beside search results. This incident has a named Microsoft repair delivered through Windows Update. A tool that asks for payment, remote access, or your Microsoft password before checking the installed version is creating risk around a problem with a much simpler route.

A work or school computer belongs on a different path. The organization may control when preview updates arrive, where File History writes, or whether another backup product is responsible. Record the reconnect warning, the last successful backup time, and the Windows version, then send those facts to support. Do not bypass its update policy with a package downloaded elsewhere.

While waiting for the repair, copy today’s irreplaceable work to another destination you already trust. A normal drag-and-drop copy to a separate external drive is acceptable as a temporary bridge. So is confirming that a current cloud copy opens from another device. Label the copy with the date, leave the original in place, and return to File History after Windows is repaired.

That temporary copy should stay boring. Encrypting archives with a password you may forget, moving the only originals off the laptop, or experimenting with unfamiliar backup software increases the number of ways to lose track of the files. The goal is one extra readable copy while the automatic route is uncertain.

Make one fresh backup and prove it moved

After the repaired update is installed, connect the external drive or make sure the network location is available. Open Control Panel, choose System and Security, then File History. Microsoft still places the main File History controls there, even though most modern Windows settings live in the newer Settings app.

Read the destination before pressing anything. The screen should name the drive or network location you expect. If it points to an old disk in a cupboard or a network address that no longer exists, a successful status would still protect the wrong place. Correct the destination through File History rather than relying on the drive letter you remember.

Now check the displayed last backup time. Write it down or take a photo. If it predates 8 September, or stopped close to the installation of KB5124008, that is consistent with the known issue, though timing alone cannot prove the cause. If it is current, continue with the test anyway because a real restore is the stronger check.

Create a small text file in Documents and give it an unmistakable name such as backup-test-2026-09-23.txt. Open it, type a sentence you will recognize, save it, and close the editor. The file belongs in a folder File History is expected to cover; putting it in a temporary system folder would test something else.

Return to File History and choose Run now. Leave the drive connected while the job works. A large first run or a long gap can take time, particularly over a home network. Let the status settle rather than unplugging the drive because the activity light pauses.

When the run completes, check whether the last backup time advanced to the present. That is your first receipt. It proves Windows recorded a new File History run after the repair. Take another photo if this computer holds work you would struggle to replace.

The time alone is still a claim made by the same system that had the fault. Add an outside check. Open the external drive in File Explorer and confirm its File History area has a recent modified time. Do not rename, reorganize, or delete files inside the backup structure. You are looking for recent activity, not manually maintaining the archive.

If the destination is on a home server or another computer, confirm that the share is reachable and that its available space is sensible. A full destination can stop good software just as effectively as a Windows bug. Keep enough free space for versions to accumulate, and review File History’s cleanup choices if old copies are consuming the whole drive.

A successful run after 22 September closes the immediate gap, but review the folders that mattered during the failure window. Open several current documents from the laptop and make sure they were saved where File History looks. Files held only in an unusual folder, another user’s profile, or an application database may sit outside the normal libraries. Move nothing until you understand which copy is current.

If the last backup time still refuses to move, stop repeating the same button. Confirm the installed KB in Update history, restart once, check the cable or network destination, and read the exact message. Microsoft’s known-issue page says affected computers could record File History crashes in Event Viewer, but ordinary home users do not need to diagnose crash modules before asking for help. The version, destination, last backup time, and exact error give a technician a useful starting packet.

Restore the harmless file before you trust the archive

A backup run is only half of the promise. The other half is selecting an older copy and returning it to usable form. File History includes a personal-files restore view for that job, and your harmless text file keeps the test free of consequences.

Open the Start menu, type Restore your files with File History, and open the matching Control Panel result. Browse to Documents and find backup-test-2026-09-23.txt. If File History shows more than one saved moment, use the arrows to move between versions and choose the one created by your fresh run.

Do not restore over the live test file on the first attempt. Right-click the green restore button and choose Restore to, then select a new folder such as Documents\Restore Test. This keeps the original and recovered copies side by side. If Windows asks about an existing file, stop and choose a clearly empty destination rather than guessing which version should win.

Open the restored text file and read the sentence you wrote. Check that the file is not empty and that its modified time makes sense. You have now proved that Windows found the saved version, read it from the destination, and wrote a usable copy back to the computer.

That is the restore receipt. Record four facts in a note: the installed repair KB, the time of the fresh backup, the name of the test file, and the time the restored copy opened. A screenshot of the successful File History screen beside the restored file works too. Keep the note somewhere you will find during a real recovery, not only on the computer whose drive may fail.

After the test, you can delete the live and restored test files if you like. The version already stored in File History may remain until its retention rules remove it. Nothing important depends on that sample after the mechanism has been proved.

Try one real but non-sensitive file as a second check if this computer matters to your work. A copy of an old recipe, a public PDF, or a finished school document is safer than a tax return or the only copy of a client contract. Restore it to the test folder, open it, and compare it with the original. Stop there when it works.

A single-file test does not promise that a completely dead computer can be rebuilt from File History. It verifies the feature’s actual purpose: returning versions of covered personal files from its configured destination. If your goal includes full-device recovery, add a separate plan for applications, settings, account access, and a failed internal drive.

Microsoft’s recovery overview can help you name those separate jobs. Windows Backup can preserve supported folders, settings, credentials, and app information through a Microsoft account; File History keeps changing file versions on a drive or network location; recovery media helps when Windows itself will not start (Microsoft Support). One tool does not have to carry every kind of loss.

What to do when the test still fails

A failed test after the repair is information, not a verdict on all your old copies. Leave the backup drive intact. Do not format it, erase its File History folder, or let a cleanup utility “start fresh” before you know whether older versions can still be recovered.

Check the simplest boundaries first. Is the expected drive visible in File Explorer? Does File History name that same destination? Is there free space? If it is a network location, can you open the share using the same Windows account? Microsoft’s ordinary reconnect guidance remains useful once the September software fault has been repaired.

Next, verify the update rather than assuming Windows installed it. Open Settings, Windows Update, Update history, and look for a successful update released on or after 22 September that Microsoft lists as carrying the File History fix. A failed installation entry, a pending restart, or a different Windows version changes the next step.

Write down the exact File History message and the last backup time. If the screen still says “Reconnect your drive” while the drive is plainly available, include that contradiction. If “Run now” starts and then stops, note the time. Evidence this precise lets Microsoft support or a trusted technician distinguish the known bug from destination permissions, drive trouble, a full disk, or damaged File History settings.

Do not erase File History’s configuration as the first repair. Reset instructions online often begin by deleting a settings folder, removing the destination, or wiping the archive. Those steps may be appropriate after the old copies are protected and the diagnosis is clear. Used too early, they can remove the map to versions you still need.

Check the physical drive with proportionate care. A drive that disconnects, clicks, disappears from File Explorer, asks to be formatted, or reports read errors has moved beyond a Windows Update issue. Stop repeated writes. If the missing files matter, get help before running repair tools that change the disk.

If the destination looks healthy but File History will not run, make a separate manual copy of current important folders before troubleshooting further. Copy Documents, Pictures, and the project folders you know you use. Open a few files from the copy. This temporary safety net does not repair version history, but it protects today’s work while you investigate.

People using a network-attached storage box should check that box as well as Windows. A changed password, expired connection, renamed share, full volume, or sleeping device can all break the route. Confirm access through File Explorer, then use File History to select the correct network location. Do not expose the storage box to the public internet merely to make a local backup easier.

If you decide to replace File History with another backup product, require the same receipt from the replacement. Make a test file, run the job, restore to a separate folder, and open the result. Brand names and subscription screens do not remove the need to test the return journey.

Build a backup habit that survives the next quiet failure

The lasting lesson from September 2026 is smaller than “never trust automatic backups.” Automatic copying is useful because people forget chores. The sensible answer is to let automation do the repetitive work and schedule an occasional proof that it still finishes.

Choose a rhythm that matches how much you change. A person who edits business files daily might check the last backup every week and restore a sample each month. A household laptop used mainly for photos and letters might do the check after a large import, before travel, and every few months. The best schedule is one you will actually keep.

Keep the external backup separate when it is not running if your routine allows it. A drive permanently attached is convenient, but mistakes, electrical trouble, theft, and some malicious software can reach both the laptop and the connected copy. Connecting for a scheduled run, verifying it, then storing the drive safely gives the spare copy a different fate.

One backup destination is better than none, and two different routes are better for irreplaceable files. A local File History drive gives quick version recovery. A reputable cloud service or another offline drive can cover a house fire, theft, or failure of the first backup disk. You do not need to duplicate every download; focus on the family photos, records, and work that cannot simply be fetched again.

Write down what is covered. “Laptop backs up” is too vague to help during a bad afternoon. “Documents and Pictures go to the blue USB drive through File History; family photos also sync to the cloud; restore test passed on 23 September” tells another person where to look and what has actually been proved.

Include another adult in the household if the files matter to everyone. Show them which drive holds the versions and how to find the short receipt. Do not make the only recovery path depend on one person’s memory, an unlabeled cable, or a password nobody else can locate.

Revisit the plan when the computer, account, or storage changes. A new laptop may use different folders. Moving photos to an external working drive can place them outside the old File History scope. Replacing a home router can break a network share even though the files and backup disk remain healthy.

Permission to stop matters here. You do not need to inspect the archive every morning or learn Event Viewer because one Windows update went wrong. Install the repair, run one fresh backup, restore one harmless file, and keep a dated receipt. Repeat on a modest schedule and after a major change.

Windows fixed the software path on 22 September 2026. The final step belongs beside your own computer: prove that one file made the round trip. When it opens from the restored folder, you can close the backup window and get on with your life.

For more calm, practical security guidance, join the newsletter. It is one email per month.

Sources