StarWind Software

I have used StartWind converter for long time. This is the first time I got problem. I converted a VHDX file into VMDK. The VMDK is unbootable. Here is my environment

Hyper-V host is Windows 10 Pro version 1607 with OS Build 14393.953
The VM on Hyper-V is Generation 2 with configuration version 8.0

StartWind runs directly on this Hyper-V host.

Use Hyper-V to convert VHDX to VHD, and then use StartWind to convert VHD to VMDK. The VMDK still unbootable.

The StarWind is downloaded today 3/24/2017 from StarWind website.

Thanks for any advice

During conversion you need to make sure you've checked "Repair OS" checkbox to trigger storage and network stack rebuilds to match new hardware (VMware and Microsoft have very different set of the emulated hardware). If you didn't do that hardware will stay the same and virtual machine won't boot.

Thank you, Anton. The option is greyed out and not available. The choice for VMDK is "Growable image" and SCSI.

Anton,

The StarWind converter works just fine. The problem was that I picked BIOS rather than UEFI when creating VMWare machine.

Thank you for your help!

Peter

Hello Peter555,

Thank you for updating us about the solution.

Hi im having similar issue where i convert .vhdx to .vmdk, but when i boot up in my VMware Esxi it say no OS found. i check the .vhdx file and i can confirm my windows server 2012 R2 OS file does exist. i mount the .vhdx file into my laptop and all system file is intact.

i try change the BIOS to EFI but it is still the same, there is no OS to boot.

FYI, the .vhdx file is from the WBadmin backup that i setup and backup into an external HD using the following command:

wbadmin start backup -backupTarget:\\192.168.1.5\ABC123_Backup\Today -allcritical -include:c: -quiet -user:YouSHallNotPass -password:YouSHallNotPass

Have you tested your vhdx file by creating a Hyper-V VM?

Hello kokfai,
Please let us know if Peter's advice helped.
Thank you!

thank you Peter, you helped me alot.

Update: You need to boot your freshly converted Windows-based VM into so-called "Maintenance Mode", Windows will rebuild drivers stacks matching new emulated hardware and... After another reboot everything will go normal!