Windows 10 2004 optimization/defrag bug

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.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I'm not sure if the problem was there before the 2004 update, I never really paid much attention to it until I became aware of the recent issue with the defrag/TRIM system.
After a reboot it did say that the drive was 0% fragmented, so I supposed that was a good sign.

It passed chkdsk fine, that's the first thing I checked to make sure there was no corruption on the drive!

I have a dual boot system, with Windows 10 and Windows XP, and I've tried running the Windows XP defragger on the drive, and it said it was still quite fragmented, so I guess the Windows 10 one didn't actually do its job.

The Windows XP defragger is now defragmenting it (taking ages) and when it's finished I will try running the Windows 10 one again to see if the result is any different now the drive should actually be defragmented.

Thanks, Dave.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

seems that the last optional update solved the problem, i tested a few times and no problem anymore.
Hunt or be Hunted

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The defrag finally completed in XP. It said it had done, but then carried on with what looked like a second pass, where again it stuck on 1% completed for ages. I guess that is the same process as on Windows 10 but it doesn't call the second pass "consolidation" as Windows 10 does.

Anyway, it eventually finished, and Windows 10 says the drive now doesn't need defragmentation, so I guess everything is OK.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I'd just like to offer a word of caution here. (it may never affect you, but)

Prior to Windows 10 I would dual boot using removeable caddies and my second hard drive was common between the two operating systems. (both windows) After some time I swapped the caddie and found the drive was no longer accessible to the older operating system. It seemed the newer one had done something the old on didn't like any more. I think the newer operating system was Windows 7 but I can't remember the older one.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This has finally been fixed for Windows 10 2004 in the September Cumulative update!  Confirmed on 2 different computers! It now remembers the last time you defragged/optimized your drives after a restart!

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Windows 10 update fixes annoying bug that affects your SSD drives

Some users believe that it’s not sensible to defrag the SSDs at all, but Microsoft experts have previously stated that Windows 10 does defragment your SSDs on purpose and it’s normal.

Typically, SSD is defragged once a month by default if you’ve Volume Shadow Copy feature enabled. Volume Shadow Copy is enabled when you manually turn on Windows System Restore, which is a feature that basically allows you to roll back to a previous version of the OS.

To facilitate the drives optimization process, Windows 10 comes with a tool called “Optimize Drives” that would record the last time a drive has been optimized/defragged/trimmed.

Windows also use the Automatic Maintenance feature to automate the defragmentation or optimization process.

Windows 10’s Automatic Maintenance is a feature that helps to keep your computer healthy with automated system optimizations when required. During its casual run, this feature will run specific maintenance tasks, such as security scans, system scans, and disk optimization or defragmentation.

The Automatic Mainataince feature relies on the “Optimize Drives” tool to see if the drives need to optimized (defragged when required). With May 2020 Update (version 2004), Microsoft broke the Optimize Drives (aka defragmentation tool) and the defrag tool was unable to flag that it’s already done a scheduled optimization on your SSD.

The tool could warn you that your storage is unoptimized when it is not. If you try to optimize the already optimized drive, the process will finish instantly and Windows won’t make any changes to the drives.

The problem about this flaw, though, is that the Automatic Maintenance feature could end up defragging your SSDs on every reboot because the built-in defrag tool doesn’t correctly report that it’s already done scheduled defragmentation on your SSD.

Microsoft patches the SSD defragger bug in September 2020 update

With Windows 10 KB4571756 (Build 19041.508), Microsoft has finally resolved the issues with Drive Optimize tool and Windows will stop defragging your SSDs automatically on every reboot.

Here’s a timeline of how the bug was discovered and acknowledged:

  • Windows Insiders flagged the issue in January 2020.
  • January’s preview Build 19551 resolved the issue.
  • The bug somehow slipped into the final release of May 2020 Update.
  • On August 14, Microsoft told us they’re aware of the reports.
  • Build 19041.488 August optional update fixed the bug in May 2020 Update.
  • Build 19041.508 patches the problem for everyone running May 2020 Update.

If you’re aware of any other issues with May 2020 Update (version 2004), let us know in the comments below.
Source: Windows Latest

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Just an update aside on this.

It looks as if things still aren't quite right.

I'm seeing this error recorded regularly in the event log -

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

You might be interested to know that my drive F: is a FAT32 formatted hard disk drive, not an SSD!

So, even though it appears as an HDD in the list of drives, it looks as if the system might be still trying to TRIM it!

Windows 10 can't TRIM FAT32 SSDs, but it can defrag FAT32 HDDs.

I have another FAT32 drive on the system which is not throwing the error.

Cheers, Dave.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Its acting crazy with a hard drive even with no fragmentation.Even on 20H2 its still not working correctly.Most people wouldn't notice this which is why its not being reported more.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated November 21, 2020 Views 32,142 Applies to: