Windows 10 2004 optimization/defrag bug

Hi all. latest news: finally Microsoft has confirmed the Drive Optimizer bug in Windows 10 May 2020 Update.

and it looks like a possible fix will ship next week via Windows Update in Preview Update (Formerly Optional Update)

known as the "C" Release. (C for the third week of the month). and if you Skip Preview Update this August they will include the fix in the Cumulative Update for September 2020 (Known as "Patch Tuesday"). i am quoting a page from the Windows Latest website.

External link: Windows Latest

When you say Skip Preview Update this Augus t were you referring to this option update "2020-7 Cumulative Update Preview for Windows 10 2004 for x64-based Systems (KB4568831)" which i installed on 08/08/2020.

Or is 2020-7 Cumulative Update Preview for Windows 10 2004 for x64-based Systems (KB4568831) the July preview update seeing it says 2020-7?

The preview to skip would start with 2020-8 for August?

not. I mean for this August. I mean it is estimated that it will come on August 25, 2020. I copied this article directly from Windows Latest Written by Author Mayank Parmar so that all of you understand what I mean.

title: Microsoft confirms issues with Windows 10 2004 drive optimizer

contents: Windows 10 version 2004 was released on May 27 with WSL 2, Cloud Download, and several other improvements to the underlying code. Unfortunately, the May 2020 update also brought with it some issues, including one bug that hits you right in the storage drive.

Like Windows 8 and Windows 7, Windows 10 also comes with a disk optimization tool that automatically defragments files for you on a schedule. By default, Disk Optimizer tool is scheduled to optimize your storage drives once a week.

When the optimization/defragmentation process is complete, the time in the Last Run column in “Optimize Drives” tool will update. Current Status will read something similar to “OK (0 days since the last run).”

After Windows 10 May 2020 Update, Microsoft’s Drive Optimizer tool (also known as Disk Defragmenter) is behaving weirdly for all users. According to our tests and user reports, Drive Optimizer is unable to report the correct status when the disks were last optimized.

If you look at the app to check the “Last Run” column, you may notice that no scans were done and Windows could even warn you that your drives need optimization, even when they were optimized.

The company was made aware of issues with drive optimization tool during the beta testing of a future Windows 10 update. This issue reportedly slipped through the production build and Microsoft is now planning to fix it in the next optional update.

In a statement to Windows Latest, Microsoft confirmed that May 2020 Update has caused issues with the built-in Drive Optimizer tool.

At the moment, it appears that the fix could be included in next week’s optional update, also known as “C” preview release. This month’s optional update is expected to arrive next week.

Internally, the optional updates are known as the ‘C’ release (C for the third week of the month), while Patch Tuesday updates are known as the B release because they arrive in the second week of the month.

The ‘C’ optional update for Windows 10 includes the non-security fixes that will be included in the following B release. If you skip the optional update, which is expected to arrive on Tuesday, you can still get the fixed drive optimization tool with September Patch Tuesday update.

I have never had this issue before build 2004, I'm on the insiders list but staying on retail builds. I've also not seen that using "dfrgui" the defrag window is actually trying to defragment the SSD. When I use manually use "optimize" it says "n% trimmed" but the status is not kept, right after that when leaving and restarting dfrgui it says "needs optimization". 

I got build 19041.264 installed on April 17th ... I mentioned this problem (and a few others) in the feedback hub, without getting feedback :-) 

I'm only seeing this issue if I go to Control Panel>Security and Maintenance and run the maintenance manually.

If you run the maintenance Control Panel>Security and Maintenance while also having the Optimize drives (defrag/optimize drives) open you will see it defrag then trim right in front of you.

You will only see it of you have both open at same time and do manual maintenance via Control Panel>Security and Maintenance. You will catch Windows doing it. Open Control Panel>Security and Maintenance and Optimize drives side by side and run manual maintenance (Control Panel>Security and Maintenance) and you will see it defrag briefly and then trim.

If you just open 'Optimize drives' only and select optimize then it will just trim it only.

I have never had this issue before build 2004, I'm on the insiders list but staying on retail builds. I've also not seen that using "dfrgui" the defrag window is actually trying to defragment the SSD. When I use manually use "optimize" it says "n% trimmed" but the status is not kept, right after that when leaving and restarting dfrgui it says "needs optimization". 

I got build 19041.264 installed on April 17th ... I mentioned this problem (and a few others) in the feedback hub, without getting feedback :-)

I have the same issue with defrag. It's a bug that many insiders reported to Microsoft, even before 2004 was rolled out to the general public.  

There is not much you can do at the moment, just hope that they will fix it soon.  Do not carry out a manual maintenance, because, as you noticed, your SSD will be defragged, which is bad for SSDs. 

So it only does it if I go to maintenance in control panel>security & maintenance and perform a manual maintenance? If I leave windows to do it's own thing it doesn't defrag in error?

I'll leave disk optimizer set to its weekly default setting and simply 'do not' do a manual maintenance? When windows does it's auto maintenance

It doesn't do the defrag error?

we can tell when Windows has done an auto maintenance as it shows up in control panel>security & maintenance.

I have the same issue with defrag. It's a bug that many insiders reported to Microsoft, even before 2004 was rolled out to the general public.  

There is not much you can do at the moment, just hope that they will fix it soon.  Do not carry out a manual maintenance, because, as you noticed, your SSD will be defragged, which is bad for SSDs.