[TOOL] XP2ESD - Create modern Windows XP installer v1.6.2

Windows XP on Hyper-V? Yes
Hyper-V on Windows XP? No, but VirtualBox does not go on XP either

 

You need to login to view this posts content.

 

@George King To make it simpler, all my multi-boot tool requires is a folder of the complete iso with a modern installer already created by XP2ESD (found in _output).
Extracting the XP install.wim and altering it with the modified wim-setup.cmd has it's benefits.
You bypass WinPE problems, errors (you bypass license, eula, product key), and prompts.
You won't have to worry about the USB drive not being detected if winpe drivers malfunction (the drivers exist on the live os).
If wim extraction is faster, then XP installation may be quicker similar to how XP2ESD_builder.cmd extracts images.
All you would have to do is basically plug the USB drive, adjust the paths, partitions, drive letters, set installation type (default, multi-boot, vhd etc) in settings.ini and once it's finished from doing the tasks in the wim-setup.cmd batch file, you should see the XP OS already extracted and tweaked in the desired partition (if it's on a different partition of the same drive, an entry should appear on BCD of system drive).
When that boot entry is selected and proceeds to boot XP from winload or ntldr, theoretically there should be no difference between the version created by WinPE and the one created by this tool.
If there's no difference, theoretically myfactory setup should work properly and continue setup from there as usual.
Basically, you would have two ways to install the XP2ESD XP OS, from WinPE or from batch file.
Maybe I can make it universal so it will be able to also AIO install 7 and newer OS from batch without winpe (using the other win 7 and newer section from the wim-setup.cmd file).
The only thing is that I already modified the wim-setup.cmd batch file to exclude C drive from drive letter (this particular tool is not designed to modify running os, only adding a new installation in another partition). If running OS is on any partition letter than C, then I can modify to batch to exclude that particular letter instead.
I know that you already know this but I wanted to give you and everyone else more information in order to get my point across.
I know this tool may use XP2ESD values, settings, and directories so it's compatible with XP2ESD ISO, but I think I should make a new topic someday for my tool even tho it's XP2ESD-related.
I know WinNTSetup exists, but this tool may work together with XP2ESD tools and files to provide support for properly tweaked myfactory XP wim installation without WinPE.
This may seem like a waste of time but I will take the risk by trying to do this myself later. Right now I'm focused on trying to boot XP on uefi class 3.

 

Why is it so important that the script runs under Windows XP?

It doesn't, min host system is x64 windows 8.1

 

What problems do you have that you want us to use win8.1?

 

Acutally this is true for modern versions of VirtualBox.
However you can use old versions of VirtualBox like VirtualBox-4.x.x.
It works on both x86 and x64 Windows XP hosts.

 

These are the minimum requirements of VirtualBox

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Does anyone know how to patch the 64-bit version of Windows setup.exe so that it suppresses the 0xC0000005 error? The 32-bit version works fine but I would like to use the 64-bit version of WinPE since I mainly use x64 WinPE.

 

I understand it's probably not supported. I just wanted to know how to patch x64 Windows 10 SETUP.EXE file to suppress the 0xC0000005 error. If it's not possible, I understand.

Thank you for your hard work.

 

I used Win10 1809 x86 to create the original ISO. But then I extracted the contents and moved the files over to my custom WinXPE10 x64 USB stick, which I use to install VISTA-Win11. So that's why I need a patched Win10 x64 SETUP.EXE.

Everything works... I just have to manually clear the 0xC0000005 error and I would like to hide it.

 

I didn't realize that Win10 x64 was supported? On the first page, it specifically states to download Windows 7 and Windows 10 32bit. I will try 64Bit and see if that will work.