i want to integrate windows 10 x86 x64 in one. and this is my plan to do so. first remove other editions and keep only core and pro in both iso with the help of "WinAio maker professional" now slipstream updates in x64 and x86 separately with w10ui. after that combined both x64 and x86 with winaio maker professional's auto aio feature. now covert it to esd with abbodi's tool. now my questions are following. 1. is this the correct procedure to so or i can do better than that, (keep in mind i dont have any knowledge of dism or other codes thing) 2.can this aio create problem in installing in efi systems which only support x64 bit? 3.will i be able to do dism restore health with this Code: dism /online /cleanup-image /restorehealth Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:x:\sources\install.esd:1 /limitaccess 4. or i can face any other problems in future with this aio. or with 7 and 8.1 aio problems are going to be any different. please share your experiance if you have tried this thank you very much.
1. Isn't that tool for 7 and not updated by a long time? 2. Download the ESD's manually, run @abbodi1406's ESD>ISO v37 script and select the alternative multi-arch iso to be created. It creates an iso that can be booted x64 eufi/bios and x86 uefi/bios (the latter can't be done by the MCT created multi-arch iso). 3. You can always do a restorehealth
thanks @dhjohns @macnavarra for the answers, i'll try to use dism to modify images. thanks for reply @Enthousiast . yes it looks a good idea to use abbodi's tool to create multi arch iso, but how am i suppose to slipstream updates in that multi arch iso, to create an updated iso? i think i can use the abbodi tool method to create multiarch win 8.1 iso as well? but what would you suggest in case of ltsb multi arch iso, bcoz i cant seem to find esd for it. in win 7, i guess using winaiomaker to create multi arch iso would be a good idea.and it can boot in x64 uefi/bios and x86 uefi/bios ? i'm sorry for these too many question, but i'm confused. thanks for the patience.
Create two iso's, one uptodate x86 and one x64 and use the standalone Multi-arch iso script, included in the ESD>ISO v37 Project folder..
thank you @abbodi1406 @Enthousiast now i'm gonna create multi arch iso for win 7, 8.1, and 10 with multi_arch_iso.cmd
Hi, @Enthousiast is it possible to create a multi arch iso and still have the ability to do "upgrade install" with mounted iso?
any script or tool available for making multi arch iso manually with mct method? i want to create multi arch iso for 7,8.1, and 10, ltsb with slipstreamed iso's.
Option 1 in ESD>ISO or multi-arch iso script, Your iso will be very, very, very, huge and not really usable without an alternative setup script like @murphy78's diskpart and apply image script.
Now this may soungs like a whole diffrent question from the topic, but at least I hope to answer this riddle for me and for those after me: what is the most effcient way to combine the missing vesrsions of windows into a precompiled .esd, for example: The 17134.1 ClientConsumer (OEMRET) ESD x64 is missing the Workstation and Enterprise versions of windows How it will be possible to join these missing esds into the consumer edition to become a all in one full .esd or iso or should it be converted first to an AIO ISO and then add somehow? the Enterprise stuff? or anywhere to download every single esd SKU and then to combine it into an iso? The end result should be an esd or iso file containing these: Code: [01] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Home | Core [02] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Home N | CoreN [03] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Home Single Language | CoreSingleLanguage [04] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Education | Education [05] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Education N | EducationN [06] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Pro | Professional [07] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Pro N | ProfessionalN [08] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Pro Education | ProfessionalEducation [09] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Pro Education N | ProfessionalEducationN [10] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Pro for Workstations | ProfessionalWorkstation [11] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Pro N for Workstations |ProfessionalWorkstationN [12] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Enterprise | Enterprise [13] 12/04/2018 en-US x64 10.0.17134.1 Windows 10 Enterprise N | EnterpriseN
There are so many ways to do that, 2 examples: From ISO: 1. Extract the install.wim from a Consumer MVS ISO. 2. Extract the install.wim from a Business MVS ISO. 3. Export the enterprise and enterprise N indices to the Consumer install.wim 4. Discard the Business install.wim 5. Update it by using @abbodi1406 W10UI script From ESD: 1. Convert the Consumer ESD to AIO ISO by using ESD>ISO v37 2. Use either WES by @s1ave77 or "create_virtual_editions.cmd" by @abbodi1406 (from UUP>ISO v15) to create the other SKU's 3. Update it by using W10UI script by @abbodi1406
Thanks for the fast and adequate response, seems simpler to read it than to do it. Some of these techniques I am aware of, and some I am not. Anyway it is a celebration for me to try them all ;-) Thanks again for directions! Have a good one all!
Another great Guide! That one really makes most sense in Dism. That Guide should be published for all in a special part of this forum! You were really helpful @Enthousiast !
What Can I say, the "create_virtual_editions.cmd" just knocked my socks off, dawg! By the way you explain info around here, there is no need of a General Content! You're everywhere around here! @Enthousiast , you need to be promoted!