[SOLVED] WinXP conversion from esx to pve refuses to boot

what a stubborn donkey this setup is. Well I tried now with a newly created disk within proxmox instead of importing or configuring the disk I got from esx - either by converting it from vmdx, or by import wizard or by restoring it from clonezilla.

But a new created disk in proxmox and new setup works fine, and seems to boot easily. Still finishing installation, but at least after reboot the setup continues.

Hi _gabriel. I already tried fixing the mbr but after what you write I ll try to boot from a livemedium and check for activ/boot flag with cfdisk, and or table partition.

On the other hand - is there a way to copy everything over to the running system leaving the partitiontable alone - just copying the files within nfts partition from the initial setup to the newly setup so I get all tools and configurations running in proxmox?

I am trying rsync -a /mnt/source/* /mnt/destination/ and see where it gets. (although it seems an ugly hack to me)

As last resort I ll come back to you, gabriel. Thanks.
 
Last edited:
Hello Gabriel, but this is a imaging thing, which I already did with clonezilla with the same result even fixing the mbr afterwards by winxp cd didnt help, so my assumption is that the disk created by vmware is problematic while a disk created within proxmox let me install winxp from scratch without any problem. Thus I dont want to image again, but copy the files from within the filesystem from source to newly installed disk (which boots from proxmox).

Thats why I first try by livesystem (linux) boot -> rsync -a
 
Last edited:
this is a imaging thing
wrong, "wim" capture isn't imaging / sector-based , it's file-based, like rsync.
"wim" can be restorerd over existing data, without deleting others folders already present.
You can't copy Windows system with rsync. That's why "wim" exist. it's the technology used since Windows Vista to install system.
 
  • Like
Reactions: Elleni
I see, then my google wasnt correct so thanks for pointing it out. Then this will be my last resort to try. Thanks again for your feedback much appreciated.
 
Making progress. At least it started booting and then bluescreened, so my next try is to attach both disks - the source and the empty but created by proxmox one to a running win10 guest and use wim as soon as I learned howto do it :)
 
I didnt as I beleived you that rsync is not the way to go thus now following the wim way you proposed.

For reference - as it might help somebody in the future here is what I have done so far:

added the winxp source disk and the winxp destination disk to a win10 guest.

Added an additional disk to have enough space to store the wim file.

Then installed win adk kit on the win10 box from here:
https://go.microsoft.com/fwlink/?linkid=2243390

then opened cmd as administrator on the windows 10 guest and started creating the wim file by:
dism /capture-image /capture-dir:E:\ (thats the non-booting disk from esx) /imagefile:G:\WinXP.wim /name:WinXP

This will take a while, so I am heading for the weekend. Next week I ll try to restore it by:
dism /apply-image /imagefile:G:\WinXP.wim /index:1 /applydir:F:\ (the Disk created on ProxMox and installed naked WinXP which boots)

and see where it gets.

Maybe I'll need to run bootrec to fix/setup the boot configuration on the restored partition, maybe not. We'll see.
In the meantime thanks for your patience with me, guiding me through the possible solutions and have a nice weekend all.
 
Last edited:
As foreseen by _gabriel the famous bluescreen could be fixed by a winxp-sp3 repair install over it after applying the wim file. Now the only thing to find out remaining is howto avoid the setup to need re-activation.

And yes, I tried to use display -> vmware. @donhwyo - made no difference.

To make it clear - I tried to create a new disk on proxmox, and then directly applied the wim file which doesn't fix the operating system not found error.

I explicitly had to install a naked, fresh winxp first. After that applied the wim file which brought me to the bluescreen step.

Before that I unsuccessfully tried all sort of fixes like bootcfg/rebuild fixmbr from windows recovery window.

Then booted the winxp iso once again, to reinstall with the R-Option.

Now trying to either avoid or re- activate the os.

Finally I'll have to install virtio drivers to be able to use those devices once everything else is settled.

(For completeness sake I'll also try again, if the rsync option instead of the wim way would also work fine)
 
Last edited:
I didnt as I beleived you that rsync is not the way to go thus now following the wim way you proposed.

For reference - as it might help somebody in the future here is what I have done so far:

added the winxp source disk and the winxp destination disk to a win10 guest.

Added an additional disk to have enough space to store the wim file.

Then installed win adk kit on the win10 box from here:
https://go.microsoft.com/fwlink/?linkid=2243390

then opened cmd as administrator on the windows 10 guest and started creating the wim file by:
dism /capture-image /capture-dir:E:\ (thats the non-booting disk from esx) /imagefile:G:\WinXP.wim /name:WinXP

This will take a while, so I am heading for the weekend. Next week I ll try to restore it by:
dism /apply-image /imagefile:G:\WinXP.wim /index:1 /applydir:F:\ (the Disk created on ProxMox and installed naked WinXP which boots)

and see where it gets.

Maybe I'll need to run bootrec to fix/setup the boot configuration on the restored partition, maybe not. We'll see.
In the meantime thanks for your patience with me, guiding me through the possible solutions and have a nice weekend all.
I have found 3 xp vm's in old backups. One worked fine (the one I might care about.) The next one needed reactivation. The last one is in the same condition as yours. The 2 may not have booted since pve 6. I will try a bit and see if I can see anything.

For reactivation look for a file called xp_activate32.exe. Read about it and download from a safe source?
 
Or use microsoft telephone activation, it's a drag but works, tested this with windows 7 a few months ago ...
Have you tried for xp? Lots of internet reports it no longer works. I waited on hold for too long and gave up. Maybe just a phone glich.
 
Thanks guys - after further testing I can report that:

- I need a new install from winXP medium to a new proxmox disk in order to get rid of the operating system not found.
- From there either a copy of the old install either via linux livesystem and rsync -a or a copy via wim file from another win10 vm
- That brings the famous bluescreen but at least boots, which then is fixed by
- Reinstalling winxp over the newly installed and copied data disk with the R-Option

Now only the activation needs to be achieved as the only way to login is via safe mode.

Thanks for your messages all, will try to activate and then finally report this thread as fixed.

Unfortunatelly I am not able to activate it via telephone robot, whatever I ask. It ends up hanging up.

Edit to add I also tried all sorts of registry hacks to try to reset the 30 days time for activation, but nothing seems to help. Still crawling the net...

Tins I tried but didnt help:
https://www.youtube.com/watch?v=RGCcVhpx5S4
https://boma23.wordpress.com/2012/08/30/windows-xp-stuck-at-login-screen-in-activation-loop/
 
Last edited:
Thanks guys - after further testing I can report that:

- I need a new install from winXP medium to a new proxmox disk in order to get rid of the operating system not found.
- From there either a copy of the old install either via linux livesystem and rsync -a or a copy via wim file from another win10 vm
- That brings the famous bluescreen but at least boots, which then is fixed by
- Reinstalling winxp over the newly installed and copied data disk with the R-Option

Now only the activation needs to be achieved as the only way to login is via safe mode.

Thanks for your messages all, will try to activate and then finally report this thread as fixed.

Unfortunatelly I am not able to activate it via telephone robot, whatever I ask. It ends up hanging up.

Edit to add I also tried all sorts of registry hacks to try to reset the 30 days time for activation, but nothing seems to help. Still crawling the net...

Tins I tried but didnt help:
https://www.youtube.com/watch?v=RGCcVhpx5S4
https://boma23.wordpress.com/2012/08/30/windows-xp-stuck-at-login-screen-in-activation-loop/
Have a look here.

Phil
 
Thanks @Blonov but I managed without those links to keygen downloads n stuff.

Basically the two last links, I posted helped me to fix the issues remaining. I had to first boot into safemode with command prompt in order to be able to manipulate the registry. I then started explorer.exe to get startmenu and with start / run I was able to start regedit.

For completeness sake I post what I did in this post just in case the links become unavailable:

in command prompt I did:
regsvr32 regwizc.dll
regsvr32 licdll.dll and
rundll32.exe syssetup,SetupOobeBnk

although I am not sure if necessary I also did a:
cd c:\windows\system32\oobe then
msoobe.exe /a

Those commands are supposed to reset the 30 period in which one has to activate.

The vid basically shows a reg key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEventS
where one should delete the numbers after the 0000 and instead fill in the following: FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD like this:

1758705429825.png

And to prevent WinXP to overwrite it, remove the write right from system like this:

1758705505516.png

In my case I still had a blue background screen after login, with no startmenu loading, which did not go away but this winxp install has also configured a custom network warning message, that pops up from time to time. Thus I checked the starting programs with msconfig and removed the following two:

1758705675645.png

vmtoolsd I already had removed before. But as the above did not load a startmenu initially, even after manipulating the registry keys I tried to boot without msmsgs and that did the trick, to the point that after the initial login where I ended up installing all the virtio drivers, I even was able to re-enable msmsgs and the system still behaved good, meaning - no not activated message until now.

One last thing was an error of mslogon.exe immediatelly after login and loading startmenu, and the source of that problem was a dll file from vmware tools, that I had to change.

In c:\windows\system32 folder -> VMUpgradeAtShutdownWXP.dll to VMUpgradeAtShutdownWXP.old. Which apparently also had to do with the vmware installation.

Last but not least I read somewhere in fedora bugreport that scsi-passthrough is not supported thus I use virtioblock for harddisk. Following the resulting config in ProxMox.

Code:
agent: 1,fstrim_cloned_disks=1
bios: seabios
boot: order=virtio0
cores: 1
cpu: x86-64-v2-AES
ide2: local:iso/virtio-win-0.1-52.iso,media=cdrom,size=57126K
machine: pc-i440fx-10.0+pve1
memory: 2048
meta: creation-qemu=10.0.2,ctime=1758531291
name: hostname
net0: virtio=BC:24:11:12:34:56,bridge=vmbr0,link_down=1,tag=50
ostype: wxp
scsihw: virtio-scsi-single
smbios1: uuid=blablub
sockets: 2
vga: qxl
virtio0: poolname:vm-123-disk-0,cache=writeback,discard=on,iothread=1,size=41G
vmgenid: bla-blub-bla

I have one other winxp to port from esx to proxmox and will report back if anything additional is needed but for now I think it should be ok, to finally mark this thread as solved.

Thanks to all for your assistance and informations very appreciated.

Edit to add that for some reason it was the created copy by wim file that was better working than the rsync copy - meaning the rsync one I never get passed the phase where I could see a startmenu by booting normally, this only worked with the wim file copy.
 
Last edited: