Windows10update Could Kill Your SSD — What You Need to Know

Windows10update Could Kill Your SSD — What You Need to Know

Microsoft is working to fix an update that appears to have introduced a bug that could compromise the life of solid state drives (SSDs).

Bug-tracking site BleepingComputer reported that the Windows 10 May 2020 Update, aka version 2004, is causing a series of problems, including one that confuses the operating system's "Drive Defragmentation and Optimization" tool. The bug means that Windows 10 version 2004 incorrectly records the time of the last time an SSD was defragmented and optimized.

In other words, when the "Defrag and Optimize Drive" tool is used, it flags the SSD as needing optimization. Since it is easy to forget to do this manually, Windows 10 performs these tasks automatically.

However, since this tool does not record the defragmentation, it will defragment the SSD every time the drive is rebooted, which in effect may cause the SSD to be defragmented about 30 times more often than it actually is. This could ultimately damage the lifespan of the SSD and cause the SSD to die slowly.

Defragmentation means putting together pieces of data and packing them closely with other related data. This is like sweeping a pile of fallen leaves from a garden together; there will still be the same amount of fallen leaves in one space, but they are grouped together for easy access at once.

The frequency of defragmentation of SSDs is controversial, with some arguing that there is no benefit to defragmentation as there is with traditional rotating disk drives. However, excessive defragmentation can affect the lifespan of an SSD. And that is the risk posed by bugs in "defragmentation and drive optimization" tools.

However, an update to Windows 10 Build 19042.487 (20H2), currently being distributed to Windows Insider program members, promises to squash this bug.

Those using the regular version of Windows 10 will have to wait for the update to pass beta testing. In the meantime, however, it may be worth turning off automatic defragmentation to avoid encountering this bug on Windows 10 machines.

Categories