The blue dot network mentioned earlier that a failure in the optimized drive functionality of Windows 10 Version 2004 prevented the optimization status time from being displayed correctly. It may seem like an inconsequential feature, but after a closer look, we found that this BUG could affect the performance and longevity of SSD SSDs, etc.
In fact, the problem existed during the beta period, and Microsoft fixed it in Windows 10 Build 19551, released in January 2020.
However, the latest official version we’re using, Windows 10 Version 2004, hasn’t been fixed, and even Microsoft hasn’t confirmed the problem yet.
Seemingly insignificant but affects SSD SSD performance and longevity:
Blue Dot Network has been testing this issue after receiving user feedback, and we found that this seemingly unimportant problem will lead to continuous system optimization.
Normally the drive is optimized to record the time, Microsoft designed to perform weekly or monthly optimization, after each optimization, the system records the current optimization time.
Because a BUG occurs, the system cannot record optimization time, so the system attempts to perform automatic optimization operations on the drive every time it is restarted and turned on.
However, for SSDs there is no need for such optimizations such as defragmentation at all, but instead, regular defragmentation optimizations can also affect flash life.
Note: SSSLs use TRIM technology for data recovery and finishing, for the same purpose as defragmentation of mechanical drives, and to process useless metadata.
Why SSDs should not perform defragmentation and why life is affected:
Defragmentation is a mechanical hard disk, also known as disk-age technology, which is designed to organize files scattered across different tracks to speed up seek times and so on.
The sSD’s flash memory is based on the electric float technology, and the sSD’s seek time is related to the flash memory technology and the master chip, so it is basically fixed.
So SSD stubation does not require defragmentation at all and this has nothing to do with SSD performance, instead defragmentation consumes flash wipes.
The lifetime of flash particles is limited, and each defragmentation is like a lifetime of flash particles, which can also affect hard disk read and write performance.
Microsoft engineers have said that only very fragmented SSDs are recommended for defragmentation, and that the frequency of finishing should be reduced to once a month.
While Windows 10’s optimized drive failure will be sorted every time it is turned on, Blue Dot’s february launch of v2004 beta is now distressing.
Note: There is also the view that SSD is not completely do not defragmentation, but the same must reduce the frequency of finishing, preferably a month or even a few months once.
Users who have already used v2004 should use the mitigation scheme immediately:
Based on the above issue, Blue Dot strongly recommends that users who already use Windows 10 Version 2004 manually adjust the optimized drive feature to exclude SSDs.
For existing mechanical hard drives although can be defragmented but each boot is certainly not possible, so it is recommended to pause defragmentation before this problem is repaired.
How to do this: The taskbar search box searches for defragmentation and then turns on the Optimize Drive feature, clicking on the changes below to go to the schedule settings task for the optimization feature.
All SSDs are excluded from the drive selection interface, after which users can perform regular manual optimizations without the need for the system to be sorted every time they are turned on.