Insider KB5016632 Windows 11 Insider Release Preview Build 22621.382 22H2 - Aug. 9

Bree · Aug 10, 2022

LeLibran said:
The 22621.x and 22622.x builds appear to be interchangeable, i.e. I've just completed a test 'repair' installation on a 22622.x VM installation using a 22621.x build of a slightly earlier vintage and the installation offered to keep all user apps and data; and did so without any problems. The system applied all of the latest updates successfully and now reports as 22621.382.

Yes, I have found that works for Windows 10 builds 19041/19042/19043/19044 too.

The reason that it works is that these builds with a number updated by just 1 all share the same base build of system files, 19041 for W10 or 22621 for W11. The update to a build 1 higher is done by a small enablement package. As these are more akin to a CU than a full feature update they don't count as far as upgrade compatibility is concerned.

For an in-place upgrade to be able to keep all installed apps and data it is only the base build of the system files that has to be the same or higher.

BrianInEngland · Aug 10, 2022

LeLibran said:
The 22621.x and 22622.x builds appear to be interchangeable, i.e. I've just completed a test 'repair' installation on a 22622.x VM installation using a 22621.x build of a slightly earlier vintage and the installation offered to keep all user apps and data; and did so without any problems. The system applied all of the latest updates successfully and now reports as 22621.382.

Yes they have exactly the same code base, it's just Beta is ahead on updates/activated features.

SHIELD3 · Aug 10, 2022

It's still offline can't down load it .

Zardoc · Aug 10, 2022

Bree said:
Yes, I have found that works for Windows 10 builds 19041/19042/19043/19044 too.

The reason that it works is that these builds with a number updated by just 1 all share the same base build of system files, 19041 for W10 or 22621 for W11. The update to a build 1 higher is done by a small enablement package. As these are more akin to a CU than a full feature update they don't count as far as upgrade compatibility is concerned.

For an in-place upgrade to be able to keep all installed apps and data it is only the base build of the system files that has to be the same or higher.

Read too fast repeat

SHIELD3 · Aug 10, 2022

Windows 11 Insider Preview 10.0.22622.575 (ni_release) amd64 which vers is this one Beta Or Dev or Release?

BrianInEngland · Aug 11, 2022

SHIELD3 said:
Windows 11 Insider Preview 10.0.22622.575 (ni_release) amd64 which vers is this one Beta Or Dev or Release?

That's Beta

Bree · Aug 11, 2022

Zardoc said:
Read too fast repeat

OK, try this slower explanation:

The reason you are not allowed do an in-place upgrade to a lower build number and keep your installed apps is because each new build introduces new registry settings. An upgrade to the same build or higher is possible, because the new build knows what all the registry settings in the currently installed OS are for. A downgrade to a lower build is not possible because the older build does not understand some of the registry settings used in the newer OS it is trying to upgrade.

Now a feature update by an enablement package does not work the same way. There are no changes to the base build of the system files. What new features there are have been drip-fed into the system over the last few cumulative updates. These are intitally dormant features and the enablement package turns them on. Because this is not a full replacement of the OS with a new one, the system files are basically still the same ones, there will be no windows.old folder created. To indicate that this is not a major feature update MS just increase the build number by 1.

Windows 10 version 2004 build 19041 was the last major feature update for W10. All subsequent feature updates, 19042 up to 19044, were by enablement package. Here's what MS said when 19042 was released.

Windows 10, versions 2004 and 20H2 share a common core operating system with an identical set of system files. Therefore, the new features in Windows 10, version 20H2 are included in the latest monthly quality update for Windows 10, version 2004 (released October 13, 2020), but are in an inactive and dormant state. These new features will remain dormant until they are turned on through the “enablement package,” a small, quick-to-install “master switch” that activates the Windows 10, version 20H2 features.

The enablement package is a great option for installing a scoped feature update like Windows 10, version 20H2 as it enables an update from version 2004 to version 20H2 with a single restart, reducing update downtime. This enables devices to take advantage of new features now. For version 2004 devices that receive updates directly from Windows Update, devices automatically get the enablement package by installing the feature update to Windows 10, version 20H2.

If a device is updating from Windows 10, version 1909 or an earlier version, this feature update enablement package cannot be manually installed. Instead, it is bundled and automatically included with the feature update to Windows 10, version 20H2. Note the installation time is not reduced in this scenario.

KB4562830 Enablement Package Feature Update to Windows 10 version 20H2

Windows 10 version 20H2 build 19042.572 - UPDATED December 8

www.tenforums.com

This method of releasing feature updates means that the base build of the system files does not change, for W10 it remains at 19041, even though 21H2 now reports itself as 19044 in Winver. One unexpected benefit of this new update method is that an in-place repair upgrade of any W10 build from 19041 up to 19044 can still be done with an original 2004 19041 ISO. There are no new system files needed, so after going back to 19041, Windows Update will then just reinstall the enablement package to get it back up to the latest 19044 build.

The same applies to 22621/22622, indicated by the new build number only being 1 higher. The only difference between them is that 22622 has had its dormant features enabled, all the system files are the same. As such, you can do an in-place upgrade on a 22622 machine with the 22621 ISO and keep all your installed apps and files.

BrianInEngland · Aug 11, 2022

Bree said:
OK, try this slower explanation:

The reason you are not allowed do an in-place upgrade to a lower build number and keep your installed apps is because each new build introduces new registry settings. An upgrade to the same build or higher is possible, because the new build knows what all the registry settings in the currently installed OS are for. A downgrade to a lower build is not possible because the older build does not understand some of the registry settings used in the newer OS it is trying to upgrade.

Now a feature update by an enablement package does not work the same way. There are no changes to the base build of the system files. What new features there are have been drip-fed into the system over the last few cumulative updates. These are intitally dormant features and the enablement package turns them on. Because this is not a full replacement of the OS with a new one, the system files are basically still the same ones, there will be no windows.old folder created. To indicate that this is not a major feature update MS just increase the build number by 1.

Windows 10 version 2004 build 19041 was the last major feature update for W10. All subsequent feature updates, 19042 up to 19044, were by enablement package. Here's what MS said when 19042 was released.

KB4562830 Enablement Package Feature Update to Windows 10 version 20H2

Windows 10 version 20H2 build 19042.572 - UPDATED December 8

www.tenforums.com

This method of releasing feature updates means that the base build of the system files does not change, for W10 it remains at 19041, even though 21H2 now reports itself as 19044 in Winver. One unexpected benefit of this new update method is that an in-place repair upgrade of any W10 build from 19041 up to 19044 can still be done with an original 2004 19041 ISO. There are no new system files needed, so after going back to 19041, Windows Update will then just reinstall the enablement package to get it back up to the latest 19044 build.

The same applies to 22621/22622, indicated by the new build number only being 1 higher. The only difference between them is that 22622 has had its dormant features enabled, all the system files are the same. As such, you can do an in-place upgrade on a 22622 machine with the 22621 ISO and keep all your installed apps and files.

Exactly! And working the other way, MS could release an enablement pack for 22621 RP/public release and enable the features that are currently in the Beta builds. Which is what I'm hoping for and mentioned in my other comments on this thread.

Bree · Aug 11, 2022

BrianInEngland said:
Exactly! And working the other way, MS could release an enablement pack for 22621 RP/public release and enable the features that are currently in the Beta builds. Which is what I'm hoping for and mentioned in my other comments on this thread.

Yes, though I suspect that the current 22622 Beta build is just for experimental testing. 22621 will be a full major feature update for the retail 22000 when it gets its public release, as it already has been shown to be for the Insider RP channel 22000 build. Anyone on Beta 22622 who wants to step out of insider builds or switch to the RP channel and wait for the RTM release can do an in-place repair upgrade with the 22621 ISO to step back down by 1.

Some of the 22622 test feature may get added to 22621 before its public release (or dropped if Insiders find fault with them). I suspect the earliest we may see a 22622 build number again could be for 23H2, assuming it will not be another major feature update.

Superfly · Aug 11, 2022

Well... WU is not offering this on my non-Insider, non-compatible - so manual download then... prob. just an Insider exclusion but still...I would have expected WU to shout at me for non-compatible. Be that as it may ...

cereberus · Aug 11, 2022

Bree said:
Yes, though I suspect that the current 22622 Beta build is just for experimental testing. 22621 will be a full major feature update for the retail 22000 when it gets its public release, as it already has been shown to be for the Insider RP channel 22000 build. Anyone on Beta 22622 who wants to step out of insider builds or switch to the RP channel and wait for the RTM release can do an in-place repair upgrade with the 22621 ISO to step back down by 1.

Some of the 22622 test feature may get added to 22621 before its public release (or dropped if Insiders find fault with them). I suspect the earliest we may see a 22622 build number again could be for 23H2, assuming it will not be another major feature update.

Yep - I cannot see a users on 22622 getting updated directly to 22521 via wupdate, but I had forgotten about the repair upgrade trick. Going to check that still works in a vm.

edit: yep still seems to be working - not finished yet though.

edit: fell over at last hurdle and undoing changes!

Zardoc · Aug 11, 2022

Bree said:
OK, try this slower explanation:

The reason you are not allowed do an in-place upgrade to a lower build number and keep your installed apps is because each new build introduces new registry settings. An upgrade to the same build or higher is possible, because the new build knows what all the registry settings in the currently installed OS are for. A downgrade to a lower build is not possible because the older build does not understand some of the registry settings used in the newer OS it is trying to upgrade.

Now a feature update by an enablement package does not work the same way. There are no changes to the base build of the system files. What new features there are have been drip-fed into the system over the last few cumulative updates. These are intitally dormant features and the enablement package turns them on. Because this is not a full replacement of the OS with a new one, the system files are basically still the same ones, there will be no windows.old folder created. To indicate that this is not a major feature update MS just increase the build number by 1.

Windows 10 version 2004 build 19041 was the last major feature update for W10. All subsequent feature updates, 19042 up to 19044, were by enablement package. Here's what MS said when 19042 was released.

KB4562830 Enablement Package Feature Update to Windows 10 version 20H2

Windows 10 version 20H2 build 19042.572 - UPDATED December 8

www.tenforums.com

This method of releasing feature updates means that the base build of the system files does not change, for W10 it remains at 19041, even though 21H2 now reports itself as 19044 in Winver. One unexpected benefit of this new update method is that an in-place repair upgrade of any W10 build from 19041 up to 19044 can still be done with an original 2004 19041 ISO. There are no new system files needed, so after going back to 19041, Windows Update will then just reinstall the enablement package to get it back up to the latest 19044 build.

The same applies to 22621/22622, indicated by the new build number only being 1 higher. The only difference between them is that 22622 has had its dormant features enabled, all the system files are the same. As such, you can do an in-place upgrade on a 22622 machine with the 22621 ISO and keep all your installed apps and files.

@Bree my dear fellow forum friend, This is really were you have to think before posting a reply

. I was referring to myself. I posted literately almost the same thing as what you had mentioned, hence I read too fast the posts and I was repeating your comment.

Sorry for making you detail what I knew but I'm sure it will help those who don't know what enablement packages are. Still, running 2 versions at once plus a preview update, does make it all the more confusing for some.

That's why I stopped beta testing years ago, but still, I do love the challenge of installing betas or previews for the fun of it.

Bree · Aug 12, 2022

Zardoc said:
@Bree my dear fellow forum friend....

Sorry for my confusion. It's so easy to misunderstand conversations in raw text when you don't have the advantage of being able to read the body language that accompanies it......

jimbo45 · Aug 12, 2022

W10 development is essentially at "Freeze" apart from security / emergency fixes. It's likely too that no development will be done for new hardware either.

For W11 I'm in the unenviable position is that the only edition I can get working without problem on the hardware I'm using is the DEV release. The STD and other insider builds just give me the "You'll need another app from the store to ...." etc whenever I try and access Windows security (WD) -- and an OS where I can't even run a virus scan is about as useful as a chocolate teapot.

However unlike a lot I've no issues with the DEV release !!!. Just hope date is extended via update or whatever as it expires in about 4 weeks.

Cheers
jimbo

SHIELD3 · Aug 12, 2022

Windows 11 build 25179: No New Features, Tabs Now Rolling Out AND MORE!

Aug 11, 2022 Microsoft has released a new Windows 11 Insider build 25179 to the Dev Channel. This is still version 22H2, since the Sun Valley 3 development, which was known as Windows 11 23H2, has been canceled in favor of releasing a major new Windows version every three years, so for now, the Dev channel is sticking with version 22H2, which will eventually release sometime in 2023, and most likely under ` Windows 11 23H2 version naming. For this release, Microsoft has not announced new features, instead saying it is a set of changes and improvements as well as fixes. Microsoft also released ISO images for this build. Announcing Windows 11 Insider Preview Build 25179

Zardoc · Aug 12, 2022

jimbo45 said:
W10 development is essentially at "Freeze" apart from security / emergency fixes. It's likely too that no development will be done for new hardware either.

For W11 I'm in the unenviable position is that the only edition I can get working without problem on the hardware I'm using is the DEV release. The STD and other insider builds just give me the "You'll need another app from the store to ...." etc whenever I try and access Windows security (WD) -- and an OS where I can't even run a virus scan is about as useful as a chocolate teapot.

However unlike a lot I've no issues with the DEV release !!!. Just hope date is extended via update or whatever as it expires in about 4 weeks.

Cheers
jimbo

@Jimbo, I read about your issue, really weird. I have one of my own also but on all releases. If I restore to previous version like let's say the actual stable build with Macrium, all my OneDrive files are then inaccessible. I have to logout of OneDrive, delete folder, login and download a full 357 GB of files. I seem to be (just like you) in my own little trouble spot.

SHIELD3 · Aug 12, 2022

Guys I don't use Dev Or the beta/

IanMosley · Aug 13, 2022

Brink said:
Release notes will be posted when made available by Microsoft

Shawn,

At the present, MS have apparently given up on posting release notes for 22H2 RP releases - see here.

Also, there is a tendency for OPs to 'go off thread' by discussing features that are not available - in this case - this RP post.

SHIELD3 · Aug 13, 2022

July 12th, 2022 - KB5015818 - Windows 11 22H2 (Build 22621.232) available for non-Insiders

Update
New Cumulative Update KB5015818 is available for all users of 22H2. this is why It's not working for some ...and the aug 9 the same build. Yeah MS you could just told every one .,,

SHIELD3 · Aug 15, 2022

Issues · uup-dump/website

Core code of the UUP dump website. Contribute to uup-dump/website development by creating an account on GitHub.

github.com

is:issue is

pen latest version is 22621.382
anyone think Posting or asking I see noone asked the creator ..

Insider KB5016632 Windows 11 Insider Release Preview Build 22621.382 22H2 - Aug. 9

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computers My Computers

At a glance

At a glance

Dazed & Confused

My Computer My Computer

At a glance

Member

Windows 11 Insider Preview 10.0.22622.575 (ni_release) amd64 which vers is this one Beta Or Dev or Release?​

My Computers My Computers

At a glance

At a glance

Well-known member

Windows 11 Insider Preview 10.0.22622.575 (ni_release) amd64 which vers is this one Beta Or Dev or Release?​

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Dazed & Confused

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Member

Windows 11 build 25179: No New Features, Tabs Now Rolling Out AND MORE!​

My Computers My Computers

At a glance

At a glance

Dazed & Confused

My Computer My Computer

At a glance

Member

My Computers My Computers

At a glance

At a glance

Windows Insider

My Computer My Computer

At a glance

Member

July 12th, 2022 - KB5015818 - Windows 11 22H2 (Build 22621.232) available for non-Insiders​

My Computers My Computers

At a glance

At a glance

Member

My Computers My Computers

At a glance

At a glance

Similar threads

My Computers

My Computer

My Computers

My Computer

Windows 11 Insider Preview 10.0.22622.575 (ni_release) amd64 which vers is this one Beta Or Dev or Release?

My Computers

Windows 11 Insider Preview 10.0.22622.575 (ni_release) amd64 which vers is this one Beta Or Dev or Release?

My Computer

My Computers

My Computer

My Computers

My Computer

My Computer

My Computer

My Computers

My Computer

Windows 11 build 25179: No New Features, Tabs Now Rolling Out AND MORE!

My Computers

My Computer

My Computers

My Computer

July 12th, 2022 - KB5015818 - Windows 11 22H2 (Build 22621.232) available for non-Insiders

My Computers

My Computers