@johnye_pt: Wow, you are the man! I was too afraid to try and more afraid to ask, but ideally I'd like to have Education and Enterprise x86 and x64 incorporated into the .iso, and it looks like it would probably fit onto a DVD5. Don't really have much desire to have extraneous versions such as LTSB, N, or single language, etc. Is a guide out of the question, since I could never construct it myself?
Thanks! Exactly what I was searching for! If I manage to find the time to make one, a batch will make it easier. It will just use 3 folders: TOOLS for the required programs, WIM to place the wim files, and AIO to place the files from the ISO created by the Media Creation Tool. Hopefully the batch will scan all WIMs, sort them by architecture and name, then create the WIM, convert to ESD and create the final ISO. Hopefully...
Just finished the batch! Should be very easy to use, it already includes all the tools, just read the README and follow the instructions, then let it do all the work for ya!
Nice guide, good job! So are you saying this AIO actually is able to boot BIOS / UEFI mode on both architectures?
Everything went well but in the end it came out to over 7GB. I added four wims to the wim file, Education x86 & x64 and Enterprise x86 & x64. Seemed to recognize and add them properly so I'm not sure what happened. I was working on a 'guide' adapting your from Win10 and Win10N to add the Edu and Ent before I saw your post--I didn't really do too well as the versions got a little scattered but it did come out at the proper 4 GB size. I was planning on trying it again but went for the batch first. I'll show it to you if you want after the batch issue gets settled. I notice cdimage.exe is missing from the x64 tools folder. Here's the wimlist.txt: x64,Core,Windows 10 x64 Home,2,install.wim x64,Education,Windows 10 x64 Education,1,install_edu_x64.wim x64,Enterprise,Windows 10 x64 Enterprise,1,install_ent_x64.wim x64,Professional,Windows 10 x64 Pro,1,install.wim x86,Core,Windows 10 x86 Home,2,install(1).wim x86,Education,Windows 10 x86 Education,1,install_edu_x86.wim x86,Enterprise,Windows 10 x86 Enterprise,1,install_ent_x86.wim x86,Professional,Windows 10 x86 Pro,1,install(1).wim
For what it seems, yes, although I don't have a UEFI computer to test it on, but only the install.esd is changed, everything else remains untouched, including both boot modes.
Probably you're mixing build 10240 with build 10586 versions? If so, the WIMs won't be just a few MB different, they'll be completely different.I'll see if I can update the batch to add build to the txt file so you can verify that
I have an UEFI computer, mine for personal use I downloaded MCT to test. Also I have downloaded iso files separately via torrent. How can I skip Download stage in MCT? Do you know a workaround? I ask because I suppose MCT does something to boot files or changes iso structure, really don't know.
MCT doesn't change any of your files if you simply create an ISO: 1st screen: select "Create installation media for another PC" 2nd screen: disable the "Use the recommended options for this PC", change "Architecture" to "BOTH" 3rd screen: select "ISO file" Try the new v1.1. If you still have the same WIM files in the WIM folder, just run step 3 and see if wimlist.txt has different builds right after each image description, they should all be either 10240 or 10586, if you have both the combined WIM/ESD will be much bigger. EDIT: cdimage.exe is not missing from the x64 folder because there is no x64 version of cdimage. The batch simply uses the x86\cdimage.exe on both architectures.
.....I think that imagex is old for work with windows 10 and 8 in the case would be good to use dism.... ^^
Although DISM can be used to get some of the info I get with IMAGEX, not everything can be done with it: for example, DISM can get <NAME> and <DESCRIPTION> but IMAGEX can also get <DISPLAYNAME> and <DISPLAYDESCRIPTION> which show different names for each versions. Also, if it wasn't for the Architecture field which IMAGEX can't get but DISM can, I wouldn't need DISM nor Administrative privileges to run the batch.
I used the all .wims version I had, so the original download and the Edu and Ent are all .wims, and it still gives the warning. What about using all .esds?
Ummm that's weird. I also used the ESDs from the ISO and added all the WIMs from other b10586 ISOs I had, the batch simply converted the ESDs to WIMs and successfully created a WIM around 5GB which was converted to a 3GB ESD. Maybe to ESDs from the ISO are different... Are you using en-US? I'm downloading a new en-US ISO to check if the ESDs contains a slightly newer version of Windows 10. EDIT: Try using only the WIMs from the MSDN ISOs, then run steps 3 and 4 to see what is the size of the new install.wim. EDIT2: I'm changing some of the imagex commands to dism, in result the "x64"/"x86" is now added to the end of the name instead of the middle, and the build number is now "10.0.10586" instead of only "10586". But I did notice that it's warning about me different versions although it's basically just comparing "10586"=="10586", gonna take a look at what might be wrong there. EDIT3: found the bug, it's a very stupid error... where it reads: Code: if not "skipFirstLine"=="1" ( should be Code: if not "!skipFirstLine!"=="1" ( It was not comparing a !variable!==1, but text==1 which always fails and executes the wrong lines, resulting in the warning always showing up. ISO download at 51%...
I even tried just the original MS download (with .esds) and didn't add any other .wims, so just the original file, and it still gave the warning. Yes, I am using en-US. I'm certain that en-US is all straight 10586.0. Real strange, because I didn't have this problem at all with the guide, and as I said yesterday I tried it and even though I screwed up the versions it still gave me a 4GB .iso. I've attached the modified guide I tried to make--see if you have any time to look it over. Note that I struck out an additional 'renaming' because I didn't think I needed it.
Just ignore the warning, check my previous post for the fix. Still trying to figure out what causing the huge ISO. Can you check a few things for me? - what's the size of the newly created INSTALL.ESD? - Are both x64\sources\install.esd and x86\sources\install.esd exactly the same size in the final ISO? EDIT: The renaming is only necessary if upgrading from Windows 7 or 8.x, because the setup will list both x64/x86 versions but doesn't show an Architecture column, so you will see 2 lines called "Windows 10 Home" or "Windows 10 Pro" and not know which line is x64 and which line is x86.