Install a Win11 Enterprise on Hyper-V is not accepted

[RedPit]

i tryed to install a Windows 11 Enterprise Test system on my Desktop System with Windows 11 Enterprise installed.

Preset 5Gb Memory and our standards like any other running Hyper-V systems.

Result just after start of installation: Pc does not support minimal requirements to install this Windows-Version

Any Idea whats wrong here?

 

[Sir Vagus Mus]

Did you make sure the VM has all the hardware requirements setup? Secure Boot, TPM 2.0, 4 GB RAM, Dual core 8th generation+ Intel Processor or supported AMD Processor? Plenty of Disk space? UEFI?

 

[RedPit]

Hyper-V properties for the tryed to Win11 system:
Memory was set to 5GB
processors was set to 3 (set before starting Install)
i did not find any way to set TPM ans Secure Boot on the Hyper-V side.
TPM 2.0 is set on the Host
Secure Boot is set on the Host
Host is running Windows 11 Release code. (soi expecting inheritance to the Hyper-V system)

still: not able to install a Hyper-V test system with windows 11 (release code)

 

[Sir Vagus Mus]

Hyper-V properties for the tryed to Win11 system:
Memory was set to 5GB
processors was set to 3 (set before starting Install)
i did not find any way to set TPM ans Secure Boot on the Hyper-V side.
TPM 2.0 is set on the Host
Secure Boot is set on the Host
Host is running Windows 11 Release code. (soi expecting inheritance to the Hyper-V system)

still: not able to install a Hyper-V test system with windows 11 (release code)

this video may help you. It goes over how to enable TPM and secure Boot in Hyper-V and VMware

 

[RedPit]

Thanks for the video.

The critical decissions are:

Hyper-V 2.Generation (to be able to configure TMP and Secure Boot)
(i am using an Microsoft ISO Image as source)
Before start do under Properties - Security:
Enable TPM
Enable Secure
Set memory to at least 4096 MB
and select at least 2 Processors.

So far so good, this should be sufficient.

In my case the start to create an 2.Generation vhdx is about a minute blocked and then an Error Message:

Virtual Machine Boot Summery
1. SCSI DVD (0,1)
The boot loader failed.
2. SCSI Disk (0,0)
The boot loader did not load an operating syteem.
3. NetworkAdapter (xxxxxxxxx)
A boot image was not found.
.....

This message makes sense, but why does the loader not find my ISO file?
(tryed also with an other win 10 ISO - the same effect.)
(All former used Hyper-V Systems are until now 1.Generation type and are generated and working fine)

Sits the bug in front of the Screen?

 

[Trouble]

Virtual Machine Boot Summery
1. SCSI DVD (0,1)
The boot loader failed.
2. SCSI Disk (0,0)
The boot loader did not load an operating syteem.
3. NetworkAdapter (xxxxxxxxx)
A boot image was not found.

I was getting the same error.
Assuming when you added and configured your "virtual DVD" and pointed it to your ISO, you didn't avoided a conflict with a SCSI controller location that was already in use, which looks good and proper according to the errors you posted.


You need to move it to the top of your boot options menu.


It seems to be necessary as an initial setting, because there is no way you can hit a key fast enough to respond to the prompt " hit any key to boot from DVD", at least I was never able to get there in time.

It's just a temporary setting, which as you can see from my image has been changed automagically to the EFI Windows Boot Manager "file" after the install succeeds.

 

[RedPit]

Thanks for that precise info.

But, still after checking again and event reimplemented as new Hyper-V system the boot process to install is not working with the same error message.
also a windows 10 install is not booting as expected with the same error.
(an external win11 Hyper-V System imported work fine)

is there any extra to care of?

 

[Trouble]

Can you take a couple window snip images of your two configuration windows as I did above, so I can take a look?

 

[RedPit]

here the full stack:






thanks in advance...

 

[Trouble]

Everything looks good to me
Just personal preferences for me
Never use "Dynamic Memory" I set it to 4096 just like yours and untick the box
Always use even number of processors pick 2 or pick 4
That's just me and probably has nothing at all to do with your issue(s)
Additionally, the path to the ISO is nested pretty deep.
Generally, I will put it in the root of a drive, usually alone on a USB stick
Again, that's just me, what you have should work.

 

[Trouble]

Read above ^^^^^^^
THEN
Is this what you are seeing???

 

[RedPit]

Thats exactly the error message i get after more than 30 seconds wait..

 

[RedPit]

Thats the error message i get after more than 30 seconds wait..

the network erorr # is (00155D01A01F)

 

[Trouble]

OK.....
The only way, I've been able to beat that is to open Hyper-V Manager, select the VM on the left, connect on the right, and then use the start button inside the VM interface rather than the Manager interface and then immediately start tapping the enter key to respond almost in advance of the prompt to hit any key to boot from DVD.

The only other thing I can think to do, is....
On the host machine
Double click your ISO to mount it.
That will produce a virtual DVD with a physical drive letter
You can then use that within the VM setting to point to as your virtual machine's DVD and first boot device.
That might work

IF not you may have a bad ISO.

 

[RedPit]

still not able to load.
I close this and pass this over to Microsoft support.

 

[RedPit]

Found a hack to start the installtion:

after getting the last seen error (Virtual Maschine Boot summery)
i tryed by pressing Tab and Space bar to restart the loading.
2. try it worked.
so it seems to be an internal bug to access the declared ISO.

 

[Kux]

| The boot loader failed.
You have to press a key to boot from CD.
You must be very fast after starting the VM ;-)

 

[RedPit]

This seems to work, at least...
But is from my point of view an Windows Bug.