They do, really, just tested a win 7 ultimate and put in my aio 10586 iso and it upgraded (with install.esd).
The keys are good only for th2--they changed that from th1--I imagine you know. Assume you didn't know about the genuine ticket.xml trick. Are you saying that the MCT downloads will support UEFI booting with a DVD? Rufus does the trick for a USB but I don't have a UEFI machine to try it with a DVD. Again, can't imagine a machine so modern that it has UEFI and not being capable of booting off a USB. By the way I loved the images--maybe you should experiment. Just 'restore' onto the hard drive (5-10 minutes) and you're practically done, even though things seemed to take forever anyway (you know!). No sitting and waiting for this and that with a straight install and then having to make all the tweaks and add-ons. That batch file you talked of sounds like a good move for that.
Problem solved! It was as simple as downloading the x86/x64 ISO, converting both ESD to WIM, merge them in a new file with new distinct names (because during upgrade there is no "Architecture" column and both x86/x64 have the same name), convert the new WIM to ESD, place it in both x86/x64 folders and create the new ISO. Nice and neat, no patching required! Now I'm going to add Home N and Pro N, probably won't make much difference in the final ISO size EDIT: lol lite8 had the same idea, only noticed after editing my 1st post! Well I included all steps and all free tools required, just repeat the steps and you'll have a DVD5 version of the downloaded ISO, with space to spare.
Honestly, I don't get it. Sounds like you just merged the wims, shrunk them back to .esds, and replaced the originals. How did that save any space and what advantage over the original download did it give you? The original download, although larger than you wanted, will upgrade any Home or Pro (x86 or x64) and will clean install either version, whether 32- or 64-bit. Can you give a little more detail about this? Update: I tried it from your guide. First, the last line in instruction 5--is that supposed to literally be typed as it is? It did and it seemed to delete something. Second, the last line in instruction no. 6 said the file wasn't there. There's still an install.wim on the root of the d:\win10_aio directory. I tried creating the .iso with and without that file there. Both ways it comes out about the right size but then when I open it in UltraISO or PowerISO it goes back to about 7GB (where it said it would be 'before optimization') when it was being created. So, I'm not sure where to go from here. Thanks for help! Second Update: It did burn onto a DVD5. Is it just fooling the UltraISO and PowerISO because the .esd is "shared" as addobi1406 mentioned? What's with the install.wim in the root directory--is that what should have been deleted in instruction no. 6?
ISO format (like many other) have an optimizing feature which allow to include matched files (in different locations) only once wim format also have this feature, therefore merging windows images (indexes) into one wim file will reduce its size then, instead of having 2 different install.esd, you will have only 1 matched install.esd shared in both x64\sources and x86\sources thus the iso size reduced
Thanks! I'm doing it now--seems to be working. I think it will be a little larger because it's en-US instead of pt-PT but should still meet the 4.37 size we're aiming for.
If I'm not mistaken, cdimage versions 2.52 and below don't support -udfver102. EDIT: Link to cdimage topic fixed in 1st post. Working link is in last post of the topic.
1st post updated with tutorial that covers a Windows 10 AIO (Home/Pro x86/x64, 4 versions) and a Windows 10 AIO with N editions (Home/HomeN/Pro/ProN x86/x64, 8 versions). If including N editions, final ISO is only about 40MB bigger I don't know if adding Enterprise or other editions will (probably) make it go above 4.37GB, but since I only need the Home/Pro x86/x64 I'll leave as it is, this ISO now replaces my previous 2 untouched ISOs in the flash drive and is also burned to DVD5 just in case USB boot is an issue. Feel free to try other combinations and post your results.
Most of cdimage/oscdimg versions will output ISOs with the same size. As long as it accepts all parameters it doesn't matter which version is used. I used v2.53 because it's the same one M$ used to create the MSDN untouched ISOs of Windows 10 build 1511.
@johnye_pt: Worked out great! What can I say--you're a genius! I added a couple of questions to my post #49. Any insight into that? Thanks again!
I thought I'd try burning the .iso onto a USB stick using Rufus and while every ISO program (UltraISO, PowerISO, ImgBurn) says it will take up approximately 4.1GB on a DVD on Rufus it did not use the "sharing" mechanism Abbodi1406 talked of and took up the whole 7GB originally used by the .iso before taking advantage of the "embedding, sparseness or optimization" when it was created. Also, as I mentioned before, when you open it for example in UltraISO or PowerISO it also shows it as a 7GB file even though it will go on to fit it and burn it as a 4.1. Can anyone explain this? Does this mean that the space saved works only with DVDs and, if so, does anyone have any idea of the difference in technologies? Also, if it's extracted to a folder on the hard drive, again, while the .iso itself also shows its size as about 4GB, once so extracted its also shows as 7GB. Thanks in advance.
If the flash drive uses NTFS, try deleting one of the install.esd and then creating a hard link using mklink in the command line. If it uses FAT32, you're out of luck. UltraISO and PowerISO recognize the optimization feature and know that although the ISO contains 7GB of data, it will fit on 4GB because 2 files of 3GB each occupy the same 3GB on the ISO. If you extract the ISO, both 3GB install.esd files are extracted to separate folders as they originally were.
Just a quick update. Got hold of all SVF of Windows 10 in my language, converted them to ISO so I could extract and combine all install.wim, these are the results: Windows 10 v10586 AIO pt-PT (18in1): - Windows 10 x86 Education WIM, 2.17GB - Windows 10 x86 Education N WIM, 2.07GB - Windows 10 x86 Enterprise WIM, 2.17GB - Windows 10 x86 Enterprise N WIM, 2.07GB - Windows 10 x86 Home Single Language WIM, 2.24GB - Windows 10 x86 Multiple Editions Home+Pro WIM, 2.28GB - Windows 10 x86 Multiple Editions Home+Pro N WIM, 2.11GB - Windows 10 x64 Education WIM, 3.01GB - Windows 10 x64 Education N WIM, 2.85GB - Windows 10 x64 Enterprise WIM, 3.01GB - Windows 10 x64 Enterprise N WIM, 2.85GB - Windows 10 x64 Home Single Language WIM, 3.06GB - Windows 10 x64 Multiple Editions Home+Pro WIM, 3.12GB - Windows 10 x64 Multiple Editions Home+Pro N WIM, 2.91GB - WIM total: 36GB (38.659.635.783 bytes) - combined install.wim: 4.65GB (4.997.387.953 bytes) - combined install.esd: 3.07GB (3.304.607.266 bytes) - Final ISO: 3.89GB (4.185.221.120 bytes) Windows 10 v10240 AIO pt-PT (22in1): - Windows 10 x86 Education WIM, 3.10 GB - Windows 10 x86 Education N WIM, 2.95 GB - Windows 10 x86 Enterprise WIM, 3.10 GB - Windows 10 x86 Enterprise N WIM, 2.96 GB - Windows 10 x86 Enterprise LTSB WIM, 2.87 GB - Windows 10 x86 Enterprise LTSB N WIM, 2.75 GB - Windows 10 x86 Home Single Language WIM, 3.15 GB - Windows 10 x86 Multiple Editions Home+Pro WIM, 3.22 GB - Windows 10 x86 Multiple Editions Home+Pro N WIM, 3.02 GB - Windows 10 x64 Education WIM, 3.10 GB - Windows 10 x64 Education N WIM, 2.95 GB - Windows 10 x64 Enterprise LTSB WIM, 2.87 GB - Windows 10 x64 Enterprise LTSB N WIM, 2.75 GB - Windows 10 x64 Home Single Language WIM, 3.15 GB - Windows 10 x64 Multiple Editions Home+Pro WIM, 3.22 GB - Windows 10 x64 Multiple Editions Home+Pro N WIM, 3.02 GB - WIM total: 46.8 GB (50.307.389.305 bytes) - combined install.wim: 4.95 GB (5.317.167.153 bytes) - combined install.esd: 3.23 GB (3.470.960.270 bytes) - Final ISO: 4.05 GB (4.351.574.016 bytes) I think I can make a batch that automatically takes all WIMs in a folder and combines them. I can make it so it reads all *.wim, then sorts them by getting the edition from the EDITIONID tag and the name/description from the DISPLAYNAME tag, but I don't know how to identify if a WIM is x86 or x64...