Britec on YouTube reports 2004 bug you likely have

Greetings,

Ignorance can be bliss. All four of my PCs finally updated and everything seemed good. I subscribe to a Windows YouTuber who has excellent advice most of time and he just warned of this bug. All 4 of my various PCs had it.

YouTube

Basically there's an SSD defragging script in Windows. 2004 update changes it from once a month-ish to several times a day. This made Brian nervous and so he explains how to turn it off.

It's easy.

1. Windows key and type DEFRAG. Select DEFRAGMENT AND OPTIMIZE DRIVES.
2. Select C drive and click CHANGE SETTINGS



3. Uncheck these two bad boys



4. Okay and save both windows. Now it won't check it AT ALL.

5. I guess you have to wait a month or so until you hear word it's been fixed. Then turn stuff back on.

(At his link he tells you how to protect your C SSD drive while allowing other drives to be checked normally.)

Here's some discussion on the topic --

https://answers.microsoft.com/en-us/...13b6f33?auth=1

I'm still running Win 10 Pro build 1909 and it had the exact same settings (Optimise drives enabled). This is on a laptop with two SSD's, no HDD's. I set them to off now. (I am able to install 2004 but have been delaying as I know there are a few bugs that need to be swatted).

However, before turning off I selected the Optimise now button and it goes thru the disk in about 1 second so it is not doing a traditional defrag. It said "trimming" but it is so quick, which might then not be as bad as you think? Whatever it might be doing, there is not much, if any writing to the SSD going on there. I would hope that by now, Windows is advanced enough to recognise SSD's and not be messing unnecessarily with them.

GregH said:

However, before turning off I selected the Optimise now button and it goes thru the disk in about 1 second so it is not doing a traditional defrag. It said "trimming" but it is so quick, which might then not be as bad as you think? Whatever it might be doing, there is not much, if any writing to the SSD going on there. I would hope that by now, Windows is advanced enough to recognise SSD's and not be messing unnecessarily with them.

One of the reasons I shared this was to see if anyone had responses like this. I'm not familiar enough with Windows to know if Britec is misguided. So I listed that discussion at MS at well. It may be a perfectly harmless bug but I'd rather not risk it.