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 No comments

171 answers

Sort by: Newest
  1. Anonymous
    2020-06-17T19:25:51+00:00

    Thanks for posting this. 

    Very resourceful. 

    This is exactly what I was talking about.

    hi GKD_799.

    I just don't understand why Microsoft has been unable to fix this defrag problem for v2004.

    this bug has been there since build 19041.1 and still not fixed with the 19041.329 & 19041.330 builds (but was somehow "fixed" in some insider build in the fast ring in early 2020 and the fix was not "backported" to v2004)

    edit - I'm encountering this defrag problem on an HDD rather than an SSD.  so it affects both HDDs & SSDs.

    2nd edit - this "MS defrag" problem was apparently fixed starting with insider preview build 19551 but did not make it into the v2004 release.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-06-16T07:35:41+00:00

    Hi All,

    I found an article.

    https://www.bleepingcomputer.com/news/microsoft/windows-10-alert-defragger-bug-defrags-ssd-drives-too-often/

    So, now, it is negative situation for SSD.

    From the article,

    "This is a problem, as defragging an SSD too much is not good for the drive as it could prematurely reduce its lifespan.

    Until this issue is fixed, if you use an SSD drive, it is suggested that you disable the automatic drive optimization of SSD drives in Windows 10."

    HTH

    Thanks for posting this. 

    Very resourceful. 

    This is exactly what I was talking about.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-06-16T07:05:39+00:00

    Hi All,

    I found an article.

    https://www.bleepingcomputer.com/news/microsoft/windows-10-alert-defragger-bug-defrags-ssd-drives-too-often/

    So, now, it is negative situation for SSD.

    From the article,

    "This is a problem, as defragging an SSD too much is not good for the drive as it could prematurely reduce its lifespan.

    Until this issue is fixed, if you use an SSD drive, it is suggested that you disable the automatic drive optimization of SSD drives in Windows 10."

    HTH

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-06-15T06:08:24+00:00

    Same here!!

    There are many other issues around 2004!!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-06-15T03:11:41+00:00

    I have actually encountered this issue in 1804. Filed a bug report in 1809. All of my bug reports in windows feedback have been completely ignored.

    Issue is present in;

    1804

    1809

    1904

    1909

    2004.

    Was this answer helpful?

    0 comments No comments