this is the line error 87 ¿ cannot find path data/all ended up with a 300mb iso without the install.wim file. lol can u upload the standalone script for exporting the win10 boot,win to win7. thanks
Sounds like you didn't provide the needed source win 7 and win 10 ISOs (not needed for the legacy tool script).
What exact MSDN Win 7 ISO did you use? Can you provide the full ISO filename and sha1 checksum, and for the 2016 LTSB ISO too? What exact script did you run? On what host OS did you run it?
Code: en_windows_7_enterprise_with_sp1_x64_dvd_u_677651 A491F985DCCFB5863F31B728DDDBEDB2FF4DF8D1 6467C3875955DF4514395F0AFCAAA62A CE09FA98 en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 F1BDFDC0 E39EA2AF41B3710682FE3BBDAC35EC9A 031ED6ACDC47B8F582C781B039F501D83997A1CF working on ltsc2019
Is not a Multiple Editions MSDN ISO (like starter, home basic, home premium, professional or ultimate (you can find this recommended ISO at post #3), all these ISOs contain all consumer grade skus). it's a single index Enterprise VL ISO, not a working source ISO.
I don't know if age has finally crumbled my feeble mind, but I'm actually struggling to use a one-click tool. Hopefully someone can answer a couple questions. Where's the final ISO output to? Honestly, I can't find it anywhere. Where's the log file? I can see the "UpdatePack7.log" in windows directory, but is there not a log of what is output in the cmd window? I wanted it to try to figure out where the ISO was output. It looks like the cleanup at the end of the tool erases the ISO?? That can't be right. What an idiot. Anyone feel like helping? EDIT: also is it correct that it should use over 100GB of disk space? Maybe I've missed something important in the 65+ pages of this thread?
Thanks. Just ran it again and can see there's errors, which will be why it's erasing the ISO directory. Going to try with a different Win7 iso. The legacy tool doesn't need a Win10 iso correct? It should work just with a suitable Win7?
Legacy tool only needs Win7 ISO with multiple SKUs, from post #3: https://forums.mydigitallife.net/th...-install-wim-esd-creation.79421/#post-1516362 For the normal tool, I'm using the original LTSB 2016 ISO (rs1 aka 14393) and it works fine.
Legacy tool didn't work for me :shrug: Got it to output an iso using two good images, but struggling to actually get it installed. I get an error message about "Windows is not able to find the Software License Terms" and it refuses to install. I need to read up on things, so it's definitely me and not the tool which is an excellent piece of work. I've not actually installed an OS on a UEFI machine before so I'm not up to date on the problems. Can anyone recommend somewhere to read up on installing old OS on modern laptops? I'm not really sure what's happening when first powering on more modern laptops, like what UEFI is doing compared to how BIOS used to work, so I think I need to get a grasp of it before I can hope to get this working.
Are the used source ISOs original MSDN Win 7 non VL ISOs? Windows 7 is only officially supported on systems with CSM/Legacy BIOS enabled, if not then you can go try the "solutions" offered elsewhere on the forum but if it's pure UEFI i would advise to install a more modern windows (8.1/10) instead of the deprecated win 7.
There are more things how this can happend 1) Your PC have too less RAM and it cannot read License from install.wim / install.esd 2) License files are missing in install.wim / install.esd in Windows\system32\%SLLP%\Licenses\_Default\%FLAG%\license.rtf" 3) License files exist, but install.wim / install.esd have different image FLAG from presented license files 4) Language mismatch. For example your image is Dutch and License files must be in located in nl-NL. NOTES: %SLLP% = Language code en-US, cs-CZ ets. %FLAG% = Image flag such as Enterprise, Ultimate etc.. Solution 2) If there doesn't exist license files you can siply create blank TXT file and rename it to license.rtf 3) If is broken image flag, fix it using WimLib or GImageX 4) If your image is build by integration language pack, these files maybe aren't in place, simply copy License files from en-US folder Example if you have captured Ultimate into install.wim you need to set correctly FLAG and check if License files are present in needed directory explained above. And I have another last one idea. If you are using Unattended to skip EULA page this error can occur when you are booting from USB and your boot.wim doesn't have correct drivers for your USB controllers. If it still doesn't work I have no idea. These all informations I found and collected during XP2ESD development which use newest setup engine to install XP that doesn't have these files.