Blog / Windows Updates & Drive Health
The Windows 11 update that made SSDs disappear: what KB5063878 taught us
In August 2025, a routine Windows 11 security update became one of the most-searched PC scares of the year. Shortly after installing KB5063878 (and the related KB5062660 preview update) on Windows 11 version 24H2, users began reporting that their SSDs were vanishing — mid-file-transfer, the drive would simply drop out of File Explorer, Device Manager, and sometimes the BIOS itself. Some drives came back after a reboot. Some didn't, and the data on them was corrupted or inaccessible.
The story has long since left the headlines, but we still see the search traffic — and the occasional affected drive — so here's the evergreen version: what happened, what it says about update risk in general, and what to do if a drive ever disappears on you.
What was reported
The reports clustered around a specific pattern. Failures were tied to large sustained writes — typically 50GB or more in a single transfer — onto drives that were more than about 60% full. Think: restoring a big backup, installing a large game, moving a video library, or cloning a drive right after the update.
SSDs using Phison controllers appeared most often in user reports, with additional reports involving InnoGrit and Maxio controllers across several brands — models named included the Corsair Force MP600, SanDisk Extreme Pro, Kioxia Exceria Plus G4, and ADATA SP580, among others. It wasn't limited to one manufacturer, and a handful of conventional hard drives were reported too.
Worth stating clearly: Microsoft investigated and said it found no link between the August 2025 update and the reported failures, and Phison said it was working with partners on the affected controllers. Users continued to report failures regardless. Whether the update caused the failures or merely coincided with a controller-level issue was never definitively settled in public — which is itself the lesson.
The real takeaway: updates and storage don't always mix predictably
We're not in the business of telling you to fear Windows updates — skipping them is far riskier, as we covered in our guide to managing Windows 11 updates for business. The KB5063878 episode matters because it shows that even a routine, well-tested patch can interact badly with specific hardware in ways nobody catches before release. You can't prevent that. You can make it a non-event:
- Back up before big updates. A current, tested backup turns "my drive vanished" from a crisis into an inconvenience. This is the whole argument for automated, monitored backups — they happen whether or not anyone remembered.
- Avoid huge single transfers right after a major update, especially onto drives that are nearly full. Give a fresh update a few days of normal use first, and keep some free-space headroom on every drive.
- Keep SSD firmware current. Drive vendors ship firmware fixes through their own tools — most people never run them. (We do this as part of managed maintenance.)
- Stage updates if you manage a fleet. Roll patches to a test machine or pilot group before everyone gets them. That's standard practice on our managed IT plans — if an update misbehaves, it misbehaves on one PC, not twenty.
If a drive has already disappeared or lost data
Whether it was this update, a different one, or plain hardware failure — the moment a drive drops out or data goes missing, what you do next largely determines whether the data is recoverable:
- Stop writing to the drive immediately. Don't reformat it, don't reinstall Windows on it, and don't run "repair" utilities that write to the disk — every write can overwrite the data you're trying to get back.
- Don't power-cycle it over and over hoping it reappears. Repeated power cycling can push a recoverable controller or firmware fault into something much worse.
- Get a professional evaluation if the data matters. A drive that suddenly dropped out of the system is often recoverable at the controller or firmware level — but usually not with consumer software.
Already lost access to a drive after a Windows update? Our sister company Desert Data Recovery specializes in SSD recovery — including controller- and firmware-level failures — with a free evaluation and a no-data-no-fee policy. Their explainer on what to do when an SSD isn't detected is a good first read while you decide.
The bigger picture
Incidents like KB5063878 are why "just click Update" isn't a patching strategy and "the drive has never failed before" isn't a backup strategy. Under an ioLogik managed plan, updates are staged and monitored, firmware stays current, and backups run and get tested automatically — so whatever the next update surprise turns out to be, it lands on a business that's ready for it. Talk to us about getting there.