I just got a CU preview for .NET 4.8 KB4562899. First time ever that i got a preview on Windows 10 and why on earth would i want a preview on my system since i'm not signed as an insider on this PC?
I completely agree with you. I am not signed up with MS as an insider, so why would I want a preview cumulative update. Sure, there is a changelog, but that doesn't mean that preview builds are considered "stable". When I worked at MS, we were taught that Beta means Broken! And a preview CU is a type of Beta. The best version of Windows 10 to implement at this time is 19041.388. Not 19041.421, 19042.388, 19042.421. With 18362 (v1903) some of us were at 18362.1002 when we wanted to transition to 18363 (v1909). This posed a problem because the enablement package was not designed to work with 18362.1002. It was meant to be used with 18362.418 (or earlier) to transition to 18363. Fortunately, a script was developed to get us back to an earlier build of 18362 so we could apply the enablement package to get to 18363. Using the script was OK, but it was an awkward method. It would have been better to not have applied so many CUs to 18362 until we got to 18362.1002. I've had to edit this post becuase 19041/2.423 has been released as a stable builid.
Updated the 2004/9 Updates Overview, added the preview catalog updates (some are on public WU too): https://forums.mydigitallife.net/th...-20h1-2-vb_release.80763/page-16#post-1571109
Why do you keep the 2 CUs, if both are offered in the MS catalogs ? Because .388 is a "public version" and not .423 ?
What's a preview CU, something like a beta CU? If so, should I install it or wait for a stable release?
Don't you just love terms like: "...ongoing stabilization of business continuity..." Look at some examples of stabilization: Enablement from 18362.1002 to 18363.481 could not readily take place. Releasing KBs with the same numbers that result in different build numbers. kb4567523 results in 19041.331 for 19041 kb4567523 results in 19042.292 for 19042 when it should be 19042.331 Using the same KB for different builds: kb4568831 results in 19041/2.421 on 7/24/2020 kb4568831 results in 19041/2.423 on 7/31/2020 Does "B" mean beta release?
B is fot the second week of the month C for the third etc. B updates are the ones that come out every second Tuesday of each month on windows update.
Just to inform what is what, people who like to stay on the safe side can use the public on WU updates, the daredevils can go the preview route ps, MSFT published some info on the subject: https://forums.mydigitallife.net/th...20h1-2-vb_release.80763/page-191#post-1610553
There is nothing different between previous non-security CUs and the new Preview CUs, all contain previous security fixes + new quality fixes they just added "Preview" to the label welcome to Win 7/8.1 updating scheme, they got that "preview" term since 2016
That's what i'm saying. In the Win 7/8.1 era a "Preview update" was posted under the "Optional updates", you could choose it install it or not, and if everything was ok, it would become next month's stable update and posted on "Critical updates" on WU. Preview is beta testing for me (i have quoted a piece of their document saying that) otherwise there's no need to confuse people,if it's not a beta keep the naming and release as it is with every other update. Not to mention that a normal user cannot avoid it on his/hers machine. Why should everyone become guinea pigs. Of course you're gonna tell me that even the "stable" ones have proven more than often to be problematic updates many times and that everything is Beta. Microsoft, i love you but...