Optimize Drives>Never Run

Page 1 of 3 123 LastLast

  1. Posts : 10
    Windows 10 Pro + Ubuntu 20.04 LTS
       #1

    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
      My Computer


  2. Posts : 25,638
    Windows 11 Pro 22621.1
       #2

    It has been like this since the first IP of 19041.21vb. MS either does not want to fix it or they don't know how or care.
      My Computer


  3. Posts : 2,279
    Windows 10
       #3

    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...
      My Computer


  4. Posts : 24,574
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #4

    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
      My Computers


  5. Posts : 25,638
    Windows 11 Pro 22621.1
       #5

    Bree said:
    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
    It is and has been a known bug since day 1 of 19041. I and others have reported this many many times ob The Hub. I have sent tweets to MS, this just shows how useless the Hub is.
      My Computer


  6. Posts : 10
    Windows 10 Pro + Ubuntu 20.04 LTS
    Thread Starter
       #6

    Thanks guys :)
      My Computer


  7. Posts : 29
    10 Pro
       #7

    Helmut said:
    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...
    Yeah it matters to us whether it runs or not, It matters that it reports properly instead of reporting an erroneous message and it matters that microsoft is ignoring the issue!
      My Computer


  8. Posts : 2,769
    Windows 11 Pro, 21H2
       #8

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


  9. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503
       #9

    Was supposed to be fixed this past Patch Tuesday but the didn't release a CU due to finding another stopper bug. Maybe next Patch Tuesday?
      My Computers


  10. Posts : 9
    Win10
       #10

    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?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 07:36.
Find Us




Windows 10 Forums