News & Commentary

Your Backup Didn't Fail. It Blamed Your Drive.

Msoft breaks file history

Microsoft's September updates broke File History and told people to reconnect drives that were fine. The fix is shipping; the lesson is how you check a backup.

Microsoft has confirmed that its September 2026 security updates can stop Windows File History from creating or updating backups on Windows 10 21H2 and later and Windows 11 23H2 and later (BleepingComputer). Affected machines say "Reconnect your drive" while the drive is plugged in and working, the Last Backup timestamp stops moving, and older files report no previous version.

If you run a one-person business or a homelab off a Windows box and a USB drive, this is your backup.

Fair to Microsoft: it flagged the issue, and the Windows 11 fix is already out in this month's optional preview updates, with everyone else getting it in October's Patch Tuesday (BleepingComputer).

But the part worth remembering isn't the crash. It's the message. A backup that fails loudly gets investigated. A backup that blames the drive sends you to check the cable, write off an aging enclosure, and move on - while nothing gets saved. A monitor that reports the wrong cause is worse than no monitor, because you believe it.

Most of us check whether backup software is running. Almost nobody checks whether it produced anything.

Check a backup by what it produced, not by what it says.