VHDX file created by sysinternals Disk2VHD cannot be imported into Hyp

I used sysinternals disk2vhd64.exe (newly downloaded) to create a VHDX VM. The source system is 64-bit Windows 10 machine.



However, Hyper-V can't find this VM when I select the proper directory. My system is Win 10 Pro 64.


What did I do wrong? I have done a lot of web searching and can't find an answer.

x509 said:

I used sysinternals disk2vhd64.exe (newly downloaded) to create a VHDX VM. The source system is 64-bit Windows 10 machine.
However, Hyper-V can't find this VM when I select the proper directory.... What did I do wrong?

The VHD and VHDX formats are different formats. The file you created with disk2vhd64.exe is in VHD format, despite you giving it a .vhdx extension. That is why Hyper-V Manager doesn't recognise it as a valid .vhdx file.

Disk2vhd is a utility that creates VHD (Virtual Hard Disk - Microsoft's Virtual Machine disk format) versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual machines...

https://docs.microsoft.com/en-us/sys...loads/disk2vhd


You have two choices, for both you'll first have to rename it with a .vhd extension. You can then use the .vhd in the VM, or if you need a .vhdx use 'Edit disk..' in the Hyper-V Manager to convert it to a .vhdx disk before using it in the VM. The VHD format is a legacy format, the better choice would be to convert to VHDX.

Microsoft said:

Hyper-V in Windows Server 2012 introduces a new version of the VHD format called VHDX, which is designed to handle current and future workloads.
VHDX has a much larger storage capacity than the older VHD format. It also provides data corruption protection during power failures and optimizes structural alignments of dynamic and differencing disks to prevent performance degradation on new, large-sector physical disks.

https://docs.microsoft.com/en-us/pre...31446(v=ws.11)

Bree said:

The VHD and VHDX formats are different formats. The file you created with disk2vhd64.exe is in VHD format, despite you giving it a .vhdx extension. That is why Hyper-V Manager doesn't recognise it as a valid .vhdx file.

https://docs.microsoft.com/en-us/sys...loads/disk2vhd


You have two choices, for both you'll first have to rename it with a .vhd extension. You can then use the .vhd in the VM, or if you need a .vhdx use 'Edit disk..' in the Hyper-V Manager to convert it to a .vhdx disk before using it in the VM. The VHD format is a legacy format, the better choice would be to convert to VHDX.

https://docs.microsoft.com/en-us/pre...31446(v=ws.11)

@Bree

Thanks for this reply. I have never needed to use a VM until now. It is a great opportunity to learn some new technology.

I find it easier just to create a blank vhdx on my data drive (E), and clone OS drive (C) iusing Macrium Reflect than using disk2vhd as you have more control over size of vhdx file.

The vhdx file only needs to be large enough to hold all progs plus existing C data. Rough rule of thumb make vhdx twice size of stored info on C drive.

So my C drive is 250 GB but only holds around 50 GB. I make vhdx maximum 2x50 = 100 GB. My second drive is 1 TB.

Important point is you need at least nominal max size of vhd spare (100 GB in this example) plus another 20 GB for temporary files i.e. 120 GB spare to run vhdx file.

Problem with disk2vhd is the vhds are too big as they get sized to whole drive.

x509 said:

What did I do wrong? I have done a lot of web searching and can't find an answer.

See the tutorial, it might help you to make the VM: Hyper-V - Create and Use VHD of Windows 10 with Disk2VHD

Kari