(Photo by Ashish Vaishnav/SOPA Images/LightRocket via Getty Images)
Why did a Windows 11 update corrupt SSD drives? Don't ask Phison. The memory component company says it has failed to reproduce the bug.
The Windows 11 24H2 update, KB5063878, rolled out earlier this month. Some users soon reported the sudden disappearance of their SSD drives from the operating system, while others noticed freezes or crashes.
In response, Phison, a Taiwanese provider of controllers for SSD drives, investigated the Windows 11 update and an earlier one, KB5062660. However, the company says it’s found no evidence of the bug, even after extensive testing and trying to replicate the problem, according to Wccftech.
“Phison dedicated over 4,500 cumulative testing hours across the drives reported as potentially impacted and conducted over 2,200 test cycles. We were not able to reproduce the reported issue, and no partners or customers have reported that the issue impacted their drives at this time,” the company tells PCMag.
The statement prompted backlash in the PC community since at least some users have encountered the problem. Others say they were hoping for a solution rather than continued uncertainty. Meanwhile, another group of users wonders if the problem was overblown from the start. We haven't been able to replicate the SSD drive issues at PCMag.
For now, Phison has only said it “remains committed to the highest standards of reliability and continues to closely monitor the situation in collaboration with our industry partners.”
A representative for the company also posted on a forum: “Phison ran every drive listed in the initial report on X in the exact same workload and cadence. This goes all the way down to the Japanese version of the game! We were unable to reproduce the issue, and to date, we are not aware of a professional test lab that has been able to do so (several partners and other companies have investigated this claim).”
Microsoft didn’t immediately respond to a request for comment. But last week, the company told PCMag it was investigating the reported problems. BleepingComputer also spotted Microsoft trying to collect data from affected users to diagnose the issue.