Disk Optimization IS NOT Running Automatically Properly

Question

Eddie, recall my stressing the importance of showing last run date in thread for disk optimization. Not positive if this started with 19042.508 /546

First noticed this in my main system last week running 20H2 (non-insider). Disk Optimization is not running automatically, had about 13 days showing last run, settings are at default to run weekly. Did a manual run back last week.

This snapshot is from a virtual machine 20H2 that I test software on daily. Both devices are kept current with builds.

This snapshot is from my main system today. Have to give it couple more days to verify and will file a FBH report at that time and update this thread. Please advise if there is anything else I can add with FBH report.

Regards,

Answer 1

Hi Johnny,

Have you come across the Docs for defrag as I haven't read this before so thought I would post it?

There are some interesting points.

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/defrag

Heres my system in which my HDD are defrag but like the points say SSD's  can not be scheduled. 

Answer 2

As per the Microsoft article whose link you supplied, SSDs cannot be scheduled to be defragged. The following screenshot, in the white rectangle, is from the article.

For SSDs, Trim is meant by defragmentation, I believe, and by the article, it is my understanding that Trim cannot be scheduled to run periodically.

Is my understanding right ? If yes, when does Trim run ? Does SSD firmware decide if Trim should run or not run ? 

Can you or some other forum member who has knowledge on this shed some light on this situation ?

Answer 3

Thanks Suat and Bryce for adding to this thread,

As Suat mentioned, from the article Bryce posted, "You can't schedule to defrag a SSD or volume on a VHD that resides on an SSD." This is understandable point regarding VHD on SSD, it is not clear as it fails to mention trim, only defrag.

In my first example, the Host (VMware) resides on SSD, the virtual machine resides on a separate HDD. The vm's manually Defrag, not Trim. As my main is Legacy bios as well as the vm's, in this example, Disk Optimization did automatically Defrag "System Reserved", but not the main Drive C: partition. This clearly shows a problem.

In the second example with SSD and HDD, the HDD's were maintained, not the SSD so it comes down to:

As all SSD's use Trim rather than Defrag, does or does this not still get scheduled with Disk Optimization?

Bryce, perhaps you recall the thread regarding Disk Optimization fails to retain last run info. Everyone was telling me it runs in the background, was a cosmetic issue. The subject of Defrag or Trim never came up.

It was not good enough for me, had to dbl check on all remotes that I maintained. Some questioned the hours wasted. It is what it is. Glad to state fully retired from freelancing. The gov taxes made it so, was not worth the effort. More time for me to annoy MS  :-)

Anyhow, hopefully Eddie or Jason can clarify if this be the case regarding Trim with Disk Optimization. Is this by design or a flaw?

Have a great day everyone!

Regards,

Answer 4

Here is one of my machines, all have SSDs and HDDs..

Answer 5

Today's Update: