I get the following error when attempting to install 19041.208 (I did verify downloaded file using checksum and I am installing using dism /online command) Code: Error: 0x800f0988
Why is everyone so focused on the optimize drive / defrag UI bug? It is only cosmetic, and I doubt you all run it several times a day.
Yes, it doesn’t attract error. Defragmenter works without errors. After the restart, it does not record the time of the last defragmentation. If you turn off the PC, then the next time you turn on the registration on the spot. This is nonsense that you should not pay attention to, nothing at all.
And why is that a problem? For an SSD it just trins the unallocated areas, which does nothing if they haven't been used since last trim.
Because it's the only bug i've noticed so far.. and probably because it could mess with the auto trim/defrag system, but i don't know s**t about that.
true, in fact, for SSD, defragment doesn't require nor matter much, it only depreciate the lifespan caused of the reduced TBW, since TRIM is natively supported so the only way I see & use that feature for my 5TB NAS, otherwise, all good since Dec-19 in my 7 different systems.
Indeed, Windows won't defragment SSD's, only trim them, so absolutely no harm from it being run daily (if that is the case).
About the Windows 10 defrag and SSDs, things might be a bit more complex. So for context, I have 2 Samsungs, a 970 Evo+ and a 850 Evo. For both, the Optimize&Defrag will schedule a "defrag" each month (even on the default HDD "Weekly" schedule). All good. The thing with the TRIM command is, I can execute it from something like Anvil's Storage Benchmark and basically nothing visible will happen on the SSDs. If I click Optimize though, it will trigger a write spike on the SSD (can be monitored with HWinfo64), that I've seen writing about 4-10GB on the SSD, the longer you wait between the optimizations, the more writes you have, the larger the write spike (it seems). So while in terms of endurance and SSD life 4-10 GB written every 30-ish days is absolutely nothing, it's still interesting to notice because Windows 10 seems to execute something other than just TRIM, what that would be, I cannot tell. It does say "Trimming" for SSDs, yes. Just a small peculiarity that everyone should be able to test.