Windows 10 21H1 now available for commercial pre-release validation
-
Avoid "expect" and "exact" then.
It was my personal option.
Some people need to read my comments fully & not jump to conclusions. I stated ‘I would expect not that I know & that patch Tuesday to be likely not that it would be released on that day.
I will make no further comments on this thread.
My comments are obviously not welcome here.
Last edited by Bastet; 18 Apr 2021 at 09:16.
-
-
I'm running 21H1 on my non-Insider machines and don't notice any difference at all between that and and 20H2 except what winver reports. There must be changes somewhere under the hood, but they are apparently hidden down in the dark recesses.
Possibly a new Windows Feature Experience Pack will be released nearer the time......
-
If You go to settings and The Windows Insider Section and click on "Stop Getting Insider Builds" and Turn on what is in the image below, you will go to the Regular Release Channel , but that may be due to the way 19043.928 was morphed from 19042 which was morphed from 19041.
-
I installed a clean version of 21H1 19043.867 as a non-insider. It became activated and has since received update to 19043.928 via Windows Update. It feels like the release of RC is close now.
-
-
So, there's no point to updating to 21H1 right now?
-
Of course, I have a backup of version 20H2 in case Microsoft changes its mind.
-
Although I'm on 21H1 I keep a thumbdrive for it and 20H2 at the ready just in case I decide to clean install either one. Right now since updating earlier this month I see several programs that have been broken such as EVGA Nu Audio, 3DMark and PowerDVD 20 Ultra and reinstalling won't fix them.
I'm very tempted to perform a clean install which would be time consuming since I'd have to open her up and remove nvme drives to isolate the boot drive for it. Once I get my laptop setup the way I want it I'm probably going to do it.
-
So, there's no point to updating to 21H1 right now?
As I see it, there's no reason to and no reason not to. I don't think it matters much. If you're currently running 20H2 and it's up-to-date, 21H1 is already present. It just requires unlocking. The enablement package that does it (KB5000736) is small: only 167kB.
-
I have no issues at all with it other than it is still in The BETA Channel.
-
-
I have no issues at all with it other than it is still in The BETA Channel.
I'm not sure that's as important as it usually is. All the CUs for 20H2 and 21H1 have been labeled 19041.xxx, which should be a pretty good indicator of how far things have – or rather haven't – advanced since 20H1.
Quote
