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.
for me i tested with EN-US language but for the cdimage.exe couldn't found version 2.53 for that i used oscdimg.exe V 2.56 instead cdimage.exe 2.53 ------------------------------------------------------------------------------------------------------------------- that's why i used oscdimg.exe ------------------------------------------------------------------------------------------------------------------- command with cdimage.exe v2.52 not completed C:\WINDOWS\system32>D:\WIN10_AIO\TOOLS\cdimage.exe -u2 -udfver102 -bootdata:2#p0,bD:\WIN10_AIO\boot\etfsboot.com#pEF,ebD:\WIN10_AIO\efi\microsoft\boot\efisys.bin -o -lWIN10_AIO -t10/30/2015,12:32 D:\WIN10_AIO\ D:\WIN10_AIO.iso CDIMAGE 2.52 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2000. All rights reserved. For Microsoft internal use only. Usage: CDIMAGE [options] sourceroot targetfile ----------------------------------------------------------------------------------------------------------------- with oscdimg.exe v 2.56 working fine ----------------------------------------------------------------------------------------------------------------- C:\WINDOWS\system32>D:\WIN10_AIO\TOOLS\oscdimg.exe -u2 -udfver102 -bootdata:2#p0,bD:\WIN10_AIO\boot\etfsboot.com#pEF,ebD:\WIN10_AIO\efi\microsoft\boot\efisys.bin -o -lWIN10_AIO -t10/30/2015,12:32 D:\WIN10_AIO\ D:\WIN10_AIO.iso OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (1500 files in 125 directories) Scanning source tree complete (1991 files in 212 directories) Computing directory information complete Image file is 7445970944 bytes (before optimization) Writing 1991 files in 212 directories to D:\WIN10_AIO.iso 100% complete Storage optimization saved 712 files, 3342239744 bytes (45% of image) After optimization, image file is 4109697024 bytes Space saved because of embedding, sparseness or optimization = 3342239744 Done.
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.
C:\CDIMAGE_OSCDIMG_and_CDImageGUImods\CDIMAGE_Editions\CDIMAGE_2.54>cdimage.exe -u2 -udfver102 -bootdata:2#p0,bD:\WIN10_AIO\boot\etfsboot.com#pEF,ebD:\WIN10_AIO\efi\microsoft\boot\efisys.bin -o -lWIN10_AIO -t10/30/2015,12:32 D:\WIN10_AIO\ D:\WIN10_AIO.iso CDIMAGE 2.54 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. For Microsoft internal use only. Scanning source tree (1500 files in 124 directories) Scanning source tree complete (1990 files in 211 directories) Computing directory information complete Image file is 7445872640 bytes (before optimization) Writing 1990 files in 211 directories to D:\WIN10_AIO.iso 100% complete Storage optimization saved 712 files, 3342239744 bytes (45% of image) After optimization, image file is 4109578240 bytes Space saved because of embedding, sparseness or optimization = 3342239744 Done. ----------------------------------------------------------------------------------------------------------------------------- C:\CDIMAGE_OSCDIMG_and_CDImageGUImods\CDIMAGE_Editions\CDIMAGE_2.53>cdimage.exe -u2 -udfver102 -bootdata:2#p0,bD:\WIN10_AIO\boot\etfsboot.com#pEF,ebD:\WIN10_AIO\efi\microsoft\boot\efisys.bin -o -lWIN10_AIO -t10/30/2015,12:32 D:\WIN10_AIO\ D:\WIN10_AIO.iso CDIMAGE 2.53 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. For Microsoft internal use only. Scanning source tree (1000 files in 110 directories) Scanning source tree (1500 files in 124 directories) Scanning source tree complete (1990 files in 211 directories) Computing directory information complete Image file is 7445872640 bytes (before optimization) Writing 1990 files in 211 directories to D:\WIN10_AIO.iso 100% complete Storage optimization saved 712 files, 3342239744 bytes (45% of image) After optimization, image file is 4109578240 bytes Space saved because of embedding, sparseness or optimization = 3342239744 Done.
after comparing the result using OSCDIMG v 2.65 or CDIMAGE v 2.54 and 2.53 will give me the same result man with EN-US Language for Windows 10 AIO
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.
my comparing was between the cdimage.exe and oscdimg.exe. the result will be the same for create an ISO file that's what i mean, also my tested was with (windows 10 x64 x32 ISO) V 1151
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!