Windows 11 22H2 (Sun Valley 2) RTM build 22621 general availability after Sept. 5, 2022

Bree · Jun 6, 2022

Mark Phelps said:
for these to be taken as facts, they need the citation from MS to back that up.

You have no further to look than in Regedit, see the key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

For the build of "10.0. 22000.708" shown when you open a command prompt....

10 is the 'Major Version Number', 0 is the 'Minor Version Number', 22000 is the 'Current Build' or 'Current Build Number'....

... and 708 is the UBR.

UBR stands for 'Update Build Revision'.

To specify additional requirements, such as build number and Update Build Revision (UBR)

Deploy Windows update packages in Intune - Microsoft Intune

Learn how to deploy a Windows update package (.msu file) in Intune.

docs.microsoft.com

Drica · Jun 6, 2022

Mark Phelps said:
Your opinion - clearly -- but WHERE is the citation from MS to support your claim?

Posters here spout opinions all the time, but for these to be taken as facts, they need the citation from MS to back that up.

Unlike others, I provided the citation from MS in my post.

Windows 11, version 22H2 certification build

Minimum acceptable build for Windows 11, version 22H2 certification is RTM build(i.e. 22621).

Read....

Folow the links...

As I said is technical stuff.

You can also use on windows 'dism /Get-WimInfo'

That the following information appears:

Drica · Jun 6, 2022

Bree said:
You have no further to look than in Regedit, see the key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

For the build of "10.0. 22000.708" shown when you open a command prompt....
View attachment 30855
10 is the 'Major Version Number', 0 is the 'Minor Version Number', 22000 is the 'Current Build' or 'Current Build Number'....

View attachment 30853

... and 708 is the UBR.

View attachment 30854

UBR stands for 'Update Build Revision'.

Deploy Windows update packages in Intune - Microsoft Intune

Learn how to deploy a Windows update package (.msu file) in Intune.

docs.microsoft.com

Thanks, finally someone understands :wink:

Wynona · Jun 6, 2022

cereberus said:
We really need some action soon - this thread is dying of boredom LOL.

Nah. I think folks will start back with important stuff once they know they won't be interrupted by trivial stuff.

Wynona · Jun 6, 2022

Drica said:
Thanks, finally someone understands

You still don't understand. Build 22000.675 was revised to Build 22000.708. Yes, the last three digits show that the Build was revised, but are still included in the Build number, i.e. Build 22000.675 was revised to Build 22000.708.

Drica · Jun 6, 2022

Wynona said:
You still don't understand. Build 22000.675 was revised to Build 22000.708. Yes, the last three digits show that the Build was revised, but are still included in the Build number, i.e. Build 22000.675 was revised to Build 22000.708.

What has changed?

The revision number because you update the build.

The build number not change because the build has been updated with security updates or non-security updates.

Is the same build with fixes 'Cumulative updates aka CU KB5014034 or something else number or SSU updates'.

It was revised when applying the updates, but is the same build.

So, if is the same build with updates what changes is the revision number.

Bree · Jun 6, 2022

Drica said:
So, if is the same build with updates what changes is the revison number.

That's the build revision number, not just the revision. The whole thing together, 22000.708 is the full number of the build. the 22000 part just identifies it as being the 21H2 that was released last October. The current update is described by Microsoft as the May 24, 2022—KB5014019 (OS Build 22000.708) Preview' in their release history.

Drica · Jun 6, 2022

Bree said:
That's the build revision number, not just the revision. The whole thing together, 22000.708 is the full number of the build. the 22000 part just identifies it as being the 21H2 that was released last October. The current update is described by Microsoft as the May 24, 2022—KB5014019 (OS Build 22000.708) Preview' in their release history.

Yes, the revision number only serves to inform us that build was updated.

If you see revision number 1, meaning that build doesn't have updates is the first build.

But Microsoft can release versions for the public or insiders with updates already made on those builds.

Which may be the case of build 22621 when it is released to the public.

You can see this in some Insiders builds, Beta and Preview builds.

And almost every month Microsoft makes available ISO and ESD files with last build updated for who has an account with these services.

The ISO or ESD May update is the 675 revision.

Bree · Jun 6, 2022

Drica said:
Which may be the case of build 22621 when it is released to the public.

May be the case? No, will certainly be the case, as it was for 22000.

From my post #139.

22000 was released to Insiders on 28 June 2021 as build 22000.51. Those of us who installed it then, whether we were Insiders or not, got a series of nine cumulative updates as Microsoft developed the OS and fixed bugs before the public release of build 22000.194 on October 4th.

Wynona · Jun 6, 2022

Drica said:
What has changed?

The revision number because you update the build.

The build number not change because the build has been updated with security updates or non-security updates.

Is the same build with fixes 'Cumulative updates aka CU KB5014034 or something else number or SSU updates'.

It was revised when applying the updates, but is the same build.

So, if is the same build with updates what changes is the revision number.

Oh, good grief!

Wynona · Jun 6, 2022

I just installed Beta Build 22621.1 on my laptop. Just had to get back to being an insider. :boom:

Gotta populate it with some apps so I can check it out.

Show and Tell to my students on Thursday . . . hope they don't want to jump ahead. If they do, should I discourage them for awhile?

Josey Wales · Jun 6, 2022

Drica said:
Yes, the revision number only serves to inform us that build was updated.

If you see revision number 1, meaning that build doesn't have updates is the first build.

But Microsoft can release versions for the public or insiders with updates already made on those builds.

Which may be the case of build 22621 when it is released to the public.

You can see this in some Insiders builds, Beta and Preview builds.

And almost every month Microsoft makes available ISO and ESD files with last build updated for who has an account with these services.

The ISO or ESD May update is the 675 revision.

You can see that the Build Number changes with every CU. The ISO that I have is 22000.708

Bree · Jun 6, 2022

Wynona said:
. . . hope they don't want to jump ahead. If they do, should I discourage them for awhile?

I would strongly discourage anyone from trying it on their main or only PC. Mine is on a spare machine, so I can afford to wipe/reinstall if it goes badly wrong.

Wynona · Jun 6, 2022

Bree said:
I would strongly discourage anyone from trying it on their main or only PC. Mine is on a spare machine, so I can afford to wipe/reinstall if it goes badly wrong.

Thanks, Bree. That's what I thought too. I put it on this lappy so it doesn't interfere with my regular stuff.

Drica · Jun 6, 2022

Bree said:
May be the case? No, will certainly be the case, as it was for 22000.

From my post #139.

I think the same but I can't say for sure because I am not part of Microsoft :wink:

Drica · Jun 6, 2022

Josey Wales said:
You can see that the Build Number changes with every CU. The ISO that I have is 22000.708

Here we go again :plead:

No, the build number not changes.

Read some previous posts, it's already been explained, I won't repeat myself.

Read my previous posts and previous posts from @moob and @Bree

Dch48 · Jun 6, 2022

Smithee said:
Will this finally give us a right-click context menu that shows all the options without having to click again on "Show more options?" Or at least allow us to customize the first level of the context menu to add critical features like "delete" and "rename"?

I know the context menu can be changed via registry edits and other tricks, but it makes me unreasonably angry that MS cares so little about what users want that they don't let us customize the context menu within the OS itself.

At least make the full context menu use the same font, icons, and spacing as the first-level one. Windows 11 looks so kludged together, there are so many visual inconsistencies.

Delete is there, it's just an icon. Rename is there too as an icon.

Josey Wales · Jun 6, 2022

Drica said:
Here we go again

No, the build number not changes.

Read some previous posts, it's already been explained, I won't repeat myself.

Read my previous posts and previous posts from @moob and @Bree

I did read them, yes it does ! The Build on The ISO that MS Releases will not change but with every release of a CU the release version goes higher.

Bree · Jun 6, 2022

Drica said:
No, the build number not changes.

We are getting a little confused with semantics here, and in their own way everyone is correct. It really depends on exactly what you use the word 'build' for. There are two parts to a build number, before and after the decimal point. The first part only changes with a Feature Update, 22H2 being the next one (likely to be 22621). The second part increases with every Cumulative Update as the build is patched.

The whole thing is the full build number, consisting of a build, a decimal point, and a build revision (eg 22000.708).

Kursem · Jun 6, 2022

lmao at people arguing at build, revision, and such.

this is all Microsoft fault for not releasing new update for 3 weeks at Beta channel guys, I'm telling ya!