Changing to 22h2 from 22h1 in windows 10

Topic

New Reply

1.CyberPower 10 year old gaming computer. I have OS build 19044.2965 (MS said I need 19041.1865 or later so I seem good here. 2.When I look below that at my Experience Pack, it says 1000.19041.1000.0  Is this going to cause a problem? Are these two numbers related in any way and will this need to be updated before I proceed? 3. Is it wise to disable any security apps before making the change? Thanks for any insights.

Windows 10 Home. HP 12GB RAM 256GB SSD 4year old desktop.

Reply | Quote

Replies

Bookman wrote:

2.When I look below that at my Experience Pack, it says 1000.19041.1000.0 Is this going to cause a problem?

For starters, did you mean to type “21H2” instead of “22H1” in the title?

I’m on Windows 10 22H2 (version 19045.2965) and I have the same version number for the Experience Pack, so I doubt it’ll cause any issues.

Since you have the same basic monthly update installed as I do (and many others here as well), all you should really need to do is to allow Windows Update to find and install the Feature Update to 22H2 via the Enablement Package, KB5015684. The download and install should take less than 15 minutes, including the reboot time, unless you have a slow internet connection. Even if you do have a slow internet connection, the Enablement Package that’s downloaded by Windows Update is really small, just a few megs in size, if I recall correctly.

You MUST perform the update before Tuesday the 13th, otherwise you’ll wind up being updated to the June monthly update as well as being updated to 22H2. That’s potentially problematic, since you’ll have an unevaluated monthly update installed which will make you an unpaid tester in the eyes of some folks.

Bookman wrote:

3. Is it wise to disable any security apps before making the change?

If you’re running any third party security apps, Susan has recommended temporarily disabling them in the past during the Feature Update. I’ve been running the default Windows/Microsoft Defender since jumping to Windows 10 and have never had a problem during the monthly updates nor during the Feature Updates. I have never had to disable it during said updates, either. However, YMMV.

1 user thanked author for this post.

Bookman

Reply | Quote

Bob,
I meant to write 22H1 because that’s how it’s been registered in my head but now I realize there may not have been a 22H1 which I think I did know at one time so thanks first for reading carefully. And thanks for clarifying what happens if I miss the June 13 date. I use a paid Avast Security suite and paid Iobit Suite (which seem to play nicely with each other most of the time) and have not had problems with leaving them on for updates previously. Hopefully the older programs I have on this greater than 10 year old machine will still function till the end of Win 10’s lifespan. It was well worth a few hundred dollars more to get a machine that would last this long and perform admirably.

Windows 10 Home. HP 12GB RAM 256GB SSD 4year old desktop.

Reply | Quote

22H1 never existed

Microsoft went straight from 21H2 (November 2021 Update) to 22H2 (2022 Update) and they’re both minor feature updates to Win10. MS announced that change here.

Release cadence and support

We will transition to a new Windows 10 release cadence to align with the Windows 11 cadence, targeting annual feature update releases. We are now renaming the servicing option for releases to the General Availability Channel starting with the November 2021 Update (Note: this replaces the previous “Semi-Annual Channel” term for the servicing option). The next Windows 10 feature update is slated for the second half of 2022. We will continue to support at least one version of Windows 10 through Oct. 14, 2025.

Reply | Quote