A Hyper-V Generation 2 VM is similar to a workstation running a UEFI workstation and as such cannot communicate with legacy PXE, but with UEFI boot images. See the following guide on how to set up a Generation 2 VM via PXE boot, how to set up a Generation 1VM via PXE boot, and how to set up a VM via PXE boot on a Generation 2 VM, how to deploy images to computers or virtual machines using WDS, and Windows deployment cannot continue, the operating system is missing via MDT deployment. A VM configured with UEFI will use bootx64wdsmgfw.efi on the WDS server when starting the boot process while a legacy boot will use bootx64wdsnbp.com.

Hyper-V specifically provides hardware virtualization. That means each virtual machine runs on virtual hardware. Hyper-V lets you create virtual hard drives, virtual switches, and a number of other virtual devices all of which can be added to virtual machines.

If your network is configured to deploy boot images using legacy methods, this will require you to configure the hardware of the virtual machine. See the link for how this is done. See the following link for more details. Here are some similar VM errors, the virtual machine has terminated unexpectedly during startup with exit code 1 (1×0), and Windows failed to start, a recent hardware or software change might be the cause.

I welcome you to subscribe to my YouTube Channel. I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.