Windows 11 Direct ISO

Keith Weisshar · May 22, 2023

Why doesn't the direct Windows 11 ISO option include the May 9th update? It only has build 22621.525 instead of 22621.1702.

cereberus · May 22, 2023

Keith Weisshar said:
Why doesn't the direct Windows 11 ISO option include the May 9th update? It only has build 22621.525 instead of 22621.1702.

Not a direct excuse but the Windows 11 iso has 11 SKUs, but the iso created by MCT only has 7 SKUs.

Perhaps the 4 more advanced SKUs have yet to be updated?

Or it could just be typical MS inconsistency - who knows?

I have created my own iso from the mct, converting the .esd files to .wim.

Bit pointless really, as all will be out of date following next update - I did it because I could LOL.

hsehestedt · May 22, 2023

If you know someone with a Visual Studio subscription that includes the OS downloads, they have build 1702 posted there.

glasskuter · May 22, 2023

Selecting iso option using media creation tool gets you 1702

garlin · May 22, 2023

W11's MediaCreationTool has been refreshed to download 22621.1702.

hsehestedt · May 22, 2023

garlin said:
W11's MediaCreationTool has been refreshed to download 22621.1702.

Not for me (in the United States). Let's just clarify:

Bree · May 22, 2023

hsehestedt said:
Not for me (in the United States). Let's just clarify....

Yes, I see exactly the same in the UK, the MCT makes 1702, the directly downloaded ISO is still 525.

glasskuter · May 22, 2023

@hsehestedt May I ask why so many people object to having install. esd rather than install.wim. I understand the file size difference and the fat32 limitation, and I understand some people customize .wim, But for the normal user, what actual difference does it make?

hsehestedt · May 22, 2023

glasskuter said:
@hsehestedt May I ask why so many people object to having install. esd rather than install.wim. I understand the file size difference and the fat32 limitation, and I understand some people customize .wim, But for the normal user, what actual difference does it make?

At least for me, the issue is exactly what you mentioned: the need for customizing the WIM. That's pretty much my thing. I've built an entire program around customizing Windows images.

For the average user, I can't imagine that it would make any difference at all. In fact, an ESD file might even for many, especially if the ESD is under 4GB in size and the WIM is larger than 4GB. In that event, they wouldn't have to worry about FAT32 4GB file size limitations when making bootable media.

cereberus · May 22, 2023

hsehestedt said:
At least for me, the issue is exactly what you mentioned: the need for customizing the WIM. That's pretty much my thing. I've built an entire program around customizing Windows images.

For the average user, I can't imagine that it would make any difference at all. In fact, an ESD file might even for many, especially if the ESD is under 4GB in size and the WIM is larger than 4GB. In that event, they wouldn't have to worry about FAT32 4GB file size limitations when making bootable media.

I fully agree.

The primary reason I prefer install.wim is so that I can inject key drivers needed reducing all the faffing around with disk management.

As you say, for most users, it makes no difference. Having said that, there is a whole world to explore with dism.

I unashamedly admit my skills at using dism and install.wim all come from the great tutorials of @Kari (the guru's guru) and a lot of trial and error.

I still have a lot to learn though - the more I learn, the more I realise I have yet to learn LOL

hsehestedt · May 22, 2023

cereberus said:
I fully agree.

The primary reason I prefer install.wim is so that I can inject key drivers needed reducing all the faffing around with disk management.

As you say, for most users, it makes no difference. Having said that, there is a whole world to explore with dism.

I unashamedly admit my skills at using dism and install.wim all come from the great tutorials of @Kari (the guru's guru) and a lot of trial and error.

I still have a lot to learn though - the more I learn, the more I realise I have yet to learn LOL

LOL. It was exactly the same for me. I came upon a few of Kari's tutorials and there was no going back. It all led up to a point where I put everything into practice by writing what is now 16,000+ lines of code to automate the handling of Windows images. A lot of that is simply running all the needed DISM commands.

Kari was always very patient with me, even through all my seemingly never-ending questions.

Like you, I too continue to learn

Scott · May 22, 2023

The ISO from UUPdump.net comes with a install.wim file.

glasskuter · May 22, 2023

Thanks to both of you. If I ever have to clean install for myself, about the only extra thing I do is install IRST in pre-boot for both my own machines. I know I could insert them into the .wim file but happily there's never a need to clean install from an iso any more. I use one install media USB for any computer I need to use it on. Again, it's rare I ever have to use it. Now, restoring my PC from an image is a different matter. I've had to do that several times when I played around in areas I had no business being so IRST was inserted into my Macrium recovery media as a CYA.
@cereberus I know only one dism command, restorehealth. After that, color me a dumbass. What little I know about the command line, writing scripts, regfiles, etc is embarrassing. If I can't copy and paste it, I'm lost. Or better yet, download one our man Brink has already written.

Bree · May 22, 2023

glasskuter said:
May I ask why so many people object to having install. esd rather than install.wim. I understand the file size difference and the fat32 limitation, and I understand some people customize .wim, But for the normal user, what actual difference does it make?

In addition to being able to customise the .wim there is another difference that may be important to some. To keep the .esd below 4GB some editions are left out for the .esd. Only the .wim contains the Windows 11 Pro for Workstations and Pro Education editions.

fierycloud · May 23, 2023

https://go.microsoft.com/fwlink?linkid=2156292

hsehestedt · May 23, 2023

The ISO image download option has been updated. It is now 1702.

BrianInEngland · May 23, 2023

hsehestedt said:
The ISO image download option has been updated. It is now 1702.

Can confirm, UK International ISO is 22621.1702

hsehestedt · May 23, 2023

The Moment 3 update will be available tomorrow (announced by Microsoft at Build 2023 today). I guess we will need to get those new ISO images now

erpster4 · Jun 9, 2023

Keith Weisshar said:
Why doesn't the direct Windows 11 ISO option include the May 9th update? It only has build 22621.525 instead of 22621.1702.

the updated Win11 22h2 (aka. "V2") ISO downloads with 22621.1702 downloads were provided on Tuesday, May 23, after 10am pacific local time; one full day after your post
you simply needed to wait another day for MS to release them

ex. Win11 22h2 may 2023 ISO en-us with build 22621.1702 > Win11_22H2_English_x64v2.iso
Win11 22h2 sep 2022 ISO en-us with build 22621.525 > Win11_22H2_English_x64v1.iso