CODEWITHSUNDEEP
virtual-machinehyper-v
PinkDraconian
PinkDraconian

Reputation: 671

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

Upvotes: 53

Views: 106082

Answers (13)

Caltor
Caltor

Reputation: 2756

Change the Secure Boot template from "Microsoft Windows" to "Microsoft UEFI Certificate Authority" as per this screenshot

Screenshot of Secure Boot options

Upvotes: 0

BYTEASSOCIATE
BYTEASSOCIATE

Reputation: 1

Guys change the boot order in the select firmware tab and move the DVD image to up

Upvotes: -1

Dave Steggs
Dave Steggs

Reputation: 1

For a Gen2 VM to instal Windows 10/11 you neeed the following simple steps:

Assuming you have your ISO mounted in the virtual dvd drive...

  1. Right click your Gen2 VM in hyperV and select settings.

  2. Click the security tab and check the box "Enable Secure Boot" and "Enable Trusted Platform Module" then save your settings.

  3. Connect to the VM with it turned off. Press the power on button and then keep pressing your enter key as the Hyper-V boot screen appears until you boot into windows installer.

Now you are able to install Windows 11 on a Gen2 VM with secureboot and TPM enabled.

Upvotes: 0

LLucasAlday
LLucasAlday

Reputation: 2551

I tried every answer here, so what I did that ended up working is:

Create with New instead of Quick Create

Select Generation 2

Disable Secure Boot

Move boot from hard disk to the top

On the black screen with the "Start PXE..." message, I selected "Action -> ctrl-alt-del" from the Hyper-V menu bar.

This reset the screen and gave me time to press a key to boot from DVD.

Upvotes: 2

Ron
Ron

Reputation: 1

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.

Upvotes: 0

Diamantidis Charalampos
Diamantidis Charalampos

Reputation: 21

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

Upvotes: 2

izy
izy

Reputation: 1253

Worked for me:

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

Upvotes: 12

CyberMonk
CyberMonk

Reputation: 1622

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.

Upvotes: 37

Ehsan Mirsaeedi
Ehsan Mirsaeedi

Reputation: 7592

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.

enter image description here

Upvotes: 4

Bashash911
Bashash911

Reputation: 171

  • 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.

Upvotes: 15

MaxAlt
MaxAlt

Reputation: 69

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.

Upvotes: 6

Matthew
Matthew

Reputation: 1612

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"

VM Settings

Upvotes: 121

AlexVPerl
AlexVPerl

Reputation: 7996

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.

Upvotes: 23

Related Questions