Mmmh, still no additional cumulative updates other than .21 yet (Production/Release channel, No Insider). That's a bit suspicious considering current official builds are getting a second batch of CUs instead. Let's hope 19041 will remain the real RTM, as I already clean installed it on my main machine (and it's already working great) so far
Or simply forget clean installs forever unless you are sure your current installation is broken and irreparable (or would take more time to get if fixed than to start over).
I did direct update on my friend laptop from 17134 to 19041 everything went good but computer after update was useless. Main problem, it was impossible to switch laptop off in other way than removing battery. Choosing "switch off" from menu caused black screen and computer was still working until battery flat. Second problem system didn't recognize anything connected to any usb port. I had to do new clean installation and after clean installation works like rocket. One thing I noticed during clean installation is that in older version when you installing clean system, after setting your partition, system automatically sets 3 extra small hidden partitions. Now only 2.
unbeleivable mess by MS, half of world users are unable to upgrade, or have issues majorly with laptops etc. Yet, they are still looking into "some users are unable to upgrade to latest buils with error code...."
Clean Installation > Upgrade/update. Always. For real? Even this isn't a public build at all ATM, & you're complaining about this upgrade flaw of a BETA /under testing build/OS? Alteast should've waited until MS released v20H1 publicly/GA with (any) bug,
It's not problem at all if u at least don't complain about problems with it. It's f**king free to use and you know that before u r installing such a software. If u want to improve windows use the friggin' feedback hub to make it even better for all of us! I don't get all that whining all the time. Just make sure you have the best start to install a fresh build and if it fails just rollback und take the next build. No one is forcing you doing anything. Just stop the crying. Thank you.
Something is terribly wrong in the land of oz, toto, if a build that is set to become RTM and has been signed off and starts to get patched with cu's and such, is unable to be installed at all, has boot issues with the boot wim files, brakes notebook computers , messes with functionality, badly responds to /component cleanup commands and becomes unbootable, and i am talking about the entire code base, not just 20H1, as other builds from the same general time and other branches suffer from similar issues. A stability and RTM readiness is first and foremost determined by broad compatibility and ease of deployment, upgrade or clean install whatever the case may be.
It will be the next 2004/20H1, there is no other slow ring build developed since. It will be in IP for a while, before it will go GA.