The SSD bug in Windows 11 is plaguing thousands of computers and Microsoft doesn’t seem to want to do anything about it to improve the situation.
The bug that affects SSDs in Windows 11 continues to wreak havoc. A few months ago, the existence of a bug designed to compromise the operation of SSDs in Windows 11 was discovered. This bug causes problems that go beyond slow speeds of both writing and reading.
In March 2023, the great problem of SSDs in Windows 11 began. The arrival of the KB5023778 update to Windows 11 computers included a bug that has caused the vast majority of users to wonder if there is a problem with their SSD drives installed in their laptops or desktop computers.
no solution in sight. Microsoft has done absolutely nothing to put an end to this SSD problem in Windows 11, in fact, since March 2023 users have been complaining about poor performance on their computers due to this bug. Furthermore, the problem affects even the most expensive SSDs on the market.
All SSDs can be a victim of this bug. Complaints from users are massive in the specialized forums, being a meeting point for all the people who are suffering the consequences of this bug on their SSDs in Windows 11. As mentioned, the speeds have decreased abysmal.
The SSD bug in Windows 11 is wreaking havoc
Speeds of 4,400 MB/S that are now 1,200 MB/S. Among the different complaints are comments from users who ensure that their SSDs now have a sequential read and write speed four times less after the arrival of the update to the operating system of their computers.
The operating system is to blame and Microsoft doesn’t care. Users have been complaining on official channels for months, while Microsoft does absolutely nothing to remedy it. The Redmond company has not made any kind of comment in this regard and is not expected to do so at this point. But it would be nice if you recognized the problem in the SSDs.
Slow SSDs in Windows 11 affecting the entire system. Games, applications and any type of program do not work as they should considering this problem caused by a bug in Microsoft’s operating system. We will have to wait for Microsoft to decide to release an update that solve this problem once and for all in the operating system.