Optimize Drives>Never Run

Page 3 of 3 FirstFirst 123

  1. Posts : 2,768
    Windows 11 Pro, 21H2

    Let's add a little detail and clarity to this issue...

    First, the bug that has been discussed in this thread is that Windows failed to recognize that a recent optimization operation on HDs and SSDs was already run and as a result would repeatedly perform optimizations on the drives.

    That bug was first resolved in preview form with the Windows Cumulative Update preview release of Sep 3, 2020 and then in final form with the Sep 8, 2020 Cumulative Update. From the release notes (https://support.microsoft.com/en-us/help/4571744):

    "Addresses an issue that causes the Optimize Drives dialog to incorrectly report that previously optimized drives need to be optimized again."

    If you have any cumulative updates from September onwards, then that bug is a non-issue.

    @GracieAllen, my next question would be this:

    What is your O: drive? I know it is 4TB in size. Since 4TB drives are not very common yet, would I be correct in assuming that this drive is NOT an SSD?

    If that is correct, then the real question here simply becomes "Why is Windows attempting to perform TRIM operations on a non-SSD drive?".

    To see what windows thinks this drive is, please open a PowerShell prompt and run this command:

    PowerShell "Get-PhysicalDisk | Format-Table -AutoSize"
    Here is an example of the output. Note the differentiation between SSD and HDD.

    Optimize Drives>Never Run-image1.jpg

    Some reference material:

    For a discussion of what TRIM is, see these articles:

    What is SSD TRIM, why is it useful, and how to check whether it is turned on | Digital Citizen

    What is Trim? | Crucial.com

    What about ReTrim?

    Take a look at the discussion in the below thread from just a few days ago. This is a perfect example of where ReTrim can come into play and how ReTrim can be triggered manually from a command line or the GUI:

    Is there an easy way in Windows 10 to re-TRIM empty space on an SSD?
      My Computers

  2. Posts : 805
    Windows 10 Professional x64 21H2

    GracieAllen said:
    I"m getting this error:
    The storage optimizer couldn't complete retrim on 4TB Originals (O:) because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)

    Which I presume is the same bug... 20H2 DIDN'T fix it? And 21H1, whenever that arrives WILL fix it?

    "Samsung Magician" Will do the job for you seeing that you have two Samsung SSD's. I use it on all my Samsung SSD's.
      My Computers

  3. Posts : 353
    Windows 10 Professional

    Yes, "O" is a 4TB HDD. There IS a 4TB SSD in the system, but this isn't it...

    I went into the event viewer to see if something else had thrown a bunch of errors and hit this one - 4 times, once for each partition on the drive.

    It looked odd that it would be complaining about trimming a drive that isn't an SSD so I went looking and found this...

    Long as I know it's just another design feature I'll ignore it... LIke all the other clutter in the Event Viewer...
      My Computers

  4. Posts : 2,768
    Windows 11 Pro, 21H2

    I'm still curious what the PowerShell command that I provided shows. Does it for some reason think that the disk in question is an SSD or does it properly identify the disk as a HDD?
      My Computers

  5. Posts : 8
    Windows 8

    hsehestedt said:
    I'm still curious what the PowerShell command that I provided shows. Does it for some reason think that the disk in question is an SSD or does it properly identify the disk as a HDD?
    Hi, I have the same error as GracieAllen, I tried your command, and my HDDs are recognized correctly
    Optimize Drives>Never Run-physicaldisk.jpg
      My Computer

  6. Posts : 2

    Hello there,

    Has anybody managed to fix the issue for HDDs? I see it with Storage Spaces and a Simple pool.
      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 16:48.
Find Us

Windows 10 Forums