I wouldn't worry too much about that since it's just a problem with an obsolete version unless it's a real easy fix or it matters to you. The batch works fine with 10586 and that's what really counts. Nobody's going to be installing 10240 much anyway and it's hardly a crime to use slightly larger media if necessary. Look forward to whatever new refinements you've got in mind. Like I've said several times, your work is very well done to this point, and is very much appreciated.
I think that you were probably right about something wrong with that USB drive. Seemed to work ok for a while but then I put another .iso on it and the install.wim file out of nowhere went to zero bytes. I low-level formatted it, so will see whether that fixes it. The phenomenon that it gave about reporting less space than the files were actually taking did not happen with any other flash drive set up the same way, i.e., with different install.esd file sizes under different x86 and x64 sources directories. Again, must be something with that hardware.
@genenioo, Thank you poweruser info to get Win10 v1511 MCT Dual Boot (x86+x64) en-US Disc Universal Layout zip download. I can used it my own created x86 folder (install.wim or esd)and x64 folder )install.wim or esd) to replace to them. I did this method already before but this zip has a little updated. Works fine. Thank you again.
if I insert the related product keys in their respective volume images of Windows 10.x, when I create manually the AIO containing more editions of this OS, the window, which lists these editions during the first installation phase, is automatically displayed even without inserting the ei.cfg file in media. Right? Thanks Bye
Windows 10 doesn't use ei.cfg. It displays all editions inside the esd/wim if booted from DVD/USB for you to choose from, and displays compatible editions when upgrading from Windows 7/8.1 (or skips this step if only one compatible edition is found).
....You dont need insert the keys to release the editions...just ignore the part that asks key and click below,i do not know my key...and all versions in image will be listed...
So Windows 10.x does not use the ei.cfg file. Since the input window of the product key is displayed when I boot the MSDN Multiple Editions (Home and Pro) of Windows 10.x, what is the way to prevent that this window appears in order to display immediately the window that lists the two editions contained in the install.wim file? Thanks Bye
I tried again and I can affirm that, injecting the product keys in the volume images of the install.wim file of the Multiple Editions (MSDN) or Education (MSDN) isos, the input window of the product keys is displayed during the first phase of the installation of Windows 10.x. Why? How do I avoid this unnecessary window without using the ei.cfg file? Thanks Bye
It is possible to include in pid.txt file or in some other file the various product keys corresponding to the respective volume images that exist in the install.wim file? Thanks Bye
It is possible to create an autounattend.xml file and insert in it the product keys related to all editions included in the install.wim file? Thanks Bye
If I create an autounattend.xml file in the root directory of the media and insert this block Code: <UserData> <ProductKey> <WillShowUI>Never</WillShowUI> </ProductKey> </UserData> I avoid displaying the input window of the product keys during the first phase of installation and therefore, the window, which lists the editions included in the install.wim file, is displayed immediately. Right? Thanks Bye
Created an AIO ISO with Feb 2016 updated MSDN ISOs using this batch. AIO ISO's size was 5.92 GB. My ISO containing 32 and 64 bit architecture WIMs of Core, Single Langauge, Pro, Education and Enterprise.