[German]A bug in the defragmentation of the Windows 10 May 2020 Update (Version 2004) causes SSDs to defragment much more often than expected. The bug was reported in January 2020 and should have been eliminated long ago.
Bleeping Computer has already prepared the whole thing a few days ago in this post. It is about the automatic maintenance of Windows, which also performs a defragmentation of the drives as a task. The Windows 10 function “Automatic Maintenance” can be viewed in the task planning under System Control -> System and Security -> Security and Maintenance, and is performed cyclically. This maintenance includes checking drives for optimization needs (defragmentation/trimming), searching for new updates, security scans and other diagnostics.
However, in the Windows 10 May 2020 Update (Version 2004), the Windows Defragmenter has a bug that defragments SSDs too frequently, trims non-SSD drives, and forgets when it last optimized a drive each time it restarts. The latter is a problem, because Windows 10 should actually remember when a maintenance/optimization was last performed on a drive. This is to prevent drives from being defragmented too often or SSDs from being trimmed.
This has been noticed in the wildersecuritys forum, where there is this entry in the thread that points out a problem:
Today I noticed error in my event viewer happening with Windows Defragger. Error 264 is logged when defragger tries to perform TRIM on non-SSD drives:
The storage optimiser couldn’t complete re-trim on [DriveName] because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
After some googling I found another report with more serious bug (defragger trying to defrag SSD). I could reproduce an issue so I disabled scheduled maintenance also.
EDIT: here is a link that describes how to disable it.
Bleeping Computer was able to reproduce this bug, the Windows Defragmentation sees optimization needs for an SSD that was just optimized early in the morning. As a general rule, you should avoid defragmenting solid state drives (SSDs) to prevent unnecessary wear and tear. However, Microsoft developer Scott Hanselmann has explained here that there is some benefit to defragmenting a highly fragmented solid state drive (SSD), and will therefore defragment an SSD drive once a month.
“Actually Scott and Vadim are both wrong. Storage Optimizer will defrag an SSD once a month if volume snapshots are enabled. This is by design and necessary due to slow volsnap copy on write performance on fragmented SSD volumes.”
However, because Windows 10 version 2004 forgets when the last optimization was performed, SSDs are optimized after every Windows 10 restart – which is certainly not good. And there’s one more thing on top – the bug should have been eliminated long ago. On January 23, 2020 Microsoft announced the Windows 10 Insider Preview Build 19551. At this tim Microsoft wrote:
Thank you for reporting that the Optimize Drives Control Panel was incorrectly showing that optimization hadn’t run on some devices. We’ve fixed it in this build.
Obviously they didn’t really test – or the bug eventually migrated back into later builds. Golem writes here that in January 2020 there were also entries in the feedback hub. To cut a long story short: Windows 10 Version 2004 is quite buggy. More details can be found at Bleeping Computer in this post, and in this Microsoft Answers forum post.
Windows 10 2004: Storage Spaces issues
Windows 10 Version 2004: Issues with Malwarebytes 4.1.0?
Windows 10 version 2004 annoys Chrome users
Windows 10 v2004 breaks Fresh Start
Windows 10 Version 2004/Windows Server 2004 released
Windows 10 Version 2004: Deprecated/removed features
Windows 10 version 2004: Graphics issues with multi monitor and f.lux
Windows 10 2004: ADMX templates available
Windows 10 Version 2004: External display turns black
Windows 10 Version 2004: Issues with DVBViewer drivers
Windows 10 2004: Upgrade fail due to drive letter on boot partition
Windows 10 Version 2004: Issue with Optane Systems
Windows 10 V2004: Office365 Sync issues with iCloud
Windows 10 V2004: Downloads removed from disk cleanup
Windows 10 Version 2004: Forced upgrade without user consent
Windows 10 Version 2004 Upgrade Issues with Surfaces
Upgrade Block to Windows 10 2004 for devices with Core isolation (HVCI)
Cookies helps to fund this blog: Cookie settings