Windows 11 Update Linked to SSD Performance Issues

markdown

Is the Latest Windows 11 Update Damaging Your SSD? Here’s What You Need to Know

Are you running Windows 11 and rely on a solid state drive (SSD) for blazing-fast performance? You might want to hold off on installing the latest security update. Reports are emerging suggesting that recent Windows 11 updates are potentially causing problems, even rendering some SSDs inaccessible under specific conditions. This article dives into the details of the alleged Windows 11 SSD issues, the affected drives, and what precautions you should take.

Potential SSD Problems After Windows 11 Update: The Details

Take this information with a grain of salt, as Microsoft has not officially acknowledged this issue. Reports originating from the Japanese tech website Niche PC Gamer indicate that the latest security updates for Windows 11 are causing unexpected problems for some users. The problem seems to manifest under specific conditions related to writing large amounts of data to solid state drives.

Which Windows 11 Updates are Potentially Causing Issues?

The root cause of the problem is reportedly the installation of either KB5063878 or KB5062660. Let’s break down what these updates are:

  • KB5063878: This is the final security update for Windows 11, version 24H2, released by Microsoft on this month’s Patch Day. These updates are typically rolled out to address security vulnerabilities and improve system stability.
  • KB5062660: This is a preview update of KB5063878, which Microsoft released in late July. Preview updates allow users to test upcoming features and fixes before the official release.

Installing either of these updates could potentially lead to problems for users with certain SSD configurations.

How Does the Windows 11 Update Affect SSDs?

The reported issue primarily affects systems using SSDs, particularly when a significant amount of data is written to the drive. The problem seems to occur when either:

  1. A large number of files are written to the drive.
  2. A single, large file is written to the drive.

In the worst-case scenario, the drive can become completely inaccessible, leading to potential data loss and system instability. This is a significant concern for users who rely on their SSDs for everyday tasks, gaming, or professional workloads.

User Reports and Initial Findings

One of the first users to report the issue was an X (formerly Twitter) user named Necoru_cat. They observed the problem while updating the game Cyberpunk 2077 after installing the latest Windows 11 security update (version 24H2). The drive where Cyberpunk 2077 was installed became inaccessible.

Necoru_cat noted that writing more than 50 gigabytes of files continuously to the SSD with a usage rate of at least 60 percent triggered the problem. While restarting the system would often restore the drive’s functionality, writing large amounts of data again would cause the issue to reappear. However, Niche PC Gamer reported that some SSDs might not become available even after multiple reboots, which means you have a serious SSD problem.

Investigating the Windows 11 SSD Compatibility Problem

Niche PC Gamer conducted tests to determine which SSDs were susceptible to this issue. According to their findings, the following SSDs were affected:

  • Corsair Force MP600
  • SSDs with Phison PS5012-E12 controller
  • KIOXIA EXCERIA PLUS G4
  • Fikwot FN955
  • SSDs with InnoGrit controller
  • Maxio SSDs
  • KIOXIA M.2 SSDs
  • SanDisk Extreme PRO M.2 NVMe 3D SSD

In contrast, the following drives appeared to be unaffected during their tests:

  • Solidigm P44 Pro
  • Samsung 980
  • SanDisk SSD PLUS 240GB SDSSDA-240G

Further User Testing Confirms Incompatibilities

Necoru_cat also conducted their own tests and compiled a list of SSDs that were either affected or unaffected by the issue. The following SSDs were found to be affected:

  • WD Blue SN5000 2TB NVMe (restarted to recover)
  • WD Red SA500 2TB SATA (restarted to recover)
  • WD Blue SA570 1TB SATA M.2 (restarted to recover)
  • WD Blue SA510 2TB SATA (inaccessible, not restored even after reboot)
  • Corsair MP510 960GB NVMe (restarted to recover)
  • Corsair MP600 2TB NVMe (restarted to recover)
  • SK hynix Platinum P41 NVMe (restarted to recover)
  • Crucial P3 Plus NVMe (restarted to recover)
  • ADATA LEGEND 800 2TB NVMe (restarted to recover)
  • HP FX7000 2TB NVMe (restarted to recover)
  • XPG SX8200 Pro 2TB NVMe (restart to recover)
  • Hanye HE70 2TB NVMe (restarted to recover)

And here are the SSDs that were not affected:

  • Samsung 990 PRO 2TB NVMe
  • Samsung 980 PRO 2TB NVMe
  • Samsung 870 EVO 1TB SATA
  • WD Black SN7100 2TB NVMe
  • WD Blue SA510 1TB SATA M.2
  • Seagate FC530 2TB NVMe
  • Seagate FC530 1TB NVMe
  • Solidigm P44 Pro NVMe
  • Crucial T700 2TB NVMe

It’s important to note that the results might vary depending on your specific hardware configuration, driver versions, and usage patterns. More testing is needed to draw definitive conclusions.

Is Your SSD Controller at Risk? Impact of Phison and InnoGrit Controllers

The findings suggest that SSDs using particular controllers might be more vulnerable to the issue. Specifically, SSDs using Phison PS5012-E12 and InnoGrit controllers were reported as affected. An SSD controller [source: Wikipedia] is a dedicated microcontroller responsible for managing the flash memory within the SSD, including data placement, wear leveling, and error correction. Potential issues with the interaction between the Windows 11 update and these controllers could explain the observed behavior.

What’s the Impact on M.2 NVMe SSDs?

Many of the listed affected drives are M.2 NVMe SSDs. NVMe (Non-Volatile Memory Express) is an interface protocol designed specifically for SSDs, offering significantly faster speeds and lower latency compared to traditional SATA interfaces. The prevalence of M.2 NVMe SSDs among the affected drives raises questions about the interaction between the update, the NVMe protocol, and potentially specific firmware versions on these drives.

What Can You Do to Mitigate Potential SSD Issues?

Until Microsoft officially addresses the issue and provides a fix, here are some precautions you can take:

  • Postpone the Update: If you have one of the SSDs listed as potentially affected, consider postponing the installation of KB5063878 or KB5062660 until more information becomes available. You can pause Windows Updates in the Settings app.
  • Back Up Your Data: Regularly back up your important data to an external drive or cloud storage. This will protect you from data loss in case your SSD becomes inaccessible.
  • Monitor SSD Health: Use SSD monitoring tools (often provided by the drive manufacturer) to keep an eye on your drive’s health and performance. Look for unusual behavior or error messages.
  • Avoid Large Data Transfers: If you must install the update, try to minimize writing large amounts of data to your SSD, especially if it’s one of the potentially affected models.
  • Check for Firmware Updates: Visit your SSD manufacturer’s website to see if there are any firmware updates available for your drive. Firmware updates can sometimes address compatibility issues.

Conclusion: Stay Informed and Take Precautions

The reports of Windows 11 updates potentially causing SSD problems are concerning. While Microsoft has not yet officially confirmed the issue, the user reports and initial testing warrant caution. If you have an SSD, especially one listed as potentially affected, it’s wise to postpone the updates and take preventative measures like backing up your data. Keeping an eye on official announcements from Microsoft and your SSD manufacturer will also help you stay informed. This situation highlights the importance of thorough testing and compatibility checks before releasing updates that can impact critical hardware components. What do you think about these reports? Have you experienced similar issues? Share your thoughts and experiences in the comments below!





Sources & Further Reading:
Original article at www.ghacks.net

spot_imgspot_img

Subscribe

Related articles

spot_imgspot_img