I thought of that and did it and the link seemed to work but when I hit setup inside Windows it doesn't respond. I tried it both ways thinking that maybe the original would start the install and the link might not but that didn't work either. When you boot from the USB and hit the bit version with the "linked" file you get a boot error but it boots from the bit version with the "real" file and gives all the version choices. I suppose a clean install from a boot would work but an upgrade probably won't. Thanks again, and let me know if you think of anything.
Been playing around some more. Found a link to download 10240 with x86/x64 structure, so I could run it through the batch. Figured I'd add other wims to it and I'd have an aio for th1 with the less than 4.37GB space. I got it to work but when trying an upgrade I got the can't validate product key error because the iso I downloaded was Home (unlike th2 MCT downloads that are multi-edition th1 MCT isos are not, and are either Home or Pro), and my system I tried to start it on is 7 Ultimate. The th2 iso will upgrade Home or Pro because the download is multi-edition, but as I said because the th1 MCT downloads are one edition or the other apparently they will only upgrade the same version they originally are. This is the case even though I replaced the wims in the download with th1 multi-edition ones. So I just wondering whether the added wims of Edu and Ent would work if you tried to upgrade those versions since the original isos didn't include them.
..The old trick of using the x36 folder to export all editions x32 and x64 looks me viable and would reduce some mbs more ...^^
When I use wimlib-imagex to export an install.vim to an install.esd, the windows install was unable to find any EULA in VirtualBox. I try with and without EI.cfg. Is generated install.esd by wimlib-imagex valid?
Nothing unclear about it: 2015-12-04 contains the instructions to manually create a Windows 10 Home/Pro x86/x64 (build 1511) ISO under 4.37GB, and on 2015-12-05 the instructions were expanded to include the N edition. The rest is striked out because it used WinAIO which doesn't work correctly with Windows 10. Or just use the batch I'll remove the older instructions and clean it up a bit.
Well, it wasn't especially unclear, it just looked kinda a bit messy, and since it was outdated already, I didn't see a reason why it should be there! Great work!
Were you still planning on a updated batch file? Don't see it as necessary unless you really want to; I made that one change you advised of to correct the mixed .wims warning glitch, and now it gives the warning when it's supposed to and doesn't when it's not. Also, I got step 7 to work correctly with the optimization, so I'd say we're set with ver. 1.1. Sure was strange that it didn't work that time but it's always worked running it from the command line, so that's always there as a backup. Sure am happy with this thread, and will of course be using the batch for redstone 1, 2 and whatever comes afterward!
The only changes I did to the batch was replacing all IMAGEX commands for DISM, except for one. The only command that was not replaced is the one that updates the image name and description to include x86/x64 at the end (useful when upgrading otherwise it lists both x86/x64 with the same name), because not only it updates NAME AND DESCRIPTION, it also deletes DISPLAYNAME and DISPLAYDESCRIPTION. For some reason DISM can only change the NAME field and leaves the other 3 untouched. If DISM was able to change them, IMAGEX would no longer be necessary.
By any chance did you forget to post the new batch? Looks like the one from 12-13-15 is the latest (v.1.1). Hope I'm not a pest. Thanks!
While your at it you could also change the old cdimage.exe for Oscdimg.exe which is current in both 32 & 64bit...
I was using cdimage 2.53 because M$ is still using it on MSDN ISOs, but now that I took a closer look, the ISOs created by the MDC seem to use Oscdimg. I'll see what parameters it needs to obtain the same result and replace cdimage too
Here's what I've used in the past, very similar to cdimage: Code: set PTH=%~dp0 Oscdimg -m -l"Win7Pro64OA" -bootdata:2#p0,e,b%PTH%SRC\boot\Etfsboot.com#pEF,e,b%PTH%SRC\efi\microsoft\boot\Efisys.bin -u1 -udfver102 %PTH%SRC %PTH%Win7Pro64OA.iso
I Fail to creat aio w10 v1511 iso by using this... I need WinToolkit the last version, please anyone give me a link and explain to me how i can add languages and activation, many thanks