Share via

VM does not Boot Following P2V or Disk2VHD

  • Article

So you perform a successful P2V using SCVMM. Or perhaps you use it’s cousin, ‘Disk2VHD’ from Sysinternals. All is well until you boot the new VM… FAILURE. For those situations where you simply get a black screen, maybe with a blinking cursor but definitely no Windows load, I have some solutions. (If you are experiencing a blue screen this article is not for you).

First! Do not fear the black screen. It simply means the path to load Windows cannot be found by the boot loader. This may be due to the boot loader, or it may be due to the MBR or Boot Sector. Let’s just say we aren’t concerned with all of the technicalities and want to fix it. Here’s how.

 

 

Windows 2008 R2 (Vista, Windows 7, Windows 2008)

We’re going to fix the entire boot path, despite what part of it is broken. Go find an ISO or DVD of any of the operating systems just listed in the title. Prepare to boot your VM from this media. We’re going to use the recovery console. We’ll assume you are using Windows 7 media.

  1. Attach the Windows 7 installation disc to the virtual machine disc drive, and then start the computer.
  2. Press a key when you are prompted.
  3. Select a language, a time, a currency, a keyboard or an input method, and then click Next.
  4. Click Repair your computer.
  5. Click the operating system that you want to repair, and then click Next.
  6. In the System Recovery Options dialog box, click Command Prompt.
    1. If an operating system is not found simply continue anyway
  7. Type the following command in this order to set your system straight:
    1. bootrec /fixmbr    (Fixes MBR)
    2. bootrec /fixboot   (Fixes Boot Sector)
    3. bootrec /scanos    (Scans for Windows installations to add)
    4. Reboot! (Type Exit)
  8. If you still do not boot into Windows, or do not have a boot menu, or something is still wrong, follow steps 1 – 6 again. For step 7 type this instead
    1. bootrec /rebuildbcd    (Rebuilds entire BCD… not a really big deal)
    2. Reboot! (type Exit)

You are now either booting into Windows, or you are not… Any blue screens I cannot help you with at this time. Search the internet for a solution, and in the meantime I intend to write an article on this as well. Comments welcome as always.

Further Information:

How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows
https://support.microsoft.com/kb/927392

Windows 2003 R2 (Windows XP, Windows 2003)

Again, we’re off to fix the boot path. Things are a bit different in Windows 2003. Same basic goal as with Windows 2008. Go find an ISO or DVD of any of the operating systems just listed in the title. Prepare to boot your VM from this media. We’re going to use the recovery console. We’ll assume you are using Windows 2003 media.

  1. Attach the Windows 2003 installation disc to the virtual machine disc drive, and then start the computer.
  2. When you receive the message that prompts you to press any key to start from the CD, press a key to start the computer from the Windows Server 2003 CD.
  3. When the Welcome to Setup screen appears, press the R key to start the Recovery Console.
  4. Select the Windows installation that you must access from the Recovery Console.
  5. Follow the instructions that appear on the screen, type the Administrator password, and then press ENTER.
  6. Type the following command in this order to set your system straight:
      1. fixmbr (Fixes MBR)
      2. fixboot (Fixes Boot Sector)
      3. bootcfg /rebuild  (Lists all Windows installations that you can add)
      4. Reboot! (type Exit)

You are now either booting into Windows, or you are not… Any blue screens I cannot help you with at this time. Search the internet for a solution, and in the meantime I intend to write an article on this as well. Comments welcome as always.

Further Information

How To Use the Recovery Console on a Windows Server 2003-Based Computer That Does Not Start
https://support.microsoft.com/kb/326215

Description of the Windows XP Recovery Console for advanced users
https://support.microsoft.com/kb/314058

 

 

jonjor

Comments

  • Anonymous
    January 01, 2003
    This worked great! Thanks!

  • Anonymous
    January 01, 2003
    thank you

  • Anonymous
    January 01, 2003
    Changing the drive letters didn't help. In fact diskpart wouldn't let me change the correct partition to the C: drive. Anyway, it turns out that my problem was caused by exporting the original system as two separate VHDs. Rather than letting the Disk2VHD program just do it's thing. Rookie mistake :)

  • Anonymous
    June 11, 2013
    Top Banana! Thank you!

  • Anonymous
    September 18, 2013
    Nice One... Thanks