It always came this error message that the boot process did not work. Thomas then tried the tips described in the blog post above and other places I found, but none of it worked. But now I wanted to make a Win11 out of the Win10 in Hyper-V and for that I had to solve this Gen2 problem. I was then only once a bit surprised when I found that I could install a Linux as Gen2 without any problems. But that was so far ok and was quite sufficient for my purposes. I had not found your above post at the time either. I still had one license left, which I could use for this.Īt that time I was not able to install this Win10 in the VM as Gen2, but since the device and Hyper-V were new to me, I did not dabble any further, but installed the Win10 as Gen1. I was already affected by this Gen 1/2 problem about 3 years ago, when I had newly purchased my current notebook with Win10 Pro and got the idea to install another Win10 in Hyper-V for testing after all. The starting point of my description of the problem is this post from 2019.

I would like to leave it then to your judgement whether you use this information further. very interesting information on the topic 'Installation of Windows 10/11 in Hyper-V 2nd Generation', which is certainly too extensive to write directly as an answer in a post. Today I would like to address you directly for the first time, because I came across m.E. Now Thomas has looked into the issue and wrote: I had already pointed out in 2019 in the blog post Hyper-V 2nd Gen: Can't install an operating system that the installation of a guest operating system can end with an error message 'PXE Network boot using IPv4 …'.

Hyper v windows 10