Optimize Drives>Never Run

I ran ''optimize'' several times and every time when I close and reopen the window I see this ''never run'' (see screenshot) . Drive C is SSD.



When run ''optimize'' for drive D (HDD) I see this in event viewer:
''The storage optimizer couldn't complete retrim on Media (D:) because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)''

After 2004 update. PC run flawlessly. I catched this accidentally, while searching for other in event viewer

It does not matter whether it runs or not, most of the optimisation is done by the controller and firmware within the SSD.
The process is very different to a mechanical HDD. Even in the latter case there is Prefetch and Super Prefetch, all on a modern disc filing system not prone to defragmentation in the first place.
No worries, carry on...

poeblightleague said:

I ran ''optimize'' several times and every time when I close and reopen the window I see this ''never run''....

....After 2004 update. PC run flawlessly. I catched this accidentally, while searching for other in event viewer

This is a known bug in 2004 (though not acknowledged by MS yet). It has not been fixed by the latest CU 19041.329. It is reported as being fixed in the latest Fast Ring Insider builds though, so it's not as if MS don't know how to, just that it's not high on their priorities

Thanks guys :)

Microsoft has officially acknowledged this issue and is working on it.

If you look in the Event Logs - Windows Logs - Application (filter for Defrag) you will see that the drives are getting optimized on schedule. The Sorage Optimizer (aka Disk Defrag) is not picking last run status information.

The log also shows
Event 258, The storage optimizer successfully completed defragmentation on (C:)
Event 264, The storage optimizer couldn't complete retrim on HGST (D:) because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)

Since the UI shows whether the media type is SSD or harddrive why does it attempt retrim a harddrive?

In another thread it was said that a defragmentation is not actually done on SSD but that is just an null operation message. But is it? When you manually optimize a SSD the Event Log shows only that the retrim was successful and nothing about defragmentation. Similarly when you manually optimize a harddrive the log shows only the defragmentation event and no corresponding retrim error.

Could it be that the scheduled tasks simply issue a retrim command followed by a defragmentation command to all drives (depending on configuration) regardless of media type?