Is OS build 22621.1 of Windows 11 stable?

Wynona · Jun 4, 2022

moob said:
Yes i know but not for now.

And that's what i've been saying

Updates not change build number...

like 22000.675, 22000.708, 19044.1738, 19044.1741...

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.

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

Aha! I've been reading your statements wrongly. You are correct, Build 22000 did not and will not change; only the "extension" will change.

In my defense, when 22000.675 changed to 22000.708, that is a change in Build Number to me. Which is what I was trying to get over to you.

So, it follows that when Build 22621.1 has an extension change, such as 22621.xxx, to me that's a Build Number change. It's how I keep things straight in my mind. And it's how I know there's been a change in the Build I'm working on.

cereberus · Jun 4, 2022

Bree said:
So you want to see an Insider build that gets a new minor build number to prove that it really IS getting a quality update, not just a new build though a feature update? All recent builds so far have all got them, here are some examples.

Build 22581.1 got two quality updates (aka Cumulative updates) first to 22581.100 then 22581,200. Then it got a feature update to a new build, 22598.1 - that in turn got two: 22598.100 and 22598.200. Microsoft have not yet issued any cumulative updates for build 22621.1, when they do we will get then straight away, just as all previous builds have got theirs.

Yeah - it is important to understand difference between feature updates and quality updates.

Supposedly feature updates are optional, whereas quality updates are mandatory.

However, of course as usual, it is not always as clear cut as the definitions imply. MS is not entirely consistent with its management of "quality" updates and "feature" updates i.e. minor new features do appear sometimes in cumulative updates, and equally security updates sometimes appear in build upgrades.

I prefer to think of "feature" updates as meaning "major feature" updates. Having said that we have had build upgrades that barely qualify (in my opinion) as feature updates - look at most recent upgrade to 25131 which was just fixes really improving quality but not adding any new features (unless one classifies less bug as a feature LOL).

It is not obvious to me why we sometimes have bug fix only upgrades - I can only surmise that some fixes require a more significant upgrade to OS?

moob · Jun 4, 2022

Wynona said:
Aha! I've been reading your statements wrongly. You are correct, Build 22000 did not and will not change; only the "extension" will change.

In my defense, when 22000.675 changed to 22000.708, that is a change in Build Number to me. Which is what I was trying to get over to you.

So, it follows that when Build 22621.1 has an extension change, such as 22621.xxx, to me that's a Build Number change. It's how I keep things straight in my mind. And it's how I know there's been a change in the Build I'm working on.

the build number is 22000.

you can get the build number with powershell script

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

cereberus · Jun 4, 2022

Wynona said:
Aha! I've been reading your statements wrongly. You are correct, Build 22000 did not and will not change; only the "extension" will change.

In my defense, when 22000.675 changed to 22000.708, that is a change in Build Number to me. Which is what I was trying to get over to you.

So, it follows that when Build 22621.1 has an extension change, such as 22621.xxx, to me that's a Build Number change. It's how I keep things straight in my mind. And it's how I know there's been a change in the Build I'm working on.

It is easier really to think of the build number convention as "Major.Minor". For the release versions, there is only one Major number per version (21H1, 22H2 etc) but there can be several Minor numbers per Major build.

The distinction is somewhat blurred for Dev versions as we get full Major build upgrades quite frequently, and sometimes no Minor (cumulative updates) between Major build upgrades.

Life would be easier if MS was consistent in its terminology i.e. Upgrades are Major, updates are Minor - unfortunately - they tend to use term update when term upgrade is more appropriate.

Wynona · Jun 4, 2022

cereberus said:
It is easier really to think of the build number convention as "Major.Minor". For the release versions, there is only one Major number per version (21H1, 22H2 etc) but there can be several Minor numbers per Major build.

That's how I think of Builds, @cereberus. Not literally "Major.Minor" but as 22000.708 (same difference).

I was an Insider on DEV, but had to back off that, since my students elected to all update to Windows 11. And yeppers, it was a tad bit confusing to say the least. Especially when I dropped back to the general release version.

I think Microsoft will soon have to change the way version numbers are given, since we've pretty much gone from two releases per year to only one. I'm on Version 21H2 (2nd half of 2021) when 22H1 (1st half of 2022) is almost all gone.

BTW:

cereberus · Jun 4, 2022

Wynona said:
That's how I think of Builds, @cereberus. Not literally "Major.Minor" but as 22000.708 (same difference).

I was an Insider on DEV, but had to back off that, since my students elected to all update to Windows 11. And yeppers, it was a tad bit confusing to say the least. Especially when I dropped back to the general release version.

I think Microsoft will soon have to change the way version numbers are given, since we've pretty much gone from two releases per year to only one. I'm on Version 21H2 (2nd half of 2021) when 22H1 (1st half of 2022) is almost all gone.

BTW:

Yep - 20H1 etc no longer makes sense but it is possible more than one could be released in a year e.g. if there was a major bug that necessitated a new build to be issued.

I would simply use YY.N

YY is obviously year, and N would just be 1,2,3 etc on sequence. N would normally be 1 unless an interim build had to be issued.

Wynona · Jun 5, 2022

cereberus said:
Yep - 20H1 etc no longer makes sense but it is possible more than one could be released in a year e.g. if there was a major bug that necessitated a new build to be issued.

I would simply use YY.N

YY is obviously year, and N would just be 1,2,3 etc on sequence. N would normally be 1 unless an interim build had to be issued.

Makes too much sense!

cereberus · Jun 5, 2022

Wynona said:
Makes too much sense!

Yeah - sack that person whoever implements it as not in line with official obfuscation policy LOL.

Is OS build 22621.1 of Windows 11 stable?

Wynona

Well-known member

My Computers

System One System Two

cereberus

Well-known member

My Computer

System One

moob

Guest

My Computer

System One

cereberus

Well-known member

My Computer

System One

Wynona

Well-known member

Attachments

My Computers

System One System Two

cereberus

Well-known member

My Computer

System One

Wynona

Well-known member

My Computers

System One System Two

cereberus

Well-known member

My Computer

System One

Similar threads

Latest Support Threads

Latest Tutorials