@George King In the Auto-Sysprep stage, virtualbox refuses to run prompting "access denied" on the command prompt and skips through the next step that is supposed to happen after the installation trying to make a VHD of a non-existing installation. My host is Windows 11 Pro 64. I tried to do this with 64 bit win 7 and 10 isos and 64 bit xp iso. I tried to repeat this with only windows 10 64 bit iso and xp 64 iso to make the necessary installers but virtualbox refuses to run. I know you probably said earlier that XP2ESD 1.6 has problems on win 11 host but before on 1.5.6 I could run virtualbox from the command prompt even on win 11. And yes I have tried to run as Administrator, still the same problem. The first time on XP2ESD 1.6 it told me about not enough space so I had to free spaces but even tho there's no more space warnings It could go a little further on the XP2ESD console until it tried to launch virtualbox on the auto-sysprep stage but it prompted me access denied (in VirtualBox, it created the virtual machine but I had to open it manually on VirtualBox), but the problem is that it didn't halt and instead skipped to capture VHD step. Even if I tried to install the os from the integrated iso manually on VirtualBox, the 2nd GUI stage of XP installation took way too long, so I had to cancel the xp installation.
@UsefulAGKHelper Any screenshots please (or console output + log folder)? It should be OK on Windows 11, @nlgxzef builded XP2ESD image under 11 as far as I know.
Is it possible to build XP image with MUI that was released separate? (no Windows XP official edition, just MUI for English)
Yes. I have ran XP2ESD v1.6 test builds on Windows 11 22H2 (22621/2). Also, if that makes a difference, my VirtualBox is installed in my secondary hard drive.
@UsefulAGKHelper How many free space do you have on that drive? Before starting you should have around 50GB free space as minimum.
@George King Here are the logs. There's also my modified Auto-sysprep.cmd where I had to activate xhci alongside existing ehci support on the "modifyvm" command (for VirtualBox) with the scope of allowing the usb 3.0 drivers to be detected and used in the xp installation.
XP doesn't contain any XHCI drivers itself so XHCI for syspreping is useless. Captured system is in original HW support as it was created. All new HW support is added after that
@UsefulAGKHelper USB3.x should be installed using SDI automatically from included ported collection after deploying image. Btw, every driver in captured image is reinstalled to get universal image. So even if you installed it in VM manually before Auto-Sysprep does its job, it will be removed. To get USB3.x installed automatically by system require true USB3.x addon and driver INF too because then in must be in relationship with layout.inf. if anybody create it, it's fine. But for me it's waste of time. Main goal is to get original XP / 2003 captured (that is currently how it's done), because we need to cover like 20 years of future
@George King I just found out that for me VboxHeadless.exe (listed in autosysprep.cmd) is not working for me so I have to use VirtualBoxVM.exe instead.
@UsefulAGKHelper Yes, it takes few minutes. But remember it's done only once before capturing. @MilkChan This problem doesn't exist on Professional distro. This must be in some policy or settings
@George King Yes, the problem is the exact the same under win7 Sp1 and XP Sp3. With the previous version I can start a second run, because it was noticed, that the XP.iso with integrated files was already build and also the *.vhd. Can you set this back in your new version, so I can test this second run again Dietmar