VHD not start after disk2vhd RRS feed

  • Question

  • Hi everybody!

    I wish to virtualize Windows Server 2008R2 (IBM 7947K6G System x3650 M2 и WinServer 2008R2) via disk2vhd v1.63 (just disk С). All is ok and after progress I have a VHD file.

    I copy this VHD to new location and attach it to fresh created VM (Hyper-V 2012). 

    After I try to start this new VM I see black screen and blinking white cursor on left upper left corner. That's it!

    I've tried lots of ways to solve the problem:

    1. I try to boot from different ERD and DART, they all say that the this version is NOT compatible with your system (and they are certainly working on dozens of previous servers).

    2. I try to boot from the installation image of WinServer (from this iso I install this system before) when attempting to enter the recovery mode it is displays a message similar to paragraph 1.

    3. I tyr to boot from different LiveCD (3rd party), there I see what this VHD really has a working system (drive C has a NTFS partition and another section in RAW format plus one part in fat32. They both 100 mb, but the C drive partition is not marked as active).

    4. I try via Diskpart make C drive active, and I get error that it is can not be made ​​active GPT to MBR. I tried to make convert MBR, and I got an error that this type of disc can not be converted to MBR.

    5. Tried to virtualize this server using MS SCVMM 2012. But agent is not start on the target physical server (but that's another story.)

    I have investigation via internet and I understood that the problem is faced with the fact that my physical server have uEFI and Hyper-V have BIOS. But I havent found any proof that this is my problem.
    At this point, the server successfully migrated to a new virtual machine (data transferred using standard tools and wizards), so the problem is not so urgent.

    Just for the future, I would like to find out why the VHD does not start correctly (VHD to the C drive I have so I can make some tests now)?

    ps http://social.technet.microsoft.com/Forums/ru-RU/virtualizationru/thread/a31151f9-1afc-4b9b-b106-f408cc7e2f37/

    Friday, January 4, 2013 7:49 AM


All replies

  • This may be a UEFI related issue, alright:


    Is the partition in the physical machine GPT?

    A bit of searching found an older post/solution with a similar scenario: http://social.technet.microsoft.com/Forums/en/winserverhyperv/thread/e174cb81-a152-4144-b59d-94ebbc8a7566
    Friday, January 4, 2013 10:16 AM
  • I already try bouth this ways from http://social.technet.microsoft.com/Forums/en/winserverhyperv/thread/e174cb81-a152-4144-b59d-94ebbc8a7566 but it is not work for me.

    Anyway I found this http://blogs.technet.com/b/jonjor/archive/2011/10/27/p2v-fails-with-gpt-disk-using-efi-boot.aspx

    So it is looks like what I can not use p2v or disk2vhd to virtulize and sucessfully run after that my servers. Better will use migration to new clean installation.

    I would be glad if I'm wrong, and someone can correct me.

    • Edited by AlexunderG Friday, January 4, 2013 1:11 PM
    • Marked as answer by AlexunderG Sunday, January 6, 2013 7:16 AM
    Friday, January 4, 2013 1:09 PM
  • Yes, you cannot just flip between UEFI and non-UEFI.  It won't work, your OS won't boot. (you should see the same result on the physical box if you turn off UEFI in the BIOS).

    The only way that I have overcome this is to re-install. 

    Or, back in the olden days we would install a new OS in the VM (matching the original) and use Windows Backup to backup the original and then restore to the new install on new hardware.

    Brian Ehlert
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    • Marked as answer by AlexunderG Sunday, January 6, 2013 7:13 AM
    Friday, January 4, 2013 4:15 PM
  • Thx a lot for your answers! Right now it is clear for me.
    Sunday, January 6, 2013 7:13 AM

  • I created a You Tube video to walk you through the steps. You don't have to format or restore from backup.


    Saturday, November 22, 2014 8:28 PM
  • Great video and tutorial.

    Wednesday, March 11, 2015 3:03 PM
  • This is actually doable since Windows 8.1/2012r2
    You need a couple of things:

    1) Disk2VHD must create VHDX files rather than VHD

    2) When creating you VM, you must create a Gen 2 VM

    3) After creating the VM you'll need to re-create the boot partition using WinPE (This is not tough, just a few steps are necessary and a Windows Media with the VM's OS or later in physical or ISO form).

    To re-create the boot partition follow these steps (taken from this article:  https://blog.workinghardinit.work/2016/09/08/disk2vhd-on-a-generation-2-vm-results-in-an-unbootable-vhdx/)

    A) Boot the VM to WinPE on the Windows Media - You'll need to create a DVD object in your VM by selecting the SCSI controller in the VM settings and adding a new DVD Drive, then either attach the .ISO or the physical drive with your boot media to that.  Once this is done you can boot the VM, hit a key when prompted to boot to the DVD.  

    B) Go to a Command Prompt Once you have the Language window up, hit Shift-F10, or click Next, then 'Repair My Computer', then 'Troubleshoot', 'Advanced', and 'Command Prompt'.  Both will get you to a Command Prompt.

    C) Open Diskpart tool (careful in here...) At the command prompt, type "Diskpart" and hit Enter

    D) Run Diskpart Commands:

    List Disk (This will show you the drives, most likely there is only one, but either way, you need to select the boot drive with the next command)

    Select Disk 0 (If you have multiple drives, this could be a different disk - you want the boot drive)

    List Vol (this will list the volumes in the same manner as List Disk did the discs) Here, you should see your volumes, but your actual boot volume (not your System Volume, just where your Boot Configuration sits) will show up as "RAW".  Note the Volume Number of this RAW volume.

    Select Vol 3 (this is assuming that RAW Volume is 3 - use your actual volume number)

    assign drive letter L: (This makes the volume visible with a drive letter - we are using L: - this is temporary and only really matters during this Boot session)

    FORMAT FS=FAT32 LABEL=”BOOT” (This will format the Volume and ready it to receive a new Boot Partition.  It also names the volume "BOOT")

    Exit (This gets you out of Diskpart)

    E) Switch to Boot Volume and Create the Boot Folder Structure with these commands 

    md L:\efi
    md L:\efi\Microsoft
    md L:\efi\Microsoft\Boot

    F) Create Bootrecord and Boot Files with these commands

    bootrec /fixboot
    bcdboot C:\Windows  /l en-us /s l: /f ALL

    This creates the BCD store & copies the boot files from the windows system directory

    At this point, you can exit the command prompt and restart the VM to the Operating System on the disk.

    • Proposed as answer by RobC_CTL Thursday, November 8, 2018 6:44 PM
    Wednesday, March 21, 2018 5:06 PM