I've got two iso's (one x86 and one x64) with all versions including Enterprise. I would like to combine them into one iso with the MCT boot setup. I tried to use the ESD>ISO script, but it kept complaining that I needed Win10/11 setup files. Is this possible?
Which exact files do I need? And what directory do they go in? I have seen setup on the root directory and the sources directory. Is there a guide somewhere for this? TIA
This could be a start: https://forums.mydigitallife.net/th...-wim-esd-creation.79421/page-122#post-1862080 EDIT, i edited the linked post because it used UUP>ISO instead of ESD > ISO.
You did not see or create Win10 MCT x64 & x86 iso? just follow the same structure but that not really recommended for Win7
I did that in the past too, create the win 10 MCT mylti-arch ISO first and then remove all unnessecray setup files and replaced the original boot and install.wim with the win 7 versions, was a long time ago and the mixed multi-arch iso works fine, you can't use it for upgrades anyway
Thanks for the link. I already did option 1. I'm trying to do option 2. What were the 'unnecessary' setup files you deleted? I tried to substitute the 'setupx64' and x86 files (and the boot.wim files too) for the setup files in the .x64\sources and .x86\sources directories but on boot the system crashes.
Option 2 is not working for 7 afaik. It has been so long now for the time i did an option 2 windows 7 ISO, have to find one on my usenet posts.
I've tested option 1 recently and it does work fine. For option 2, I still have a "shell" of a windows 10 multi-arch iso where you just insert your x86 and x64 isos contents into the x86 and x64 folders respectively. Only issue is I think it needs actual windows 10 setup files and just install.esd's from windows 7. If you want setup to look like windows 7, then you have some fiddling to do with **img.dll files. I tried this same iso just now with my current windows 7 isos and they each boot, but as soon as you select the language they both ask for storage driver and I don't know where exactly it all breaks. Usually it was due to setup.exe missmatch but the win7 isos themselves work as intended on their own.
Nope, i can only find my alternative aio win 7 isos (mixed x86/x64 install.wim), will check this out when i am feeling better.
At this point I can't remember all I've tried. Mainly I've started with a Win 10 MCT dual iso and replaced the boot.wim and install.wim. I've tried various combos of UEFI and BIOS boot. Nothing works completely. I.e. 64-bit os would install on BIOS but not the other way around. As someone mentioned above, when things looked like they were going to install I would get a complaint about needing some storage driver. It would be helpful to know how to get bootmgr to point to specific setup files to run.
That probably is because of mismatching setup.exe in boot.wim\2\sources and iso:\sources (or did that trigger the licensing error). WIll test asap, have to go to bed now.
Not just the .wim files. That's when you get to Put your entire win7 iso's contents into those folders.
My script creates working win 7 ISOs with install.esd, you can do that yourself but i did it the fast way 4 years after EOS/EOL and 16 years after it first was released i don't really care about the win 10 looks in the first window, it changes instantly to 7 after pressing one button. Best is to just create the ISOs using the legacy script and use them separately, then the ISOs can also be used for inplace/repair upgrades..
EDIT: I figured it out. Why didn't my original SP1 ISO's work for this? Basically I am wanting to know if there was a more modern boot.wim or setup file etc. that are in the Simplex iso's? Also I noticed that when using UEFI it doesn't give me the option to choose between x86 and x64. It goes straight to x64. Do you know why? This is under vmware btw.