Recently I was attempting to replace the operating disk in one of my Hyper-V hosts in my home datacenter.
During that operation, I intended to migrate from a rather small SSD drive, to a mirrored set of 1 TB SATA SSD drives left over from an older storage server.
My guess was I could easily setup an operating system partition mirror to one of the new SSD’s, than remove the original SSD drive from the mirror and replace that drive with the second 1 TB and included it as a mirror. Unfortunately, I selected the C partition for the mirror operation, converting the disks to dynamic and excluding the two small recovery and EFI system partitions, rendering the system unbootable.
It took me quite a while to recover the OS partition from the original disk, converting it back to basic etc. Long story short, I got the OS booting again after fiddling a lot with Hirens BootCD tools and the Server 2019 recovery tools.
The server booted normally, everything seemed to work, except, I was unable to move the VM’s from my secondary hyper-v server, claiming incompatible hardware, while both servers use identical components.
Error message:
“The Virtual Machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine”
I tried to move one of the VM’s in a powered off state. The move operation now is successful, but I cannot start the VM with the message:
“The Virtual Machine could not start because the hypervisor is not running”
Services however are running normally. When checking for additional info, I found information about DEP being disabled etc. That however was not the case.
The cause of the issue was the rebuild of the bcd boot configuration during the recovery of the system partition.
When running bcdedit on a command prompt on both the recovered and still running hyper-v host and comparing the entries, it showed this line was missing:
hypervisorlaunchtype AutoThis can easily be added using the command:
bcdedit /set hypervisorlaunchtype AutoReboot the system, and Hyper-V is running again!
Leo's blog 