Windows quietly stopped backing up your files, and the fix is the one thing that won't install itself

Here's the quiet horror: you install the monthly Windows security update, walk away, and your backups stop — and nothing tells you. That's exactly what Microsoft's September Patch Tuesday did to File History, the built-in feature that quietly keeps hourly snapshots of your Documents, Pictures, and Desktop on an external drive or NAS. After the update, backups stopped creating or updating, the "Last Backup" stamp froze, files showed "No previous version available," and connected drives triggered a "Reconnect your drive" nag even though they were plugged in and fine. Microsoft confirmed it in a Saturday service alert and shipped the fix — but the fix is KB5124006 and KB5124010, the optional non-security preview updates. So unless you already opt into "get the latest updates as soon as they're available," the fix will not find you. You either hunt it down in Windows Update and install it by hand, or you wait for next month's Patch Tuesday on October 13. A backup that's broken is one thing. A broken backup whose repair doesn't auto-deploy is two things — and the kind of thing that only becomes obvious the first time something real goes wrong and you reach for the one version you were counting on, except it's not there.

The bigger picture is that File History isn't the only casualty, and that's what should keep an admin up at night. This same September update wave is also behind Hyper-V breakage, Remote Desktop Services failures, USB audio dropouts, an "Antivirus is turned off" scare, Always On VPN drops, and a domain-login bug that needed its own out-of-band fix. Microsoft has been firing one-off out-of-band patches all month to clean up the fallout, which is a polite way of saying the September drop was rougher than usual. Meanwhile KB5124010 is also the final preview update for Windows 11 24H2, which hits end of support in October — so that one carries an extra layer of "you should be on a newer build anyway" pressure on top of the backup fix. The operational lesson is the same one you learn every time a "routine" cumulative update goes sideways: a backup system that doesn't verify its own output is just a hope, and an auto-update pipeline that can corrupt that hope without a dashboard telling you is a liability you didn't know you were running.

Source article image
Source image 1

So if you run File History, or anything in that category of set-and-forget backup, go check it now — don't assume the green "backed up" state is real, and don't assume the fix reached you. The tension worth sitting with: we've made backups so convenient and so "hands-off" that the moment they fail, the failure is invisible, and the repair is deliberately gated behind an optional update. When the thing you trust to save you is the thing that silently breaks, what does your detection actually look like?

Source article image
Source image 2

Sources

Comments

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

When Two AI Bots Finally Learned to Talk in Discord

Enterprise AI Is Quietly Becoming a Systems Integration Problem