Updated! I also added new screen with multieditions setup Code: 08.01.2021 - v1.0.1 - Fixed generating License files for all mentioned Editions during install.wim updating
I don't think it's allowed on this forum, just simply use your downloaded 7 & 10 ISOs. I tested it with 32bit Windows 7 SP1 with all updates + Windows 10 20H2_v2.
Why should that not be allowed those are public files that are available on the Microsoft website itself.
Tool updated to v 1.1, first post updated too to fits these changes! Code: 08.01.2021 - v1.1 - Added prepatched setup.exe (10.0.19041.572 from Windows 10 20H2 v2) to suppress 0xC0000005 error - Many thanks infuscomus from Win-Raid forum - Added w32uires MUI patch to get perfect setup look by removing unneded installation steps
do all updates just mean MassStorage and USB ?! (not DriversPack for Windows XP) Why do you need both Windows 7 and Windows 10 ISO ?! Why don't you just use an ISO? Great job, it would be perfect if it automatically installs all drivers like Driverpacks.net Tools does last thing, is it possible to add multiple languages in the boot.wim to translate the installation GUI? I did not understand what you need w32uires.dll.mui files in all languages ... if you create a SysPrep the RunOnce function I see it useless ... the SysPrep exists just for this, a clean installation without adding anything during the installation. in the next days I will test it ...
I'm preparing Capture.cmd right now to make it easy for every one. Will be ready in few hours. Windows 7 is here for grab Windows 7 PE - boot files and boot.wim image 2, in new update that will be ready soon there will be also bootloader localization from files from install.wim Windows 10 is here to add Windows 10 setup engine to add ESD support into Windows 7 PE Do not add multiple languages as its useless. For example, I'm using Czech Windows XP that means CS in XP SP3 MSDN ISO names and egual to cs-CZ in Win7/Win10 language terminology images. So I'm using localized ISOs as input. Modern Windows setup engine have 5 steps during first setup phase. 1) Copying Windows files 2) Expanding Windows files 3) Installing features 4) Installing updates 5) Finishing up XP2ESD uses only 3 1) Copying Windows files 2) Expanding Windows files 3) Finishing up w32uires.dll.mui patch means to remove these unneded setup steps t make perfect look. I would like to add support for every langugae that mach XP as you can see at the end of first post. Like if you use RU XP upload me w32uires.dll.mui from ru-RU Windows 10 boot.wim\2\sources\ru-RU. Then I'm able to make RES patch and include it XP2ESD For Driverpacks - yes, this will be added in future as its in to-do list, we need to go step by step to make it Perfect Do all updates means - integrate OnePiece Update pack as is linked in first post - these packs are MultiLanguages and perfectly upgrade XP to latest version with everything you shoud need for start. See his project as it includes all released updates until 22 June 2017
Updated to v1.2 First post updated with new informations and download link Code: 09.01.2021 - v1.2 - Added CaptureVHD.cmd for easy capturing Syspreped VHD - Improved BCD localization on setup media - Fixed diskpart handling for removing unnneded recovery partition created during setup - Fixed generated boot.ini attributes @infuscomus CaptureVHD.cmd is ready, let me know how it goes
@George King your CaptureVHD.cmd had problems on my machine - It said it could not find some drive or path specified, and then on the Capture WIM step it got stuck and ended up in a loop, stopping it I ended up with a 250gb WIM file.
@George King OK, got the install.wim now - ASSIGNLETTER was G for me, not X But now in XP2ESD_Builder I'm getting "Access is Denied" prompts when I'm running as Administrator. edit: It seems I mixed up my win7 and win10 ISOs
@George King can you do an experiment to see if you can get XP to boot in UEFI mode using your installer?
Updated to v1.2.1! This is most critical update, now is every custom step performed only after successful installation! Code: 09.01.2021 - v1.2.1 - Fixed setup process when user cancel setup and target tag file handling Now its time to check DriverPacks and add support for it