1909 in the offing?

goopy said:

Greetings Bree.
Are you suggesting that installation using the UUPDUP 18363.418 ISO is not a 1909 build?

No. I'm suggesting that to install 1909 first Setup installs 1903 (18362) then it switch on the 1909 (18363) features with the Enablement Package.

1909 is not a full Feature Update in the normal sense, this is the first Feature Update to be performed via a form of cumulative update. See my post #115

Bree said:

No. I'm suggesting that to install 1909 first Setup installs 1903 (18362) then it switch on the 1909 (18363) features with the Enablement Package.
1909 is not a full Feature Update in the normal sense, this is the first Feature Update to be performed via a form of cumulative update. See my post #115

Thanks for the kind reply , Bree.
1. So a new install using the latest UUPDump ISO will indeed be 1909 and have all new features turned on?
2. Would you also be kind enough to explain why a 1903 service stack update is still being offered? (see my earlier post.)
Many thanks and best regards,

goopy said:

Would you also be kind enough to explain why a 1903 service stack update is still being offered? (see my earlier post.)

Your earlier post shows you are using Dism++.

Microsoft have said that "19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package". So it's exactly the same update whether it's used on 1903 and 1909.

The update servers should have two titles for the one package, when Windows Update finds a package that is available it would be offered the title appropriate to your version, 1909 or 1903. My guess is that either Dism++ had picked up the wrong title for this one, or Microsoft have forgotten to give this service stack a 1909 title.

It would be interesting to see how it is described in Windows Update.

Bree said:

Your earlier post shows you are using Dism++.

Microsoft have said that "19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package". So it's exactly the same update whether it's used on 1903 and 1909.

The update servers should have two titles for the one package, when Windows Update finds a package that is available it would be offered the title appropriate to your version, 1909 or 1903. My guess is that either Dism++ had picked up the wrong title for this one, or Microsoft have forgotten to give this service stack a 1909 title.

It would be interesting to see how it is described in Windows Update.

Thanks for the kind reply, Bree.

1. Your linked post seems to be saying if one's setup is 1903.18362.418, it already has all the 1909 features in place but not turned on. The new features will be activated, and the build # bumped up to 1909.18363.418 by installing the 21kb enablement package KB4517245 linked below. Is this correct?

Error - UUP dump

2. WU did not pick up the 1903 service stack update.

Many thanks and best regards,

goopy said:

1. Your linked post seems to be saying if one's setup is 1903.18362.418, it already has all the 1909 features in place but not turned on. The new features will be activated, and the build # bumped up to 1909.18363.418 by installing the 21kb enablement package KB4517245 linked below. Is this correct?

That is my understanding, and how I understand it is intended to work once 1909 is released for general availability. Which may not be long now, November 12th is said to be the target date.

Bree said:

That is my understanding, and how I understand it is intended to work once 1909 is released for general availability. Which may not be long now, November 12th is said to be the target date.

Thanks for the kind reply, Bree.
Installed the enablement package KB4517245 on a 1903 build, and winver is now showing 1909.18363.418.
However, 18362 still pops up in a couple of places. Is there a way to test if this is now indeed a 1909 build? New features?
Many thanks and best regards,