Hyper-V prevented starting virtual machine because it is prepared for failover

I don't think anyone has been answered you yet because it is difficult to truly grasp the meaning of your question.

That said, the best practice on Hyper-V is to reserve one NIC as a "Management Adapter." This NIC will be configured just like any other regular NIC on any other physical host on your network, and you do not use it as a Hyper-V adapter that your VMs or HyperV Virtual Switch will use.

Then use another separate adapter to dedicate to the HyperV Virtual Switch. I would recommend not setting DNS servers or a default gateway on this NIC. This NIC simply needs to provide physical network access to your VMs. Creating an external Virtual Switch is what you want to do if you want your VMs to be able to communicate with the rest of the world.

Then connect your VMs to that virtual switch, give them a full IP stack as if they were regular physical hosts on your network, and go!

If you want those VMs to host services, you will then need to configure your NAT'ing router to forward ports to those internal VMs.

I found this problem myself while adding certain VHKD files to new and existing Hyper-V virtual machines, I never really dug around that much as I have experience loads of problems adding virtual hard disks to Hyper-V unless they were VHD format.

This is more of a work around than a solution, but it may help you; I downloaded this tool

http://download.softwaretipspalace.com/Windows/System-Utilities/Other/V2V-convertertion-tool_7728.html

Which is completely free! It allows you to take a VHKD and convert it to a VHD! It doesnt take that long either, I would imagine it would work after doing this.