Updated differences in installed Dev .100 .120 Build versions?

Buschik · May 5, 2024

Differences in build numbers, re: the .100 .120 Updates? I don't remember if the text said .100 but its actually .120 . hence the screenshot.. this is normal, right?

Paula

OAT · May 5, 2024

Buschik said:
Differences in build numbers, re: the .100 .120 Updates? I don't remember if the text said .100 but its actually .120 . hence the screenshot.. this is normal, right?

Paula

Announcing Windows 11 Insider Preview Build 26120.461 (Dev Channel)

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 26120.461 (KB5037009) to the Dev Channel. Windows Insiders in the Dev Channel will now receive updates based on Windows 11, version 24H2 via

blogs.windows.com

Buschik · May 6, 2024

Ok, thanks, but the announcement does not say "you are getting .120 but will only say .100" which is what I am asking abt ..

OAT · May 6, 2024

Buschik said:
Ok, thanks, but the announcement does not say "you are getting .120 but will only say .100" which is what I am asking abt ..

Sorry where do you see that please?
As far as it is normal, whatever that means, yes it is.

Buschik · May 6, 2024

Where do I see what?

Look at the screenshot:

Updated to .120
Winver says .100

The announcement does not say, "you'll see .100 but it's really .120"

OAT · May 6, 2024

The watermark you mean?
Couldn't tell you, I remove those.
Your winver is correct and you are on the latest Dev.
The build API & build registry values are different if that's what you mean.

Buschik · May 6, 2024

Yes, difference btwn watermark(registry) and winver(api) .100/.120 I did not see if/where it said they could/would be different that's all.

Bree · May 6, 2024

Buschik said:
Yes, difference btwn watermark(registry) and winver(api) .100/.120 I did not see if/where it said they could/would be different that's all.

The feature update to 26120.461 was by means of an enablement package. From the link OAT gave you earlier....

Microsoft said:
Windows Insiders in the Dev Channel will now receive updates based on Windows 11, version 24H2 via an enablement package (Build 26120.xxxx).

That means that build 26100.xxxx and 26120.xxxx share a common set of system files, the enablement package just turns on dormant features that are already in the 26100.xxxx system files. So yes, Winver now says 26120, but the watermark will show the base build which is still 26100.

The same thing happened for the RTM Win11 22H2 update to 23H2. This was by enablement package too, and raised the build shown in Winver from 22621 to 22631.

KB5027397 Enablement Package for Windows 11 version 23H2 Feature Update

Microsoft Support: Summary Windows 11, versions 22H2 and 23H2 share a common core operating system with an identical set of system files. Therefore, the new features in Windows 11, version 23H2 are included in the latest monthly quality update for Windows 11, version 22H2 but are in an inactive...

www.elevenforum.com