Windows Latest: A fix for the broken Win10 version 2004 Drive Optimizer (Defrag) tool is being tested

Topic

New Reply

Just in from Mayank Parmar at Windows Latest: According to the changelog of Build 19042.487, this issue has now been resolved in Windows 10 20H2*. Aft
[See the full post at: Windows Latest: A fix for the broken Win10 version 2004 Drive Optimizer (Defrag) tool is being tested]

3 users thanked author for this post.

lmacri, Carl D, GreatAndPowerfulTech

Reply | Quote

Replies

It’s about time MS fixed this problem!  I wonder if this “fix” will trim SSD’s correctly?

3 users thanked author for this post.

Carl D, GreatAndPowerfulTech, woody

Reply | Quote

Good question!

It’s amazing the fix took this long. There were complaints long, long before 2004 shipped.

2 users thanked author for this post.

Carl D, GreatAndPowerfulTech

Reply | Quote

Microsoft needs to have a  Year of Stability for 10 and Focus only on stability, sans any New And Shiny!

Reply | Quote

I remember watching someone with Windows 3.1 running defrag and thought it was really cool, all those little squares moving around and changing colors.  That was the only Windows computer in our group at work.  The mouse was perplexing, what did it do?

That was Windows 3.1 running on a really cool 386 processor that did math even faster than before although most of didn’t know what was before.

And MS wrecked the defragger, something I first saw about 40 years ago?  Ours (present day) all work fine on mechanical and solid state drives; it continues to amaze me how some Windows users are delivered problems others never experience.  Could the “D” level team mangling Windows put down their phones long enough to fix something that has functioned well since before many of them were born?

Wait, silly me. Silly me.

Reply | Quote

Only 8 months to recieve the feedback about the bug

2 users thanked author for this post.

GreatAndPowerfulTech, woody

Reply | Quote

I’m guessing it will appear to Windows Update today.

And since in about week and half it’s patch tuesday again, installing this optional update is kinda pointless for most. Would it kill MS to release these D week updates on C week like the rest of them?

1 user thanked author for this post.

woody

Reply | Quote

[EP]

@woody

in case people are wondering which files the KB4571744 update included for the defrag/optimization fix – the defragproxy.dll, defragres.dll & defragsvc.dll files are v10.0.19041.487

the defrag.exe & dfrgui.exe files, however, are not updated with KB4571744
only the DLL files were updated

• This reply was modified 4 years, 6 months ago by EP.

1 user thanked author for this post.

woody

Reply | Quote

Wonder if we’ll see them today…

Reply | Quote

Today 28 August, so far nothing.

Reply | Quote

I’m still wondering how they managed to break something like this in the first place since it has always worked properly (for me, at least) up until 2004 was released?

Makes me also wonder what else is being broken every time a new Windows 10 version is released? Actually, make that almost every time ‘Patch Tuesday’ updates are released these days.

Reply | Quote

The update is intended for Windows 10 20H2 even though it will fix the bugs in 20H1.

Mayank Parmar wrote

Microsoft plans to roll out the same update to those with Windows 10 May 2020 Update (2004) later this week or before September 1.

I’m somewhat skeptical of that comment with no link to MS to back it up..assumptions meh!

Reply | Quote

GCG1000 wrote:

It’s about time MS fixed this problem!  I wonder if this “fix” will trim SSD’s correctly?

No, they didn’t fix the SSD defrag issue – see my addendum at

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

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

madquack

Reply | Quote

Defrag of SSDs is intentional:

Scheduled task

The defragmentation process runs scheduled task as a maintenance task, which typically runs every week. As an Administrator, you can change the how often the task runs by using the Optimize Drives app.

When run from the scheduled task, defrag uses the below policy guidelines for SSDs:

Traditional optimization processes. Includes traditional defragmentation, for example moving files to make them reasonably contiguous and retrim. This is done once per month. However, if both traditional defragmentation and retrim are skipped, then analysis isn’t run.

If you manually run traditional defragmentation on a SSD, between your normally scheduled runs, the next scheduled task run performs analysis and retrim, but skips traditional defragmentation on that SSD.

Windows 10 defrag documentation

CONCLUSION

No, Windows is not foolishly or blindly running a defrag on your SSD every night, and no, Windows defrag isn’t shortening the life of your SSD unnecessarily. Modern SSDs don’t work the same way that we are used to with traditional hard drives.

Yes, your SSD’s file system sometimes needs a kind of defragmentation and that’s handled by Windows, monthly by default, when appropriate. The intent is to maximize performance and a long life. If you disable defragmentation completely, you are taking a risk that your filesystem metadata could reach maximum fragmentation and get you potentially in trouble.

The real and complete story – Does Windows defragment your SSD?

1 user thanked author for this post.

woody

Reply | Quote

It seems that at 10:00 AM in Redmond, MS did not send a C / D patch for Windows 2004 in August (so far).

Reply | Quote

Looks like this STILL hasn’t been fixed after 6 months or so..

After the release of two Windows 10 feature updates and numerous cumulative updates, Microsoft has still not fixed a bug causing Windows Defrag to TRIM non-SSD drives…

bleepingcomputer article

If debian is good enough for NASA...

Reply | Quote