Windows 11 SSD problems are blamed on auditors using “early versions of the fixed program”

Reports have been circulated during the past few weeks that have been the last Windows 11 updates (KB5063878 and KB5062660) Some SSDS caused Phiston controllers. Although many YouTube and Tiktok videos blamed Microsoft on problems, Phiston has identified “early versions of fixed and bius” programs “as a problem instead.

Michael Woo, General Motors and President of the United States, says in a statement to freedom. “These versions are performance inspection engines and they are not identical to that introduction to the final users through official distribution channels. We have noticed that old fixed programs are still used in some SSDS and we encourage any auditors who face this to take advantage of the updated updated fixed programs through the update facilities provided by the manufacturer.”

Youtuber Jayztwocents He claimed last week “Windows update and SSD problem are much worse than we thought!” Jayztwocents showed a decisive T500 leadership (with the Phison E25 controller) failed after the latest Windows 11 security updates from Microsoft, and needs an energy cycle to return to life. It is not clear whether Jayztwocents used fixed -based SSD programs before release, or even BIOS early motherboard.

Veson managed to repeat the issues he reported PCDIY! community Nevertheless, I found that these were retreating to the fixed engineering programs. “PCDIY Test and Send PCDIY! It was used as the fixed -fetched engineering inspection programs, which are not the final fixed programs used in the Corsair Force MP600 SSD 2TB series and other engines with the E16 control unit available for consumers in the market.” PHison also conducted the same tests on SSDS for consumers and did not find any accidents or failures.

Microsoft said at the end of last month that she “did not find any contact” between safety updates and the disabled drive on social media and other places. This did not prevent many people, including prominent YouTubes, did not blame Microsoft in SSD problems. This is barely sudden, given the history of Microsoft for the chaotic Windows updates.