Preview Build 18362.10022

[Trouble]

Day old news

Today we are releasing 19H2 Build 18362.10022 to Windows Insiders in the Slow ring. This build includes the improvements and fixes from KB4515384 as well as general improvements to the overall quality of 19H2.

SOURCE: https://blogs.windows.com/windowsex...w-build-18362-10022-19h2/#gDEEh5xl1Mtvslw1.97

 

[Regedit32]

Nothing sticks out as a major change.

It did install a little faster than last weeks effort though.

 

[Trouble]

Not sure what's going on exactly but it looks like everyone in the release preview ring is basically running the same build even though it might reflect different numbers 18363.387 versus 18362.387 (which by the way is the same version I'm running on my non-Insider machine) OR more accurately the common publicly available and current version of Windows 10

UPDATE 9/27: Today we have enabled 19H2 Build 18363.387 for Windows Insiders in Release Preview. This is just a small refresh update from Build 18363.385 with some fixes for uninstalling 19H2 updates.
UPDATE 9/25: Today we have released 19H1 Build 18362.387 for Windows Insiders in Release Preview who are still on 19H1 only. This is just a small refresh update from Build 18362.385. We plan to enable this update for 19H2 soon.

SOURCE: https://blogs.windows.com/windowsex...livery-approach-for-19h2/#6M4hr1f3hkXtYmjt.97

 

[Saltgrass]

Not sure what's going on exactly

Trouble, do you think there would ever be a situation where full build upgrades were not released by the build would be upgraded by several special CUs?

I have been watching the comments about being able to enable certain options through update releases such as they are doing with the Insiders right now and it crossed my mind Microsoft may be going in this direction. At lease there would not be a two times a year threat of losing your system due to a full build upgrade.

 

[Trouble]

Pretty sure that, that is all 19H2 is or is gonna be
AND
When you look at 20H1 you won't see a remarkable difference
SO
YES.... as soon as they settle on terms and by that I mean actual language definitions.
Does a "Feature Update" represent the need for a build update
Does a "Cumulative Update" or a series of them over time require a build update
AND
At some point you've got to begin to grasp that the underlying base code of the Operating System even something as voluminous as Windows 10's primary code is likely to be is not going to change..... especially since you've already announced that it will be and is the "Last Version of Windows ever", and giving us new color backgrounds and more font choices for Sticky Notes should not jeopardize my system by requiring an "upgrade installation"

 

[Saltgrass]

They are speculating on the Microsoft site Oct. 8th just a CU and not a full build. I suppose one way folks would no longer be able to be a year behind would be to do CUs instead of full builds.

But, CUs don't usually make changes to your current settings, where build upgrades will change quite a few. I have seen some things recently where it seems the CUs are making system changes so maybe this goes along with your comment about defining what a "Feature Update" will actually be.

I suppose a CU will have a more substantial effect on an install then they have in the past, is a possibility. Wow, instead of worrying about backing up a system every 6 months, now we have to worry monthly!!!

 

[Snuffy]

mostly I dl the CUs then add to the current install (online) then add to the most current install.wim (remade iso).
that gives me the latest full iso so either a CLEAN install or a Repair Install when needed. all done by MS Approved script
dism /image:E:\mount /Add-Package:"E:\cab\windows10.0-kb4508451-x64.cab"
DISM.exe /Online /Add-Package /PackagePath:E:\windows10.0-kb4508451-x64.cab
then take the install.wim and compress it to ESD readd to the iso on USB, or you can use the wim. i prefer to compress but many do not.
this gives me currently 18363.388 - iso

 

[Saltgrass]

I wonder what the .10024 update is for..?

The blog post regarding the next release has been updated as of 10/16/2019 and addresses the 18362. and 18363 versions.

Getting the November 2019 Update Ready for Release

UPDATE 10/22: As mentioned in the below blog post, once Windows Insiders are on the final 19H2 build (Build 18363.418) – we will continue to improve the overall experience of 19H2 on customers’ PCs as part of our normal servicing cadence. This means we will continue to iterate and release new...

blogs.windows.com

 

[Trouble]

I believe the key to that information is this quote

This update also includes a fix necessary to move Insiders in the Slow ring to the final 19H2 build

They branched off the Slow ring a while back with that weird numbering so they have to do something to get everyone over to 19H2

 

[Saltgrass]

What I noticed was the following, it tells us what will happen to the public builds. The same download you already have will just change the build number to 18363.. So it would appear I do not yet see the new features. But at least I don't have to worry about going through some build upgrade process.

For an outsider, it gets a little confusing as to where you need to be to move forward. But I suppose your 363.418 build will take you out of the Insider program on that system?

For customers who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the November 2019 Update features. This changes the build number for the OS from Build 18362 to Build 18363.

 

[Snuffy]

363.418 is part of Insider while 362.418 is not Insider. yes rather strange. I have one on 362.418 and as of today (now) there are no updates. and many are having issue with 18362.100024. be ware of this one...

UPDATE 10/16: Today we have released 19H2 Build 18362.10024 to Windows Insiders in the Slow ring. This update includes all of the latest 19H2 features as well as the latest fixes included as part of KB4517389. This update also includes a fix necessary to move Insiders in the Slow ring to the final 19H2 build as noted in the below blog post. Any Insider on Build 18362.100xx should receive this update regardless of your ring settings. If you already moved from the Slow ring to Release Preview ring as recommended below last week – you will still get this update.

Hello Windows Insiders!

We are now getting the Windows 10 November 2019 Update (19H2) ready for release. We believe that Build 18363.418 is the final build and we will continue to improve the overall experience of 19H2 on customers’ PCs as part of our normal servicing cadence. Build 18363.418 includes all of the latest 19H2 features as well as the latest fixes included as part of KB4517389. Windows Insiders in the Release Preview ring already have this build, so no action is needed from them to get this build.

As we have communicated previously, the May 2019 Update (version 1903) and November 2019 Update (version 1909) share the same servicing content. That means they share the same Cumulative Update packages. For customers who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the November 2019 Update features. This changes the build number for the OS from Build 18362 to Build 18363. Because they use the same servicing content, the build revision number (the number that comes after the dot) will always match between May 2019 Update and November 2019 Update. Today, customers on the May 2019 Update have Build 18362.418 but Windows Insiders on the November 2019 Update have Build 18363.418.

 

[Saltgrass]

I wonder if the enablement package will be available to the Public build Seekers prior to the Nov. announcement?

 

[Snuffy]

#EnablementPackage #KB4517245 update comes to only enables Windows 10 1909 features. This package makes the 18362 version 18363. Since the Windows 10 1903 18362.329 all new functions of the Windows 10 1909 are contained in 1903 already.

 

[Saltgrass]

#EnablementPackage #KB4517245 update comes to only enables Windows 10 1909 features. This package makes the 18362 version 18363. Since the Windows 10 1903 18362.329 all new functions of the Windows 10 1909 are contained in 1903 already.

Not sure what your point is, Snuffy. The fact components are already contained does not mean they are enabled until my version number changes, as the referenced Blog post indicates. That will happen with an update on or maybe shortly before (seekers) the official announcement.