https://forums.mydigitallife.net/th...-wim-esd-creation.79421/page-110#post-1802071 + Updated the simplix updatepack thread OP: https://forums.mydigitallife.net/th...egrate-hotfixes-into-win7-distribution.45005/ Updated the WA addon post with the latest files by @abbodi1406 : https://forums.mydigitallife.net/th...-install-wim-esd-creation.79421/#post-1516362
Thanks. Update went just fine after temp disabling Avast a/v unlike last month's mess with a handful of false positives. Still, I always make a complete disk image beforehand for safety.
Afaik that is about boot.wim\2\sources\setup.exe needs to match ISO\sources\setup.exe else you will get an error at setup from boot about missing license files.
Thats not true exactly, just place License folder into proper place in WIM / ESD. Its enough to have setup.exe only in boot.wim
The error will be actually about missing drivers (and you don't get the partitions/drive) setup.exe must match
I was thinking that too in past. But setup engine works for me always without this famous issue. 1) License folder is always in needed place in WIM 2) Generic ei.cfg is in boot.wim 3) Setup engine can be any from 8-10 in 7 or any other boot.wim version ( only Vista is limited 8.0 setup engine) 4) Unattended works fine 5) winpeshl.ini is used to launch setup Maybe its related to setup.exe launching method.
then apply this solution?, thanks Enthousiast , George King , abbodi1406 I'm still a beginner but with you I learn every day
although I only have a small question, sorry for the inconvenience, does it affect when NTLITE is used to delete the setup.exe? since it only leaves the install.wim and boot.wim
I know it's not an NTLite thread, don't be confused my English is bad because I use a google translator, but anyway thanks Enthousiast
@abbodi1406 @Enthousiast I just discovered why I don't have that driver issue when swapping setup engine. When you run setup.exe with parameters, this issue is gone. I will try to check winsetup.dll in IDA where it parses these parameters. Last time I patched DISM /is-serviceable depency on winsetup. Will see If there is any log to catch that stupid issue. Otherwise another way could be to patch autorun.dll to run setup.cmd instead of setup.exe and handle few lines of code there to run it with parameters and keep “Recovery option” button available