KB4568831 Cumulative Update Windows 10 v2004 build 19041.423 - July 31 Win Update

Cliff S said:

They haven't even acknowledged it exists, is what is really getting my goat.
Not in a blog, not in known issues, not in all the threads about it in answers.microsoft.com their own forums, and not in any of the Feedback hub threads.

Cliff, why don't you try Defraggler program by Piriform company its.. FREE! lol
Download Defraggler - File & Disk Defragmentation

I use it all the time... works great for me..!

I guess I will give this update a go..!
WISH ME LUCK! lol

EDIT:
ok I'm back no issues detected yet...
ie. it did NOT bork my Win10 install ^_^ huwayy!

Cliff, why don't you try Defraggler program by Piriform company

Windows Defender doesn't like anything by Avast for me. Picked up Ccleaner and Speccy installers on an old SD card I plugged in.

With Build 19041.423 (KB4568831) it's possible to get "new" Start menu.
Open Notepad and paste in the following:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\0\2093230218]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

Save the Notepad file as 20H2.reg and double-click on it to apply the registry changes. Reboot your system and you should have the new menu.

mfessler said:

Please excuse the request, but as long as one (or more) of the problems doesn't concern or bother me, it is absolutely fine to just ignore these previews, because the fixes will come with the next CU anyway - have I understood that correctly?

Regarding the defrag problem:
Some say until this bug is fixed, it is important to deactivate the optimization schedule, otherwise a SSD is trimmed each time the system is started.
Others mean it is practically only a "cosmetic problem" because the maintenance task is controlled independently.
Now what's wrong?

Thanks and regards!

Yes the next CU will include this one but any issues found may be fixed. The defrag problem. No one knows for sure except MS and they are not saying. The safest course is to disable automatic defrags and if needed do them manually. SSDs should not be done more often than once every 28 days, which is what the defrag program does if it is working properly.

pietcorus2 said:

" still no fix or even an acknowledgment of the Optimize Drives bug "..........it seems to be too difficult to fix for MS , so no acknowledgment !

Word is it is fixed in the Dev Channel but I can't test because my Dev build is in a VM.

kado897 said:

Word is it is fixed in the Dev Channel but I can't test because my Dev build is in a VM.

It was never problem in Dev channel, always worked fine which makes it more perplexing. I switch to it at least once a day.

CountMike said:

It was never problem in Dev channel, always worked fine which makes it more perplexing. I switch to it at least once a day.

I can't remember Mike. Wasn't 19041.1 in the Fast Ring at one time?