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

Question

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

My teacher told me I should use gen2. That didn't work. I fixed the issue by using gen1. — PinkDraconian, Oct 23 '19 at 08:33
Switching to gen 1 worked for me when trying to install Win Server 2019. The below solutions did not for whatever reason. — Maximojo, Jun 03 '20 at 04:41
https://www.youtube.com/watch?v=4rmxMM_-2S0 . By Pressing Space and loading solved the problem. I kept the the video for your reference. — Am_official, Dec 14 '22 at 09:57

Matthew · Answer 1 · 2020-05-22T18:58:13.057

89

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"

edited May 22 '20 at 18:58

answered Mar 27 '20 at 16:33

Matthew

1,264
1
11
20

I couldn't figure out why my fresh HyperV wouldn't boot from my Debian ISO. Turning this off helped. Thanks! – eth0 Jun 05 '20 at 16:36
Microsoft has some pretty good details about what features are supported on various flavors of Linux and FreeBSD, and a note: Generation 2 virtual machines have secure boot enabled by default and some Linux virtual machines will not boot unless the secure boot option is disabled https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-debian-virtual-machines-on-hyper-v – Matthew Jun 20 '20 at 03:55
This is it! Should be accepted. Help me a lot! ThANKS – tim Mar 12 '21 at 14:12
This is a quick and dirty solution, if you are running a newer Linux distro that supports secure boot, take a look at some of the other answers that talk about using the "Microsoft UEFI certificate Authority" for secure boot. – Matthew Oct 05 '22 at 15:49

score 22 · Answer 2 · answered Jul 10 '21 at 06:43

22

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.

answered Jul 10 '21 at 06:43

CyberMonk

1,462
2
16
21

I had the same issue when trying to install Windows Server 2019 VM. This method solved it, but can anyone explain what happened and why it got resolved this way? – Xu Shaoyang Mar 24 '23 at 11:59

score 19 · Accepted Answer · answered Jan 21 '20 at 02:33

19

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.

answered Jan 21 '20 at 02:33

AlexVPerl

7,652
8
51
83

That cracked it, thanks – mayersdesign Dec 29 '21 at 14:15

izy · Answer 4 · 2022-04-29T02:15:23.533

12

Worked for me:

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

edited Apr 29 '22 at 02:15

answered Dec 21 '20 at 07:25

izy

1,085
14
18

1

Very good answer which I upvoted, indeed it's working even for new os or especially when you convert .ovf virtual machines to .vhd or .vhdx After aving exported a virtual machine from VMware for example. – LuckyFr Feb 26 '21 at 19:26

Bashash911 · Answer 5 · 2021-05-21T19:08:52.107

10

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.

edited May 21 '21 at 19:08

answered May 21 '21 at 08:27

Bashash911

121
1
5

1

Changing secure boot to use "Microsoft UEFI Certificate Authority" worked for me. I've installed Ubuntu Server, Generation 2 VM. – Kajsa Gauza Sep 17 '21 at 14:05
1

This answer (and MaxAlt's) should be the accepted one. Hyper-V gave 3 options for the secure boot template, and only choosing "Microsoft Windows" or "Microsoft UEFI Cert..." will Hyper-V say secure boot is enabled, and it seems only UEFI works for Linux (Works for Ubuntu 22.04) – Paul L Jul 19 '22 at 03:01

score 5 · Answer 6 · answered Nov 25 '20 at 07:22

5

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.

answered Nov 25 '20 at 07:22

MaxAlt

51
1
3

I used this approach to install RHEL 8 from a DVD ISO. – Richard Jessop Jan 06 '21 at 02:37
Worked for Ubuntu 20.04 too – Jay M Mar 27 '22 at 09:56

score 4 · Answer 7 · answered Jun 25 '21 at 14:38

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.

score 1 · Answer 8 · answered Sep 05 '22 at 10:42

1

In my case I left disabled the "Enable Secure Boot" flag and it worked pretty

answered Sep 05 '22 at 10:42

Diamantidis Charalampos

11
1

This works for me, thanks. – jojemapa Jul 08 '23 at 04:26

score 0 · Answer 9 · answered Feb 19 '23 at 23:40

0

Copying a vhdx image from a Windows Server 2012 R2 Hyper-V environment to Windows 10 Hyper-V, I had to create a Generation 1 VM. Generation 2 did NOT work. It booted without the PXE over IPV4 error then.

answered Feb 19 '23 at 23:40

Ron

1
2

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

9 Answers9