[SOLVED] P2V Windows XP 0x7B error

[vescovialex]

Hi,

Yesterday, I found an old HDD containing a Windows XP Pro installation. I attempted to virtualize it, but unfortunately, I haven't been successful.

I create the qcow2 file with Disk2VHD program, I've tried 3 ways. The first create a vhdx file, the second with vhd and third vdh with the flag "Prepare for use in Virtual PC". For all this three images I've tried the solution here down described.

Here's what I've tried:

• Without MergeIDE.reg: As expected, this resulted in a blue screen of death (BSOD).
• Using Hirens BootCD and MergeIDE.reg:
  • I loaded the hive from my old HDD into regedit.
  • I applied the MergeIDE.reg file, but encountered another BSOD.
  • I noticed that the MergeIDE.reg file writes to CurrentControlSet, which doesn't exist in my registry. Instead, I have ControlSet0001 and ControlSet0002.
  • I modified the MergeIDE.reg to target ControlSet0001 first, leading to a BSOD. Similarly, targeting ControlSet0002 also resulted in a BSOD, both with the same error code 0x7B.
  • I tried with a Win XP CD a repair with fixboot, bootreg and this stuff.
  • I explored the internet, and although the most commonly suggested solution is the MergeIDE.reg file, it hasn't worked for me.

Have you any other suggestions?

Thanks

 

[Wh1teWolf]

I have similar situation but with 2008R2std. I created vhdx file and imported into vm. Maybe mergeide need to be added to physical machine before creating vhdx file?

 

[_gabriel]

MergeIDE need to be executed under running system before capture disk2vhd.
"apply" offline can be possible under WinPE like Hiren but need some work , out of scope of the forum.
You need to dig, like Load hive from Regedit + update the .reg to "search and replace paths".
This Windows problem always existed before virtualization ...

 

[vescovialex]

I have similar situation but with 2008R2std. I created vhdx file and imported into vm. Maybe mergeide need to be added to physical machine before creating vhdx file?

I've resolve this in a very simple way. I hope that for you will be the same.

Start a Hiren's CD version 15.1, search in Hiren's programs the fix_hdc.cmd, start it, give them the Windows path. And the script do the magic.

After the restart my VM started perfectly.

 

[SourishCreature]

I've resolve this in a very simple way. I hope that for you will be the same.

Start a Hiren's CD version 15.1, search in Hiren's programs the fix_hdc.cmd, start it, give them the Windows path. And the script do the magic.

After the restart my VM started perfectly.

Thanks - this worked for me on an XP VM transferring over from VMWare Workstation Pro via OVF export

 

[Adamg]

OMG! I can't believe this worked like a charm!!!

I've resolve this in a very simple way. I hope that for you will be the same.

Start a Hiren's CD version 15.1, search in Hiren's programs the fix_hdc.cmd, start it, give them the Windows path. And the script do the magic.

After the restart my VM started perfectly.

THANKS A MILLION @vescovialex

For anyone else that stumbles into this post, I was able to get a Windows XP drive from a dead machine to boot as a proxmox VM easily using this method above.

I made a full disk image of the drive from the dead machine, using the dd command in linux.

I made a new proxmox VM, set it as Windows XP during setup which set the drive as an IDE drive and the NIC to be a Realtec device, which was fine.

I used dd in linux to copy the disk image to the new blank IDE drive for this VM

It of course went to Blue Screen on every boot attempt.

So, I downloaded the "Hiren's CD version 15.1" ISO and booted the VM to it.

I selected the 2nd option from the list: "Mini Windows Xp" and that booted into a Windows XP PE environment.

Then I selected "HBCD Menu" (shortcut on the desktop)

The "Hiren's BootCD 15.1 - Program Launcher" window appears

Click the "Browse Folder" button

That opened file explorer to the folder:

D:\HBCD\Programs (which has a bunch of .cmd files in it)

Go down and run the file "FixHDC.cmd"

That opened a command window with 2 options:

T to set TargetRoot (which in my case I set it to c:\windows)
M to Update MassStorage Drivers (which ran fine after setting the target)

It completed and I rebooted the VM and it went into Windows XP just fine!!!

AMAZING!