for nonexpert, "not cleaned-up" sounds like some hasty work and not final. Would that be any issue in using this ISO? I mean are these esd final for this build of 20h2 or likely to be changed after an official release (new esd having seemingly right size)?
Every time they fix a significant setup phase bug that could compromise client data, or prevent installation on certain hardware, or to bring speed improvements to the setup phase. These happen quite rarely. All other stuff can be addressed via cumulative updates.
Guys, can you please share a link for 19041.1 ES-MX in esd, lost my iso with a hd crash last week, cant find it anymore, and the uupdump for that version downloads nothing
There is no 19041.1 ESD file, go to uup dump and select any of the latest cumulative update 19041.xxx builds and set addupdates =0 in the convertconfig.ini file, you will end up with a 19041.1 ISO.
btw, can u tell me how to create a ISO to boot from a pen drive without selection of OS architecture? Like i want a ISO with both architectures and when i'm selecting what windows i want i can decide if i go for x86 or x64... because i only know how to do it but i need to choose x86 or x64 before booting from my pen drive, and i would like to select that when i'm on the menu with all windows editions x86 and x64
You could export all x64 indexes to a x86 install.wim but that won't ever be able to boot uefi systems. I have asked @abbodi1406 these questions in the past too. How it now works is the best way to have both, x86 and x64, functionality intact.
@goncalo16 but in uefi world, you cannot boot x64 installer if cpu is x86 only (some cheap tablet or netbook for example ) more over, x64 installer cannot install x86 images. only in legacy bios world, 32 bits installer can install both x86 or x64 images...