unfortunately it does not work... could it be a problem of the final install.wim, when created with Gimagex? To create the aio which program do you use?
GimageX only executes the imagex export command, it's not anything magical. On the test i did i've used GimageX to export the windows 7 indices into a windows 10 install.wim. I showed you that you don't even need an ei.cfg to get it to work, just put the install.wim in a win 10 consumer iso and it will install fine.
you're right but I have a problem with the windows 10 versions only ... I'll do other tests and I'll know
I was also struggling on this, after checking files one by one, finally I found ... winsetup.dll from sources folder makes AIO difficult for Windows 10. I used winsetup.dll from Win10 1709, the setup.exe won't work for Win10 1803; similarly, using winsetup.dll from 1803 makes setup.exe not working for 1709. [UPDATE] you can try this out by replacing the X:\Sources\winsetup.dll with a target one. Changing this dll will do the magic for different Win10 releases. And you can run the setup from command line: X:\sources\setup.exe /installfrom:\sources\install.wim /noreboot
Why would you mix & match file from different win 10 versions,I thought such AIO means different editions of same version of windows(& not an AIO of RS3 & RS4 pro etc).
Because Win10 1709 and 1803 are not end of life, they are still needed by different people, not only older windows versions like Win 7/8. I am trying to combine all those often used images together, but the setup.exe seems not working for this.
Thank you so much <3 You saved my day... Problem with me was Windows 1809 setup.. I merged 7 8.1 and 10 wim in one. And used win 10 sources as base for iso. For Win 8.1 SL and 8.1 Enterprise i was getting that error "Microsoft license not found etc.." Then I mount the 8.1 SL image and change the License dir as per win 10 SL. Same with ent edition. and the error is gone. Hope this help someone someday.