{"id":10879,"date":"2019-08-25T08:13:41","date_gmt":"2019-08-25T06:13:41","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10879"},"modified":"2024-10-05T18:34:31","modified_gmt":"2024-10-05T16:34:31","slug":"hyper-v-2nd-gen-cant-install-an-operating-system","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/08\/25\/hyper-v-2nd-gen-cant-install-an-operating-system\/","title":{"rendered":"Hyper-V 2nd Gen: Can&rsquo;t install an operating system"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2013\/03\/winb.jpg\" width=\"58\" align=\"left\" height=\"58\">[<a href=\"https:\/\/www.borncity.com\/blog\/2019\/08\/25\/hyper-v-2nd-gen-betriebssystem-lsst-sich-nicht-installieren\/\" target=\"_blank\" rel=\"noopener noreferrer\">German<\/a>]In Hyper-V, you may not be able to install guest operating systems in Generation 2 VMs. The installation process ends with a 'PXE Network boot using IPv4 &#8230;' message. <\/p>\n<p><!--more--><\/p>\n<h2>The error image<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg01.met.vgwort.de\/na\/5fd237cd6eba45a1830173239fe91068\" width=\"1\" height=\"1\">I come across the corresponding error description in this German administrator.de post a few days ago:<\/p>\n<blockquote>\n<p>Setup VM W2016 does not start in Hyper-V 2016<\/p>\n<p>is just sitting over my new server and trying to install it a VM at the host. I wanted to install a W2016 VM (as Generation 2 over an ISO) as a guest os in Hyper-V &#8230; briefly saw the prompt to press any key to setup via the \"optical drive\" &#8230; and then I'm constantly in a black screen with \"PXE Network boot using IPv4 ( ESC to cancel). Performing DHCP Negotiation &#8230;.\" please.<\/p>\n<\/blockquote>\n<p>It looks like the prompt to press a key is not being passed to the virtual machine. Then the VM will not boot from the mounted ISO file and attempt a PXE network boot, which of course fails. <\/p>\n<p><img decoding=\"async\" title=\"PXE Network Boot\" alt=\"PXE Network Boot\" src=\"https:\/\/scomandothergeekystuff.files.wordpress.com\/2017\/01\/1.png\"><br \/>(Source: scomandothergeekystuff.com)<\/p>\n<p>If you search the internet for this error message, you will get several hits at once. The <a href=\"https:\/\/social.technet.microsoft.com\/Forums\/windows\/en-US\/fbed0fe1-daa8-40e1-8d5c-3c63957d59ad\/win-10-hyperv-guest-gen2-wont-install-os-from-iso-using-virtual-hard-disk?forum=win10itprovirt\" target=\"_blank\" rel=\"noopener noreferrer\">Technet forum thread here<\/a> discusses the issue &#8211; and <a href=\"https:\/\/www.pbworks.net\/windows-10-hyper-v-vm-boot-not-working\/\" target=\"_blank\" rel=\"noopener noreferrer\">this blog post<\/a> also deals with the topic. The above screenshot is from <a href=\"https:\/\/web.archive.org\/web\/20230127150944\/https:\/\/scomandothergeekystuff.com\/2017\/04\/06\/hyper-v-2016-linux-vm-pxe-network-boot-error\/\" target=\"_blank\" rel=\"noopener noreferrer\">this blog post<\/a>.<\/p>\n<h2>Suggested solutions for the problem<\/h2>\n<blockquote><\/blockquote>\n<p>In <a href=\"https:\/\/www.pbworks.net\/windows-10-hyper-v-vm-boot-not-working\/\" target=\"_blank\" rel=\"noopener noreferrer\">this blog post<\/a> you will find a hint to set the Secure Boot option to \"Microsoft UEFI Certificate Authority\" in the security settings or to disable the Secure Boot. <\/p>\n<p><img loading=\"lazy\" decoding=\"async\" title=\"Hyper-V Secure Boot\" alt=\"Hyper-V Secure Boot\" src=\"https:\/\/scomandothergeekystuff.files.wordpress.com\/2017\/01\/3.png\" width=\"618\" height=\"585\"><br \/>(Source: scomandothergeekystuff.com)<\/p>\n<p>The above screenshot is also from the contribution of <a href=\"https:\/\/web.archive.org\/web\/20230127150944\/https:\/\/scomandothergeekystuff.com\/2017\/04\/06\/hyper-v-2016-linux-vm-pxe-network-boot-error\/\" target=\"_blank\" rel=\"noopener noreferrer\">scomandothergeekystuff.com<\/a>, but refers to Ubuntu there. On German WindowsPro you can find <a href=\"https:\/\/www.windowspro.de\/tipp\/vm-startet-nicht-unter-hyper-v-boot-failed-efi-scsi-device\" target=\"_blank\" rel=\"noopener noreferrer\">this article<\/a>, which also deals with this topic. There you can find the hint to convert the whole thing to Gen 1 VMs &#8211; which is not very helpful. Also in <a href=\"https:\/\/danielengberg.com\/start-pxe-over-ipv4-hyper-v-machine\/\" target=\"_blank\" rel=\"noopener noreferrer\">this article someone<\/a> deals with the configuration of the VM, but aims at a legacy network adapter for the network.<\/p>\n<p>On administrator.de, one person has found a completely different solution &#8211; he only makes sure that the keystrokes of the host are forwarded to the VM and the guest. He writes about this:<\/p>\n<blockquote>\n<p>Some suggestions found in the network (uncheck secure start, move ISO file) &#8230; have brought nothing. Note: In the HOST settings under User configure the keyboard for use with the \"physical\" computer &#8230; <\/p>\n<\/blockquote>\n<p>Maybe it will help one or the other affected person out of a mess.<\/p>\n<p><strong>Similar articles:<br \/><\/strong>RDP vulnerability puts Hyper-V at risk<br \/><a href=\"https:\/\/borncity.com\/win\/2019\/06\/18\/windows-10-v1903-ip-resolution-bug-in-hyper-v-switch\/\">Windows 10 V1903: IP resolution bug in Hyper-V switch<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2019\/02\/08\/hyper-v-vm-shutdown-issue-in-windows-server-2019\/\">Hyper-V VM Shutdown issue in Windows Server 2019<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2018\/09\/23\/tip-delete-hyper-v-vms-with-a-gui-tool\/\">Tip: Delete Hyper-V VMs with a GUI tool<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]In Hyper-V, you may not be able to install guest operating systems in Generation 2 VMs. The installation process ends with a 'PXE Network boot using IPv4 &#8230;' message.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,1218,2],"tags":[355,842],"class_list":["post-10879","post","type-post","status-publish","format-standard","hentry","category-issue","category-virtualization","category-windows","tag-hyper-v","tag-issuewindows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10879","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=10879"}],"version-history":[{"count":2,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10879\/revisions"}],"predecessor-version":[{"id":35502,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10879\/revisions\/35502"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=10879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=10879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=10879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}