It is only a guess, but since the process is not "interactive" it may just do what it should do. G:\I386\winnt32.exe /syspart:F: /tempdrive:F: /makelocalsource /noreboot I don't know, it has to be tested, but WinNTSetup has historically worked very well on both old and more recent environments, so it is likely to work, the doubt is more if it would be more suited for the tests an old version (like the one I linked to) or a latest-latest (though it is a bit of time I don't use it, late evolution was all focused on the new 7/8/10 so while it surely works on them, it has to be seen if specifically the XP setup part still works in a 10 PE). Presumably booting to WinNTSetup under WinPE 10 and installing XP does not suffer from this issue? (untested). Or use mountvol to remove the drive letter and then re-assign it? You could also try to put the disk offline and then put it back online via Diskpart, maybe it is *something* that remains "stciky" in the Windows 10 PE after the creation and formatting? The CONVERT MBR is to switch from GPT to MBR (it is not about simple or dynamic) AFAICT What do you have with list disk and detail disk (like here):Ĭreate the partition via diskpart of the windows 10 PEīoot to another "good" PE, let's say a Windows 7 PE If it is not the MBR and not the PBR code (and I presume it is not the non-cylinder-bound offset and size) then it could be:ġ) some pre-existing data at the end of the disk? (dynamic disks - not entirely unlike GPT - have some info written at the very end of the disk) But it would make no sense, if it happened to both you and your user.Īnyway, I seem to remember that XP/2003 could be installed to *some types* of Dynamic Disk (though noone or next to noone ever did that).
Win xp pe iso en install#
I also don't understand why it is asking me to convert it to a dynamic volume and then install XP, I thought XP had to install to a simple volume?ĭiskpart must have change between Win8 and WIn10. The issue seems to be that it does not like the partition that was created? Just tried that and it did not fix the problem.