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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-08-07T00:29:21+00:00

    It's a pity that they fix it on the next build of Windows - I wonder if the fix will become available for current version (2004 and 20H2).

    I reported many bugs via Feedback Hub.

    If a bug is cosmetic and/or not resulting in data loss, privacy breach, loss of functionality, etc., (to add salt to the wound, if a bug is not severe, not widely published, not widely complained), they won't deliver the fix via Windows Update, but they will fix it on the next version of Windows, leaving current users with unfixed, reproducible bugs.

    Such reproducible bugs means I have to avoid certain ways I use my computer.

    For example:

    1. On Windows 10 1511, 1607, and 1703, try to press Winkey+X more than once. See that the shutdown sub-menu (options to sleep, shutdown, hibernate) becomes discolored. I report it in v1607, and they fixed it in 1709. Update 1511, 1607, and 1703 with the latest cumulative update, the bug is still there.
    2. On Windows 10 1903/1909, open advanced indexing options and Settings (the modern Settings app) at the same time, and go to Search settings. Try to rebuild index, the Settings app will crash. No fix even with the latest (July 2020 build 997) cumulative update. This problem is fixed in 2004.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-02T14:03:17+00:00

    thank you for that info, i will wait for that build then

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-02T13:58:51+00:00

    at this point, i dont think microsoft will fix it anymore...

    you are wrong. Microsoft has fixed the Defrag Bug in Windows 10 Build 19551. The next update feature will be code name manganese.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-02T13:31:33+00:00

    Of course they will fix it, it's a serious flaw, which could potentially seriously shorten the life of SSDs in systems where people aren't aware of it!

    IIRC the story was that it was actually fixed in an earlier build, but then regressed for some reason, so they have done the work on it.

    Why they haven't just rolled the fix out again in an update is a mystery, maybe there was another issue with it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-02T12:37:40+00:00

    at this point, i dont think microsoft will fix it anymore...

    Was this answer helpful?

    0 comments