Skip to main content

Support for deployment to Hyper-V Gen 2?

Thread needs solution
Posts: 1
Comments: 2

Hi Everyone!

I've got an existing disk image made with Snap Deploy 5 that I'd like to deploy to a Hyper-V virtual machine to test a few things. I'm using the Hyper-V feature on Windows 10 Pro and created the VM as Gen 2 so I can use UEFI (image was initially made from a UEFI system).

The trouble is when I boot the VM using the bootable media ISO (1780 or 1877) the local disk is not detected. As a sanity check I booted the same VM from a Windows 10 ISO and Windows Setup can see the disk just fine (installs Windows fine as well).

Am I missing something or is it just not supported to deploy images to a Hyper-V Gen 2 VM?


0 Users found this helpful
Forum Support specialist
Posts: 0
Comments: 1982

Hello, Lowly.

Have you tried to boot your Hyper-V VM with WinPE-based bootable media? You can use the latest Windows ADK versions for Windows 10 (1703, 1803, and 1809) to create WinPE-based bootable media with the Acronis Snap Deploy 5 PE Builder wizard (with new build #1877).

Otherwise, we recommend that you contact Acronis Support Team and provide them with system information collected under Acronis Bootable Media created with the build #1877 in order to investigate the reason why it does not see the local drive.

Forum Member
Posts: 5
Comments: 25

I can confirm that using the WinPE based boot media works in HyperV.

We are using a Gen2 VM with UEFI based booting as well. 

Posts: 1
Comments: 2

Thanks for the suggestion Maria! I built a PE image following the instructions and it does work!

Couple of things to note for future folks that may arrive here:

  1. Hyper-V failed to boot automatically from the mounted ISO but it does work when selecting the SCSI DVD device from the boot menu.
  2. Loading an image from a network share felt very clunky:
    1. The interface to enter network credentials is a command line window that sort of pretends to be a modal window. You need to tab through the "fields" and "buttons".
    2. The network paths never updated in the expanding folder list; I had to use the image path field "hint" feature to muddle my way to the image.