Known and Resolved issues for Windows 10 May 2020 Update version 2004

kado897 said:

Nope. Still broken.

Now that is really stupid.

Compumind said:

Now that is really stupid.

It's all over the Feedback Hub too. It's fixed in the Fast Ring builds so why not here?

kado897 said:

It's all over the Feedback Hub too. It's fixed in the Fast Ring builds so why not here?

I gave up with the Feedback Hub.

I've been thinking about this defrag UI bug, and have started to wonder if they are working on the code to bring it over into the Settings app under Storage where it actually belongs now, whether anyone like it or not.

I mean, like everyone else I would prefer a defrag UI that would show the pretty colored blocks being moved around, but that cost system recourses, totally unnecessarily.

Cliff S said:

I've been thinking about this defrag UI bug, and have started to wonder if they are working on the code to bring it over into the Settings app under Storage where it actually belongs now, whether anyone like it or not.

I mean, like everyone else I would prefer a defrag UI that would show the pretty colored blocks being moved around, but that cost system recourses, totally unnecessarily.

Looks like Auslogics, probably wrong. I liked the dancing blocks, too.

f14tomcat said:

Looks like Auslogics, probably wrong. I liked the dancing blocks, too.

Nope something more powerful: UltraDefrag download | SourceForge.net

You can fully optimize a hard disk at boot if you set the script up this way, Example for C: drive

Code:

@echo off
;--------------------------------------------------------------------
;                UltraDefrag Boot Time Shell Script
;--------------------------------------------------------------------
; !!! NOTE: THIS FILE MUST BE SAVED IN UNICODE (UTF-16) ENCODING !!!
;--------------------------------------------------------------------

;set UD_IN_FILTER=*windows*;*winnt*;*ntuser*;*pagefile.sys;*hiberfil.sys
;set UD_EX_FILTER=*temp*;*tmp*;*dllcache*;*ServicePackFiles*

; exclude big fragments which rarely benefit from defragmentation
; set UD_FRAGMENT_SIZE_THRESHOLD=20MB

; if your system drive is an SSD uncomment the following
; line to exclude slightly fragmented content as well
; set UD_FRAGMENTS_THRESHOLD=20

; uncomment the following line to increase amount of debugging output
; set UD_DBGPRINT_LEVEL=DETAILED

; uncomment the following line to save debugging output to a log file
set UD_LOG_FILE_PATH=%UD_INSTALL_DIR%\logs\ud-boot-time.log

udefrag -o C:
udefrag %SystemDrive%


boot-on

exit

Most of those "newly discovered" bugs are either longstanding or recurring. Mention of them pops up with every new build and we all marvel about how could have they missed it now and than they fade away or get fixed until next build. Some would inevitably make out of it a "tempest in a teacup" while MS says that it's looked at and will be fixed soon.
Altogether, why the heck are we surprised ?

Compumind said:

I gave up with the Feedback Hub.

It’s like they have thumbed their noses to the feedback hub so I wonder why there is a feedback hub. The defrag is important to me and countless others on this forum.

magilla said:

The defrag is important to me and countless others on this forum.

It's far from critical, believe me, lol.
If MS knew about the problem, I can't understand why it's not in this build.

I'm only concerned about the scheduling.

For me, defrag is not important at all, fragmentation has been minimal ever since W7 and haven't gone past a percent or so even with autodefrag is off. I just run manually Optimize on SSDs about once a month. Here's a HDD that wasn't ever optimized in couple of years and used for transient storage only.

And second HDD even older (3 years) used for everything including downloads and temporary data

As long as there is enough free space fragmentation is minimal to non existent.