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

Bree · May 27, 2022

HRPuffnstuff said:
In the about windows window it shows like a normal release so this is probably the real deal.

That, or very close to it. The desktop watermark and the expiry date in Winver were dropped a couple of builds back.

HRPuffnstuff · May 27, 2022

Well not being one to give up easily I disabled two start up programs and tried installing 22621 on my desktop and this time it went without a hitch.

Mark Phelps · May 27, 2022

NavyLCDR said:
No. But why would you have to exit the insider program on the drive you do a clean install to? You would have to join the inside program on that drive first in order to leave it.

I'm going by what you said in post #97 -- as my interpretation was that I install from the ISO and once up and running, choose to leave the Insider program.

NavyLCDR · May 27, 2022

Mark Phelps said:
I'm going by what you said in post #97 -- as my interpretation was that I install from the ISO and once up and running, choose to leave the Insider program.

Whether or not an install is on the inside program or not is specific to each install of Windows- not to the user nor the computer. In other words you can have 22621 in one partition that is in the inside program, and have a second install of 22621 in a different partition that is not in the insider program. Clean installs, by default, are not in the inside program until the user goes into settings and enrolls that install.

HRPuffnstuff · May 27, 2022

This is what I'm now seeing on my machine since updating to 22621 a few hours ago.

cereberus · May 28, 2022

jimbo45 said:
I think most of us are heartily sick of year 2022 -- to put in the words of "Lizzy II - QEII of GB -- probably the only "Honest politician" left these days " --"Anus Horribilus" -- not sure how long ago she said that but right sentiment.

Lets' s have 23H1 !!!!!! All in favour of that -- start a new year with a new build.

Cheers
jimbo

I think you mean Annus LOL.

jimbo45 · May 28, 2022

cereberus said:
I think you mean Annus LOL.

Hi there
Did Engineering at Uni -- Latin wasn't my thing !!!!!!!

Cheers
jimbo

Bree · Jun 3, 2022

moob said:
I have 22621.1 version installed on another PC and I have not received any update

That's not surprising. There haven't actually been any cumulative updates for 22621 yet. When MS eventually get round to issuing one you will get it, just as all the previous builds got theirs. You don't even need to sign up as an Insider - I'm not.

moob · Jun 3, 2022

Bree said:
That's not surprising. There haven't actually been any cumulative updates for 22621 yet. When MS eventually get round to issuing one you will get it, just as all the previous builds got theirs. You don't even need to sign up as an Insider - I'm not.

View attachment 30680

What you got was anothers build, not updates.

Updates for build 22621 will be released when go public or only in beta channel (maybe).

Updates not change the build number...

like 22000.675, 22000.708...

there are non-security and security updates.

When change the build number, the build is not the same and is not an update.

Is another build.

Bree · Jun 4, 2022

moob said:
When change the build number, the build is not the same and is not an update.

You can clearly see the updates in my screenshot.

22598.1 > 22598.100 > 22598.200

Wynona · Jun 4, 2022

Bree said:
You can clearly see the updates in my screenshot.

22598.1 > 22598.100 > 22598.200

Which is what I've been calling a Build Number change. For me the Build Number includes the update number. Please correct me if I'm wrong . . .

moob · Jun 4, 2022

Wynona said:
Which is what I've been calling a Build Number change. For me the Build Number includes the update number. Please correct me if I'm wrong . . .

Bree said:
You can clearly see the updates in my screenshot.

22598.1 > 22598.100 > 22598.200

this confirms what I said, not change build number 22598.1, 22598.100, 22598.200

In bold is build number.

and the updates are in current channel in this case "Dev channel"

you are confusing upgrades with updates.

in the last years Microsoft only releases two upgrades for year.

In case of windows 11 if release the build 22621 in October, this year in only 1 upgrade.

In case of windows 10 releases 2 build per year, the build 19043 and the build 19044.

When change the build number is an upgrade not an update.

NavyLCDR · Jun 4, 2022

@Bree, @Wynona,

I would give up if I were you. I think we need, at this point, to just agree to disagree with @moob.

moob · Jun 4, 2022

NavyLCDR said:
@Bree, @Wynona,

I would give up if I were you. I think we need, at this point, to just agree to disagree with @moob.

you can get the build number with powershell script

or if you use Visual studio in C# with Environment.OSVersion.Version.Build

and see for yourself :wink:

NavyLCDR · Jun 4, 2022

moob said:
you can get the build number with powershell script

or if you use Visual studio in C# with Environment.OSVersion.Version.Build

and see for yourself

I have build number 22621.1. I am not in an insider program. Is my build number 22621.1 going to get updated by Microsoft before September? Yes it is. That's what this whole argument started out to be. You claimed it would not get updated. I claim that it will. We shall see in the next couple of weeks with patch Tuesday.

moob · Jun 4, 2022

NavyLCDR said:
I have build number 22621.1. I am not in an insider program. Is my build number 22621.1 going to get updated by Microsoft before September? Yes it is. That's what this whole argument started out to be. You claimed it would not get updated. I claim that it will. We shall see in the next couple of weeks with patch Tuesday.

ok, I say this because that's what microsoft has been doing over the years.

there are only updates after the versions "aka builds" become public, the calls "final versions or final builds".

if there are updates in beta or dev builds, the updates it's on specific channels, Dev or Beta.

And it makes sense.

Bree · Jun 4, 2022

moob said:
this confirms what I said, not change build number 22598.1, 22598.100, 22598.200

In bold is build number.

and the updates are in current channel in this case "Dev channel"

you are confusing upgrades with updates.

No, you are confused.

Upgrades are called 'Feature Updates' by Microsoft, and are indicated by a change in the major build number, 22598 in this example. A Feature Update introduces new and/or changed features.

Updates are by means of a Cumulative Update, called a 'Quality Update' by Microsoft. These are security and non-security patches for an existing major build, indicated by increasing the minor build number as in this example from .1 to .100 and again to .200. A Quality Update does not add any major feature changes.

moob · Jun 4, 2022

Bree said:
No, you are confused.

Upgrades are called 'Feature Updates' by Microsoft, and are indicated by a change in the major build number, 22598 in this example. A Feature Update introduces new and/or changed features.

Updates are by means of a Cumulative Update, called a 'Quality Update' by Microsoft. These are security and non-security patches for an existing major build, indicated by increasing the minor build number as in this example from .1 to .100 and again to .200. A Quality Update does not add any major feature changes.

ok, you are write what i said before.

every insider build come with "'Feature Updates", and that's why it changes the build number.

if it's just for fix things, change the ".1 to 100, to .200 and so on"

Bree · Jun 4, 2022

moob said:
there are only updates after the versions "aka builds" become public, the calls "final versions or final builds".

There are many updates for the release candidate build before it becomes public. 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.

The full list of pre-release updates, and what was fixed or added in each, can be found here.

Windows 11 version history - Wikipedia

en.wikipedia.org

In is inevitable that the same process will happen as 22H2 build 22621.1 is got ready for its release date. And anyone who is running 22621.1 now should be confident that they will get all the pre-release cumulative updates.

cereberus · Jun 4, 2022

moob said:
ok, you are write what i said before.

every insider build come with "'Feature Updates", and that's why it changes the build number.

if it's just for fix things, change the ".1 to 100, to .200 and so on"

This convention is (reasonably) ok for release version but for Insider builds, it is not always that clear cut e.g. latest Dev build upgrade was basically nothing but fixes.