I need a Hyper-V machine to run a win10 32 bits machine on a win10 64 bits pro I uploaded an official win10 32 bits .iso I created an Hyper V using this .iso. Everything went smoothly. I started the machine as requested. Then it repeatedly stops on: start PXE over IPV4 then Microsoft Hyper-V UEFI Virtual machine boot summary SCSI DVD (0,1) the boot loader did not load an OS SCSI disk (0,0) the boot loader did not load an OS Network adapter (00155D004E00) a boot image was not found No OS was loaded. Your virtual machine may be configured incorrectly. Exit and reconfigure your VM or click to retry the current boot sequence again." The VM does not see the .iso or the .iso has not the right format or something is wrong in the VM configuration or...??? In fact it does that on both my Surface Pro 7 and PC Both machines satisfy Hyper-V Requirements. Would you know what should be changed? Thanks a lot for your help

You might also try creating it as a Gen1 since its a 32 bit instance. Hyper-V Gen2 does not support 32 bit UEFI. You will need to create the Windows 10 32 bit guest as Gen1. --please don't forget to Accept as answer if the reply is helpful--

We have experienced this on 64 bit systems too (we never use 32bit). It appears that the boot loader will present the PXE message, and even if you click inside Hyper-V and press space to boot from the CD (ISO) it will ignore you. However, if you * press 'reset' in the tool bar * as soon as the black screen appears, click in the black screen and press space You have to be super super quick, it will then boot from the ISO image. This issue has been there for a few years now, and I'm surprised it's not fixed. @Lance Johnson - You may like this info If you're interested, I have catalogued a number of Hyper-V issues and solutions on my terribly ugly blog. https://gilesey.wordpress.com/tag/hyperv/

FWIW, I just ran into this issue trying to install Ubuntu Budgie 21.04 on Hyper-V. Found this by searching the PXE message. @Giles Middleton , your solution didn't work for me but I ended up looking at the VM settings, and realising that Secure Boot was enabled - disabled it, and voila! booted like a charm. hope it helps someone in the future!

Patrick, you are a genius! You made me discover that there was VM generations and you are right Gen2 does not support 32 bits instances. 3 months of trying with MS support....

created Hyper-V machine - does not boot

janloune 46

I need a Hyper-V machine to run a win10 32 bits machine on a win10 64 bits pro
I uploaded an official win10 32 bits .iso
I created an Hyper V using this .iso. Everything went smoothly.
I started the machine as requested.
Then it repeatedly stops on:
start PXE over IPV4
then
Microsoft Hyper-V UEFI
Virtual machine boot summary

SCSI DVD (0,1) the boot loader did not load an OS
SCSI disk (0,0) the boot loader did not load an OS
Network adapter (00155D004E00) a boot image was not found

No OS was loaded. Your virtual machine may be configured incorrectly.
Exit and reconfigure your VM or click to retry the current boot sequence again."

The VM does not see the .iso or the .iso has not the right format or something is wrong in the VM configuration or...???
In fact it does that on both my Surface Pro 7 and PC
Both machines satisfy Hyper-V Requirements.
Would you know what should be changed?
Thanks a lot for your help

harsha irugu 1 Reputation point

2022-12-04T16:20:10.137+00:00

Hey, I got the same issue recently when I tried. The thing is, you must click on "more options" in bottom and give network adapter as Default and Voila!
Michel LAPLANE (MVP Visio) 0 Reputation points MVP

2024-01-15T18:07:57.5333333+00:00

You save my life. Works great

Accepted answer

Dave Patrick 426K Reputation points MVP

2020-07-18T14:27:47.1+00:00

You might also try creating it as a Gen1 since its a 32 bit instance. Hyper-V Gen2 does not support 32 bit UEFI. You will need to create the Windows 10 32 bit guest as Gen1.

--please don't forget to Accept as answer if the reply is helpful--
Please sign in to rate this answer.

5 people found this answer helpful.
X H 1 Reputation point

2020-11-16T03:13:18.427+00:00

Great. It worked for me.

Lance Johnson 6 Reputation points

2020-12-03T15:24:40.14+00:00

So what if I get that message and I'm not using a 32-bit system. I am remoting into the host that I am using to create the VM (as I live in the rurals and my internet is abysmal and can't do what I need it to, so my server is elsewhere), and it has a notice at the top to "Press any key to boot from CD ..." but no key press is recognized as far as I can tell. It then faults into the exact same screen as the janloune-6508 described where I again can not select the "RESTART" option with mouse or keyboard. I don't run 32-bit anywhere, so I know it's a 64-bit .iso ... but I can't do anything, I found this thread trying to find a way to "Start PXE over IPV4". My theory is that it won't push the keyboard to the Gen-2 Guest System when I am remoted into the host ... but it maybe it's something different. Figured I would ask.
Sign in to comment

5 additional answers

Giles Middleton 221 Reputation points

2021-08-12T15:26:43.627+00:00

We have experienced this on 64 bit systems too (we never use 32bit).
It appears that the boot loader will present the PXE message, and even if you click inside Hyper-V and press space to boot from the CD (ISO) it will ignore you.

However, if you
* press 'reset' in the tool bar
* as soon as the black screen appears, click in the black screen and press space

You have to be super super quick, it will then boot from the ISO image.

This issue has been there for a few years now, and I'm surprised it's not fixed.
@Lance Johnson - You may like this info

If you're interested, I have catalogued a number of Hyper-V issues and solutions on my terribly ugly blog. https://gilesey.wordpress.com/tag/hyperv/
Please sign in to rate this answer.

40 people found this answer helpful.
Stephen Yates 11 Reputation points

2021-08-21T10:58:45.74+00:00

Brilliant - thanks for info. I've been tearing my hair out (I can't afford to loose any!!)

Paul Lenehan 6 Reputation points

2021-08-24T05:06:13.783+00:00

awesome worked for me

MadMan 6 Reputation points

2021-09-03T09:25:54.41+00:00

Thank you @Giles Middleton , I was looking for a solution for a similar problem, although the message I was getting was a bit different:

Virtual machine boot summary.

SCSI DVD (0,1) the boot loader failed.

Network adapter (00155DFC6907) a boot image was not found.

SCSI disk (0,0) the boot loader did not load an OS. No OS was loaded. Your virtual machine may be configured incorrectly.

Regardless, your suggestion allowed me to push through. Thank you so much.

A.M. Sabuncu 31 Reputation points

2021-10-01T10:26:56.187+00:00

A huge THANK YOU! This solved it for me.

IT Admins 6 Reputation points

2021-10-05T16:47:51.727+00:00

IThanks! This is what did it for us.

Fan Zhang 6 Reputation points

2021-10-11T09:04:13.377+00:00

Thank you!!!!!!!!!!!!!!!!!!!

anon221 6 Reputation points

2021-10-22T16:43:31.183+00:00

You are a genius mate. worked like a charm !

Dung Chu 6 Reputation points

2021-10-24T11:11:22.717+00:00

it work for me.. thanks

Ermin Rašitović 6 Reputation points

2021-11-15T03:27:15.387+00:00

Thank you

Stefani Clark 6 Reputation points

2022-01-03T18:09:57.293+00:00

Thank you SO MUCH, I was stumped by this. This is the FIX!!

greatly appreciate you sharing!

tigre

Aditya Padisala 6 Reputation points

2022-01-17T02:26:17.86+00:00

This worked. Thanks

Giles Middleton 221 Reputation points

2022-01-24T09:32:53.59+00:00

Thank you. It is the craziest of solutions is it not? I came up with it all by myself too. Maybe my years of creating strange bugs in software lead me to this career pinnacle.

Jason Phillip Bonn 1 Reputation point

2022-02-14T05:45:35.393+00:00

Thank you. Solved it for me on a WinServ2019 install.

IT_Guy 1 Reputation point

2022-03-03T20:17:33.407+00:00

this worked for me. it loaded into the windows setup.

Tanto Widjaya 1 Reputation point

2022-03-31T05:31:47.743+00:00

Brilliant. I was very helpful with the information. Thank you very much.

Martin 1 Reputation point

2022-04-25T09:16:23.397+00:00

Works like a charm. THANKS! :)

Lucid Dreamer 5 Reputation points

2023-02-24T16:49:18.1966667+00:00

Thank you so much, 2023 and this bug still persists :)

Pétuel Placide 0 Reputation points

2023-04-09T23:33:30.86+00:00

This option works for me.

fmcasado 0 Reputation points

2023-06-10T05:17:51.3933333+00:00

Pressing Reset and Space on Black Screen did the trick.

Raphael 0 Reputation points

2023-07-26T12:18:10.9066667+00:00

Space bar tricks worked!

Jacob Drury 0 Reputation points

2023-10-22T11:41:05.07+00:00

I was wondering why Gen2 didn't work with my x64-bit ISO.

I tried your solution (quoted below), and it worked! Thank you.

* press 'reset' in the tool bar
* as soon as the black screen appears, click in the black screen and press space

Mark Costa 0 Reputation points

2023-11-08T13:03:58.3866667+00:00

This should be the accepted answer, thanks!

Patrick Kuehn 0 Reputation points

2023-12-07T15:30:51.41+00:00

Giles, You da man. That worked like a champ

Anielka Oliveros 105 Reputation points

2024-01-03T19:11:52.9466667+00:00

Crack!!!! Thanks
Sign in to comment
Anthony Bush 16 Reputation points

2021-08-19T03:05:48.66+00:00

FWIW, I just ran into this issue trying to install Ubuntu Budgie 21.04 on Hyper-V. Found this by searching the PXE message. @Giles Middleton , your solution didn't work for me but I ended up looking at the VM settings, and realising that Secure Boot was enabled - disabled it, and voila! booted like a charm. hope it helps someone in the future!
Please sign in to rate this answer.

3 people found this answer helpful.
John Tony 6 Reputation points

2021-11-01T10:28:07.453+00:00

Thank you so much! I was trying to install Ubuntu 20.04 and I got this PXE message too. Turning off Secure Boot fixed it for me.

ObiEmmaTK 1 Reputation point

2022-01-06T14:11:15.827+00:00

That worked for me.

BobHLiton 1 Reputation point

2022-02-21T16:47:14.953+00:00

Thank you, I kept thinking in my head I bet it is something with UEFI but didn't put it together. Thank you again!

Jacob Tanner 1 Reputation point

2022-08-30T23:36:50.647+00:00

Thank you, this worked perfectly for me.

Олег Ананьев 0 Reputation points

2023-12-02T12:26:43.2333333+00:00

my problem was solved
Sign in to comment
janloune 46 Reputation points

2020-07-18T16:22:32.777+00:00

Patrick, you are a genius! You made me discover that there was VM generations and you are right Gen2 does not support 32 bits instances.
3 months of trying with MS support....
Please sign in to rate this answer.

1 person found this answer helpful.
Dave Patrick 426K Reputation points MVP

2020-07-18T16:25:03.097+00:00

Glad to hear it helps. You're quite welcome.

Greg Woods 31 Reputation points

2023-03-31T15:04:16.3366667+00:00

Also make sure the boot order is set correctly in the "Firmware" settings. Network boot is first, it doesn't matter how fast you click and press space, you'll never get the prompt to boot from the DVD!
Sign in to comment
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more