Windows 10 Insider Preview Beta Channel Build 19042.487 (20H2) Aug. 26 Insider

jimbo45 said:

Hi there
possibly true -- but as it works on other builds it has to be a combination of the environment - things like Office are quite tightly integrated within the OS so unless you are a developer on these things all the user (i.e me) can say --it was working before but not now so "something is broken" !!!!!.

Problem with this type of error it's not regularly reproduceable --intermittent faults are the worst kind to fix whether in I.T, Engineering or anything else.

As for the rest of this build I'm happy so far with it.

Cheers
jimbo

Me, too! I'm giving 7:5 this will show up as "D" channel today for 19041. RP is, and if nothing super serious happens, 20H2 will be "triggered" in a few weeks.

I never said any of this

kado897 said:

They may have fixed the date problem with defrag but it is still trying to trim HDDs

Agreed Kado
I have good old WD Black Caviar HDD'S. So from reading articles because I really was tired of reading the same thing over & over, The defrag issue is partly fixed because there are 3 problems:

1) The more serious one:
defrag of SSD drives too often
2) The less serious but still annoying one:
forgets when it last optimized a drive.
3) The obvious but still annoying one:
Tries to trim HDD's.

So, 1 and 2 seem to be corrected, but 3 is a no go with latest update.

Zardoc said:

Agreed Kado
I have good old WD Black Caviar HDD'S. So from reading articles because I really was tired of reading the same thing over & over, The defrag issue is partly fixed because there are 3 problems:

1) The more serious one:
defrag of SSD drives too often
2) The less serious but still annoying one:
forgets when it last optimized a drive.
3) The obvious but still annoying one:
Tries to trim HDD's.

So, 1 and 2 seem to be corrected, but 3 is a no go with latest update.

I don't think it's doing any harm, it's just annoying.

Most Windows issues are annoying like event 10016 DCOM errors, event 642 Esent errors and other events like Event 2 PerfDiag, Event 37 Kernel-Processor-Power, Event 64 F0DB7EF8, Event 219 wudFrd, Event 1014 DNS. SAM errors Appinit errors etc..

These errors are for the most part like you said « ANNOYING » to say the least and can be solved very easily by MS. Unfortunately the Term « BY DESIGN » is the term always used by MS which in their dictionary means (WON'T FIX).

Man, you created the error, just fix it and let's move on to more serious problems!! It's only when there is a large public outcry that MS acknowledges what was quite obvious from the beginning.

MS still argues that the monthly defrag of SSD's is warranted but ever since I've been using them the makers have been saying « DON'T DEFRAG ! » I Haven't seen any makers change their position because then, it would be logical to follow suit.

The SSD mindset reminds of the « let the battery drain for memory » issue with cell phones and Laptops

New Weekly Windows 10 Insider Program Pulse Survey - August 28

The term "defrag" has been around for decades and decades. It's ingrained in our speech when we speak of storage and storage devices. The term Optimize is relatively new in comparison. It is very common, and understandable, that the term Defrag when speaking of SSD devices is taken to mean trim/re-trim, not the historical HDD interpretation. Eventually, everyone (almost) will use the exact proper term for the device in question. Until then the terms will be interchangeable, and just a tad of common sense when reading the context resolves the meaning.

f14tomcat said:

The term "defrag" has been around for decades and decades. It's ingrained in our speech when we speak of storage and storage devices. The term Optimize is relatively new in comparison. It is very common, and understandable, that the term Defrag when speaking of SSD devices is taken to mean trim/re-trim, not the historical HDD interpretation. Eventually, everyone (almost) will use the exact proper term for the device in question. Until then the terms will be interchangeable, and just a tad of common sense when reading the context resolves the meaning.

I'm with you Tomcat, but MS should be the first to change the interpretation from Defrag to trim of SSD because it still shows defrag when maintenance is launched.
VIDEO