Windows 10 2004 optimization/defrag bug

Anonymous
2020-05-29T10:31:40+00:00

Hi all

I've just completed the Windows 10 2004 upgrade and I have noticed 2 issues.

  1. When I manually trim my SSD in the drive defrag/optimize tool in windows and I reboot it says 'never optimized' when i go back. I heard this was a bug in insider preview which they obviously didn't fix. 
  2. I happened to have the defrag/optimize tool open at the same time as Control Panel\All Control Panel Items\Security and Maintenance, I initiated a manual maintenance and I caught windows defragging my SSD and then it trimmed it straight afterwards. If i click the optimize button in defrag/optimize tool it only trims it and not defrag.

This seem to only happen when Control Panel\All Control Panel Items\Security and Maintenance initiates its automatic maintenance or if I select start maintenance.

This is concerning as it should never attempt to defrag an SSD.

My laptop is only a few months old and came with a PCIe SSD and Windows 10 1909 so there is no compatibility or lack of trim support issues obviously.

I have disabled scheduled weekly optimizations in the defrag/optimize tool which prevents it from attempting to defrag when the control penal maintenance attempts its maintenance when the computer is idle.

I want to let everyone know that this is happening so others are aware. My other computers that have the latest update are also doing it.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

171 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-05T18:18:04+00:00

    Glad I found this thread as I was seeing a problem with disc optimisation too.

    In my case I have a normal HDD (Drive F:) on the system which I keep getting error messages written into the Windows Event Log about on every boot. Strangely I've had Windows 10 version 2004 for a few weeks now, and these errors have only just started to appear.

    "The storage optimiser couldn't complete re-trim on CAPTURE (F:) because: This operation is not supported on this file system. (0x89000020)".

    So, it's trying all the time to TRIM a conventional hard drive!

    What a mess....

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-05T18:43:18+00:00

    Yep, we all get same trim error for HDD.  Luckily that doesn't cause any harm.  But doing a full defrag on our SSDs after every boot is really bad for the SSD.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-06T12:35:36+00:00

    Some conventional drives support trim (SMR ones). Error is why defrag tries trim on drives without support.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-07-06T16:21:56+00:00

    Good point, but the HDD trim  error in event log never occurred until MS messed up Defrag in 2004 update so I'm guessing Windows can identify a hybrid drive that supports trim and only trim hdd's that need it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-11T04:14:22+00:00

    This caused SSD errors on my laptop.  Had to initiate a full ScanDisk to fix them - will have to replace the NVMe SSD in it, now, because I don't trust them once they start to give these types of errors.  Too bad, $150 down the drain!  Drive is only like 6 months old.  4TBW on the drive.  Endurance rating is 200TBW.  Errors happened about 2 weeks after installing this 2004 update, which is when I noticed the Optimizer was broken (when drive has errors it will not be shown in the optimize window - so that's a red flag that this is starting to kill your SSD).

    Turn off the automatic optimization.  This bug defrags your SSD on every reboot, which is very bad.  If you want to kill your SSD, then sure... keep it turned on.  Otherwise, you have been warned.  Also, this is REALLY bad for people with devices that have eMMC storage - like Surface Go and similar tablets.  That storage tech seems to die really fast from repeated defrags, like SD Cards and thumb drives do.  Those people REALLY need to TURN OFF AUTOMATIC OPTIMIZATION.

    Massive, drive killing, bug.

    Surprised this was allowed to go live before it was fixed.

    I have turned off automatic optimization on both of my machines.  They both have this bug.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments