KB4566782 Cumulative Update Windows 10 v2004 build 19041.450 - Aug. 11 Win Update

bobcollard said:

I would consider the company who made the SSD drive you are using. You may find they have an optimization for your brand and advice. As for Micro Soft, I would not depend upon them to fix this problem, sooner or later.

The manufacturers are giving general advice for use of their SSD with many OS/file systems, some of which do not support file system level TRIM, like FAT32. NTFS does support TRIM at the file system level. You can also disable TRIM at the file system level (it is enabled by default for NTFS), so manufacturers also must assume this can happen.

Ztruker said:

Re TRIM/DEFRAG. This was posted recently but I can't remember where or by who. Good article though:

The real and complete story - Does Windows defragment your SSD? - Scott Hanselman

That contains some good information I was not aware of. The file system queues up TRIM requests to the SSD when files are deleted, the queue is limited in size, and if the queue is full, TRIM requests are dropped. So if you are performing lots of deletes on a busy system you can potentially drop some TRIM requests. The SSD won't know those blocks are free unless they are written to or the reTRIM command is issued by defrag optimize.

After the the update i started to get this error in my event viewer

Ztruker said:

Verified. I removed the registry hack for the new start menu, rebooted and the version is back:

You are right, Rich. The screenshot below doesn't show it (Version 2004) anymore after applying the registry tweak. I used to have before: