How to get the Windows 10 2022 Update version 22H2 Win Update

jamis said:

sgage: My i5 is a 2320 as shown in the my computer specs. It was a W7 machine originally when purchased well prior to W10 being released.

Yes, it is a bit older - second gen. It was released in Q3 2011, and discontinued in Q1 2013. A capable CPU, though. Just type i5 2320 into your favorite search engine and you can find all the details. In any case, I don't think CPU age is being used by MS as a criterion for this update. But who knows how MS thinks! Certainly not me...

I presumed that the Media Creation Tool was already out for W10 v22h2, but when I downloaded it today from MS and ran it, the ISO file it created was for 19041.2006 -- not even close to 19045.2130.

And ... before anyone jumps to the conclusion that I downloaded the WRONG file -- the filename is: MediaCreationTool22H2.exe

So, naturally, I presumed it would create, if not a build 19045 ISO, at least a build 19044 ISO -- certainly NOT a build 19041 ISO.

Mark Phelps said:

I presumed that the Media Creation Tool was already out for W10 v22h2, but when I downloaded it today from MS and ran it, the ISO file it created was for 19041.2006 -- not even close to 19045.2130.

And ... before anyone jumps to the conclusion that I downloaded the WRONG file -- the filename is: MediaCreationTool22H2.exe

So, naturally, I presumed it would create, if not a build 19045 ISO, at least a build 19044 ISO -- certainly NOT a build 19041 ISO.

On the same MS page where you pick MCT, you can also opt to simply download the iso. I did that, and got 22621.

Mark Phelps said:

I presumed that the Media Creation Tool was already out for W10 v22h2, but when I downloaded it today from MS and ran it, the ISO file it created was for 19041.2006 -- not even close to 19045.2130.

And ... before anyone jumps to the conclusion that I downloaded the WRONG file -- the filename is: MediaCreationTool22H2.exe

So, naturally, I presumed it would create, if not a build 19045 ISO, at least a build 19044 ISO -- certainly NOT a build 19041 ISO.

You did something wrong. Using MCT, I downloaded the files, created the ISO and installed 22H2 2130 ten days ago.

Ghot said:

That's for Windows 11.
Mark is looking for 19045.2193



@Mark Phelps

For Mark and anyone else on an older, incompatible computer, you can still install Windows 11 if desired.
I'm assuming that anyone attempting this, has a fresh, full OS image backup.

Let's install Windows 11 on incompatible hardware | Windows 11 Forum




I detest Oprah, but she does make a useful meme.

Yep, I posted the location for Win11. Serves me right for bouncing around between the 10 and 11 forums so much! Thanks for the correction...

Hmm . . Let's see,

The 22h2 enablement package was posted to my listed 2nd system and my ol' gateway dx483 beater the week after this Oct's patch Tuesday. System one's didn't show until after this patch Thursday.
I was going to wait until Nov's patch Tues. but thought maybe I should do them now and avoid the rush.

Being that these were 'enablements' all three machines fared the process well, with an average of 7minutes from the d/l start to the restart an back to the dsktp.

Just an obs | All three act quicker.

Can someone offer a clarification on this? Notice the retirement and end dates:



I take it as 22h2's eol is Oct 14, 2025, but the end date is May 14, 2024.

Does that May date mean that the 14th is the last day 22h2 will be offered, and you will have to find other avenues to update to 22h2?