Uncategorized

Windows 11 update fixes annoying SSD slowdown error

Si ha experimentado un rendimiento lento en su PC con Windows 11, es posible que desee buscar una nueva actualización. Microsoft ha lanzado un parche que corrige un error molesto que provocaba que algunos SSD se ralentizaran en el último sistema operativo.

The bug was first reported by users on Reddit and other forums, who noticed that their SSDs were running at slower speeds than expected after upgrading to Windows 11. Some users also reported increased CPU usage and disk activity, which could affect the lifespan and reliability of their SSDs.

windows 11
windows 11

Microsoft acknowledged the problem and said it was due to a compatibility issue with some storage controllers. The company said it was working on a fix and advised users to avoid defragmenting or optimizing their SSDs until the patch was available.

The patch, which is part of update KB5007262, is now being rolled out to Windows 11 users via Windows Update. The update also includes other improvements and fixes for the operating system, such as resolving an issue that prevented some applications from launching, improving the reliability of the taskbar and fixing an issue that caused some devices to lose network connectivity.

To install the update, go to Settings > Windows Update and click Check for updates. If the update is available, you will see it listed as «Preview cumulative update 2021-10 for Windows 11 (10.0.22000.282)». Click Download and install and follow the instructions to complete the process.

After installing the upgrade, you should notice a significant improvement in the performance of your SSD. You can also use a benchmark tool such as CrystalDiskMark to measure the speed of your SSD and compare it to the results before the upgrade.

We hope this update will help you enjoy a smoother and faster Windows 11 experience. If you have any questions or comments, feel free to leave a comment below or contact us through our support channels.

If you are an early adopter of Windows 11, you may have noticed a significant drop in the performance of your NVMe SSD since March 2023. This is due to a bug introduced by the Moment 2 update (specifically, update KB5023706) that caused many SSDs to run at half their normal speed. Despite widespread complaints, Microsoft did not address the problem until August Patch Tuesday, when it released a new Windows 11 cumulative update KB5029263.

Although the official release notes do not mention anything about the SSD bug or its fix, many users have reported that their SSDs have returned to normal after installing the update. WindowsLatest also confirmed this in a recent article, quoting a user who said, «After the March update, it was like driving a sports car with a clogged fuel filter. This recent August update fixed the NVMe SSD issues for us, but it also sheds light on the need for Microsoft to improve its quality assurance processes.»

This is good news for Windows 11 users who rely on fast and reliable SSDs for work or play. However, it also raises questions about how Microsoft tests and deploys its updates, especially for a new operating system that is supposed to be more stable and secure than its predecessors. We hope Microsoft learns from this experience and avoids similar problems in the future.

The final sentence of the previous paragraph reveals that Microsoft did not make any public statement about the Windows 11 SSD bug, leaving affected users without any support. However, it appears that Microsoft was working on a fix behind the scenes, as update KB5029263 resolves the issue. It is not yet clear if the update improves performance for all NVMe SSDs or if some users are still experiencing issues.

A Reddit user reported that he is still having problems:

«I still have the problem, but the most frustrating thing is that Microsoft never acknowledged whether this problem exists or not. So we never know if they fixed it or not. But if it doesn’t exist, why do so many of us have the problem? What I notice is that fewer people are complaining about this in recent updates, so maybe it’s fixed for some.»