{"id":330,"date":"2021-12-13T10:52:53","date_gmt":"2021-12-13T09:52:53","guid":{"rendered":"https:\/\/vmoller.dk\/?p=330"},"modified":"2022-11-29T10:22:09","modified_gmt":"2022-11-29T09:22:09","slug":"installing-windows-11-on-esxi","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2021\/12\/13\/installing-windows-11-on-esxi\/","title":{"rendered":"Installing Windows 11 on vSphere \/ ESXi 7"},"content":{"rendered":"\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"801\" height=\"181\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-error.jpg\" alt=\"\" class=\"wp-image-331\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-error.jpg 801w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-error-300x68.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-error-768x174.jpg 768w\" sizes=\"auto, (max-width: 801px) 100vw, 801px\" \/><\/figure>\n\n\n\n<p>If you run in to the above error when installing Windows 11 as a virtual machine on ESXi (or other virtual platforms) then be aware that there is a workaround.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p>First of all make sure that &#8220;Enable Windows Virtualization Based Security&#8221; is enabled when the virtual machine is created.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"863\" height=\"217\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/WinSettings.png\" alt=\"\" class=\"wp-image-338\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/WinSettings.png 863w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/WinSettings-300x75.png 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/WinSettings-768x193.png 768w\" sizes=\"auto, (max-width: 863px) 100vw, 863px\" \/><\/figure>\n\n\n\n<p>When the setup starts (Showing &#8220;Install now&#8221;) then press &#8220;Shift + F10&#8221;  &#8211; this will open a command prompt on top of the setup window.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"792\" height=\"592\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-1.jpg\" alt=\"\" class=\"wp-image-333\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-1.jpg 792w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-1-300x224.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/win11-1-768x574.jpg 768w\" sizes=\"auto, (max-width: 792px) 100vw, 792px\" \/><\/figure>\n\n\n\n<p>When the command prompt appears type the following command:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">REG ADD HKLM\\SYSTEM\\Setup\\LabConfig \/v BypassTPMCheck \/t REG_DWORD \/d 1<\/pre>\n\n\n\n<p>Followed by &#8220;exit&#8221; <\/p>\n\n\n\n<p>Then you can start the installation &#8211; but without check for at TPM chip.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"699\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/Win11-2-1024x699.jpg\" alt=\"\" class=\"wp-image-334\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/Win11-2-1024x699.jpg 1024w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/Win11-2-300x205.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/Win11-2-768x524.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2021\/12\/Win11-2.jpg 1030w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">Bypassing TPM check<\/figcaption><\/figure>\n\n\n\n<p>Please be aware that Microsoft considers this as a security issue since best practise is to have a TPM v. 2.0 chip when running Windows 11<\/p>\n\n\n\n<p>You can find other guides that show how to enable a virtual TPM chip in VMware but I consider this the fastest workaround but it should only be used in a &#8220;Lab&#8221; environment <\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you run in to the above error when installing Windows 11 as a virtual machine on ESXi (or other virtual platforms) then be aware that there is a workaround.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[36,20,6,7,39],"tags":[23,24,4,40],"class_list":["post-330","post","type-post","status-publish","format-standard","hentry","category-esxi-nutanix","category-esxi","category-vmware","category-vsphere","category-windows-11","tag-esxi","tag-vcenter","tag-vsphere","tag-windows-11"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/330","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/comments?post=330"}],"version-history":[{"count":8,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/330\/revisions"}],"predecessor-version":[{"id":380,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/330\/revisions\/380"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=330"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=330"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=330"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}