Windows 10 Version 2004: Update KB4571744 will fix the Defrag bug

[German]In Windows 10 version 2004 (and also in the 20H4) there is a bug in the program Defrag, which wants to optimize SSDs and drives constantly. Now there are hints that the update KB4571744, which has just been tested with Windows Insiders, should correct this bug. But it seems, the the SSD defragmentation bug isn't fixed.


Background: The Defrag Bug

I had already mentioned the problem in June 2020 in the blog post Windows 10 2004: Bug defragments SSDs too often. The drive optimization of Windows 10 May 2020 Update (Version 2004) no longer remembers the latest version, but shows 'Never run, optimization required'. Blog reader Volker had already noted this in this German comment at the end of May 2020.

This leads to the unpleasant effect that SSDs are optimized more often than necessary. Defrag also wants to perform trims on non-SSD drives and unnecessarily tries to optimize hard drives as well, because the information when a drive was optimized last time is forgotten.

Update KB4571744 for Windows 10 V2004 and 20H2

Currently Microsoft is testing update KB4571744 with Windows Insiders, as I mentioned in the blog post Windows 10 Insider Preview Build 19042.487 (20H2). The update is intended for Windows 10 20H2, which is expected in autumn. But since Windows 10 version 2004 gets the same updates, the fixes are applicable for this version as well.

But now Microsoft is testing an update for Windows 10 20H2 with Windows insiders in the Beta Channel as well as in the Release Preview Channel for Windows 10 Version 2004. The announcement of the update KB4571744 for Windows 10 20H2 was made in the Windows Blog, where you can read the extremely long list of fixes. EP already mentioned in this comment (ths) that the optimization bug should be fixed by this update.

The KB4571744 update for Win10 v2004 & v20H2 includes the defrag/optimization bugfix as mentioned by MS in their blog:

"We fixed an issue that causes the Optimize Drives dialog to incorrectly report that previously optimized drives need to be optimized again."

Note – the updated DLL files for the ms defrag fix are defragproxy.dll, defragres.dll & defragsvc.dll – all 3 of them with ver. 10.0.19041.487

Woody Leonhard has also mentioned this in a short article. When the update will be released in general is not yet known. I just checked, the update KB4571744 is not listed in any support article yet, so it is not yet generally released.


SSD is still defragmented

Addendum: Apparently Microsoft has only changed the description and announced a fix, but has not fixed the bug. In the comments within my German blog it was reported that there are 'discrepancies' concerning the fix. In the task planner you can find the entry:

defrag -c -h -o -$

German blog reader Girofox writers, that without the $ sign, the SSD drive is optimized, but with the $ sign, the SSD is analyzed and defragmented. In a follow-up comment he writes:

Unfortunately, SSDs are still defragmented if you run the Task ScheduledDefrag (under Task Library -> Microsoft -> Windows -> Defrag) manually with the "Optimize Drives" window open. Alternatively, simply run -c -h -o -$ in the cmd defrag and you will see that SSDs are defragmented instead of optimized.

On German site there is now this article which confirms that SSDs are still defragmented instead of optimized.

Similar articles:
Microsoft Office Patchday (August 4, 2020)
Microsoft Security Update Summary (August 11, 2020)
Patchday: Windows 10-Updates (August 11, 2020)
Patchday: Windows 8.1/Server 2012-Updates (August 11, 2020)
Patchday: Updates for Windows 7/Server 2008 R2 (August 11, 2020)
Patchday Microsoft Office Updates (August 11, 2020)

Microsoft August 2020 Patchday issues

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Update, Windows and tagged , , . Bookmark the permalink.

One Response to Windows 10 Version 2004: Update KB4571744 will fix the Defrag bug

  1. EP says:

    the KB4571744 update has now been publicly released as of THU Sept. 3 (as build 19041.488 instead of 19041.487)

Leave a Reply

Your email address will not be published. Required fields are marked *