[why to run 3x to defrag to 3% fragmentation?]

Thank you for your kind view point.  I absolutely agree that there is never a state of complete defrag as windows begins writing files.  I have 2 interesting points to make.

1-In the old days of Norton a defrag in W3 was a single choice and it didn't take that long and it looked like it did consolidation except it was only called defrag.  No one told me we now have a "consolidation" aspect.  As I recall defrag once was good enough as a 2nd time was a waste of time on a 3 megabyte disk.

2-For fun I did the File defrag 6 times and each time it got shorter till the process took less than a minute.  Then I rebooted and did file defrag again about 8 times.  At the start it took several minutes while I wondered where did all the defrag come from after reboot.  But again the process wound down to less than a minute.  My point being that the old days of doing once and being done are gone.  But defrag a few times may help and then -like you say- you and I defrag waaay more than necessary.

My disk performance is always more responsive after defrag which is the whole goal.  I can hardly wait till I get a SSD for really fast response in defrag and opening apps.

[why to run 3x to defrag to 3% fragmentation?]

Thank you - I didn't know defrag had 2 flavors.  I will use the file defrag vs consolidation.   Suggest better description of this difference since it was there all the time and I never knew it.    Perhaps a button called "Defrag-files" and a "Learn more" button so people like me won't assume "Defrag" means "Defrag-files" only.  Again many thanks.

[why to run 3x to defrag to 3% fragmentation?]

33 minutes ago, nukecad said:

Defragging the full disk can actually fragment some fies as it tries to fit them into the smallest number of clusters it can.
So as you found you can end up with more fragmented files than when you started.
Full disk defragmentation is not needed so much with todays larger capacity disks.

Once you have done a full disk defrag if needed on an untidy disk, then the best way in future is to do a 'file defrag' for normal use rather than a full disk defrag.
It's also a lot quicker.

A 'file defrag' is actually consolidation of the files into one piece each, rather than what is traditionally called defragmentation which tries to free up as many whole clusters as possible.

What most people want these days is to have their files in one piece each (consolidated) and not worry about a bit of empty space in some clusters.
And that's just what a file defrag will (attempt to) give you.

See the third option "To defragment multiple files:" here: (Once you've used it you'll soon get the hang of it).
https://www.ccleaner.com/docs/defraggler/using-defraggler/defragmenting-a-folder-or-file

 

[why to run 3x to defrag to 3% fragmentation?]

Why after the first run of defraggler the result says 3 fragmented files and 3% fragmentation.  Then upon immediate restart there really is 40+ fragmented files and up to 8% fragmentation.  I repeat this up to 5 times and finally the restart fragmentation percentage matches the end of the previous run fragmentation percentage.  I'm running this on a i7 laptop with W10.

Is there a way to defrag once and be done?