'When trying to install OS in Hyper-V, it ignores boot order and goes to "Start PXE over IPv4" instantly

I'm trying to create a VM from an .iso file on my computer. In my boot order settings, the DVD Drive with as value the .iso is at the top. I've tried several different VM's (Ubuntu18.04, Windows 10 and Windows Server 2016) all of which give me the same problem where they don't boot from the .iso file. Pressing any key doesn't do anything.

I followed tutorials from both my lecturers and articles online when creating the VM's.

I am clueless as to what I'm doing wrong, so any help is appreciated

Black "Start PXE over IPv4 screen Error message when trying Windows 10 after the black "Start PXE over IPv4" screen Error message when trying Ubuntu after the black "Start PXE over IPv4" screen

virtual-machine hyper-v

Solution 1:^[1]

Just go into VM Settings / Firmware and change the boot order by moving the VHDX image to the top.

Changing to Generation 2 VM is not necessary.

Solution 2:^[2]

Try disabling Secure boot in the "Security" section of the settings.

I had the same problem with a gen2 Linux vm (running in Hyper-V Manager 10.0.17763.1). Turning off "Enable Secure Boot" allowed booting from an .iso. I think in some other versions of Hyper-V Manager the setting is under "Firmware"

Solution 3:^[3]

This occurred when I was trying to boot from a Win 10 ISO. After the "Press any key to Boot from DVD..." message displays, it jumps almost immediately to trying to boot from the network (PXE over IPv4). The solution for me was to select 'Reset' from the Hyper-V menu and then immediately start hitting a key before the message showed up.

Solution 4:^[4]

Worked for me:

Create a new VM.
A "New Virtual Machine Wizard" will start.
During step 3 - "Specify Generation", choose "Generation 1"

Solution 5:^[5]

When using Windows10 - moving the VHDX to the top Boot order was the solution in my case.
When using Linux - Changing secure boot to use "Microsoft UEFI Certificate Authority" was the solution. I tested CentOS_Stream & Mint - same problem, same solution.

Solution 6:^[6]

I left enabled "Enable Secure Boot" flag, but selected a different template: from "Microsoft Windows" to "Microsoft UEFI certificate Authority" for my Centos 7 distribution hosted by Windows 10. This tells the UEFI is needed for Linux installation.

Solution 7:^[7]

The only solution in my case was to re-create the VM in Generation 1. Changing the boor order or disabling Secure Boot did not resolved the issue at all.

It seems "Quick Create" creates VM in Generation 2 by default. You have to Go with "New" instead of "Quick Create" to choose Generation 1.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	AlexVPerl
Solution 2
Solution 3	CyberMonk
Solution 4
Solution 5
Solution 6	MaxAlt
Solution 7	Ehsan Mirsaeedi

'When trying to install OS in Hyper-V, it ignores boot order and goes to "Start PXE over IPv4" instantly

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]