Is OS build 22621.1 of Windows 11 stable?


Wynona

Well-known member
Power User
VIP
Local time
3:37 PM
Posts
1,648
Location
Arkansas
OS
Windows 11 20000.613
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.
 

My Computers

System One System Two

  • OS
    Windows 11 20000.613
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    ntel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    100 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer

cereberus

Well-known member
Pro User
VIP
Local time
9:37 PM
Posts
2,532
OS
Windows 10 Pro + others in VHDs
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.


1654303093941-png.30680
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?
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
M

moob

Guest
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
 

My Computer

cereberus

Well-known member
Pro User
VIP
Local time
9:37 PM
Posts
2,532
OS
Windows 10 Pro + others in VHDs
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.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0

Wynona

Well-known member
Power User
VIP
Local time
3:37 PM
Posts
1,648
Location
Arkansas
OS
Windows 11 20000.613
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:
 

Attachments

  • 2022-06-04_22h01_06.png
    2022-06-04_22h01_06.png
    11.2 KB · Views: 1

My Computers

System One System Two

  • OS
    Windows 11 20000.613
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    ntel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    100 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer

cereberus

Well-known member
Pro User
VIP
Local time
9:37 PM
Posts
2,532
OS
Windows 10 Pro + others in VHDs
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.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0

Wynona

Well-known member
Power User
VIP
Local time
3:37 PM
Posts
1,648
Location
Arkansas
OS
Windows 11 20000.613
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! :-)
 

My Computers

System One System Two

  • OS
    Windows 11 20000.613
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    ntel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    100 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer

cereberus

Well-known member
Pro User
VIP
Local time
9:37 PM
Posts
2,532
OS
Windows 10 Pro + others in VHDs
Makes too much sense! :-)
Yeah - sack that person whoever implements it as not in line with official obfuscation policy LOL.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
Top Bottom