Esxi 7.0 Win 11 PC not meet requirements

[hongning123]

Need to install a Win 11 VM ,what is needed to install WIn 11 on Esxi 7.0

I keep getting message, when I start installing

PC does not meet requirements

We have a Dell R540 and I know it has a TPM 2.0 module, what do I need to do when creating the VM?

[alantz]

You need to add the registry entry to bypass the check. On a fresh install you might have to install Windows 10,

add this registry entry, then do the upgrade.

 

https://support.microsoft.com/en-us/windows/ways-to-install-windows-11-e0edbbfb-cfc5-4011-868b-2ce77ac7c70e

--Alan--

 

 

 

[hongning123]

Thanks for replying pretty much appreciated.

However what if if we want to have Win11  do the TPM checked.  We bought the server to consider the requirement.  What do I need to do to this.  I already confirmed with Dell that the TPM is enabled and working, but what needs to be done in Esxi side?

 

Thanks

 

[IRIX201110141]

Add the vTPM to your UEFI and secure boot enabled VM prior to the fresh Win11 install.

Regards,
Joerg

[hongning123]

Okay I enabled TPM is the server and enabled Secure Boot, how do I see if that enabled in the ESXI?  And how do you add vTPM to the ESXI host?

[IRIX201110141]

The phys. TPM doesnt matter.  vSphere 6.7 supports vTPM together with a external KMS and 7.02 comes with a Native Key provider one. 

vCenter->Configure->Security  and than add Native Provider.

 

Regards,
Joerg

[hongning123]

okay what if we want to use the physical TPM, shouldn't it be automatically detected by Windows 11 VM?

[IRIX201110141]

Not possible. The real TPM is for the Host and a vTPM for a VM. You add a vTPM by adding a new Device from type Trusted Platform Module to a VM.

Regards,
Joerg

 

[hongning123]

Sorry, I am not familiar with this topic, but can you add a vTPM to just the free ESXI version.  If yes can anyone send me a link on how to do it.  Cant seem to find any info on Esxi.

[IRIX201110141]

I think its a vCenter feature.

Regards,
Joerg

[jamesnb1]

Hey Joerg,

I am using latest version of vCenter and ESXi but could not find what devices to add the vTPM as per you mentioned... What is the vTPM device classified as?

Thank you

[IRIX201110141]

You have to add a Key provider first.  On vCenter level -> Configuration -> Security -> Key Provider -> Add

[IRIX201110141]

and after adding a key provider you are able to add a vTPM to a VM.

 

Regards,
Joerg

[jamesnb1]

Hi there,

I have added native key, back it up OK

Went ahead and create new VM, attached vTPM --> did not work, it said it required TPM v.2

I am using latest vCenter and latest Dell image ESXi (just upgrade yesterday)

Any idea?

[alantz]

When you created the VM did you choose the latest hardware version 19 ?

--Alan--

 

[jamesnb1]

Hi Alan,

Yes, it is version 19 as per the note

"Compatibility: ESXi 7.0 U2 and later (VM version 19)"

Anyway, I have deleted the VM and start over again. It is now working!

Thank you

[alantz]

Awesome. Sorry I just got to the email, but yea, version 19 is the 7.0 U2 release. U3 still uses version 19 as well.

--Alan--

 

[MZimbaro]

Glad to see all the people that have VSphere installed got it working.  What about the original question of installing Windows 11 directly on an ESXi 7 host (No VSphere).  This is the free version of ESXi for those of you who are not familiar.  Can a vTPM be created and installed, or should we be looking at something like Hyper-V instead?

[JeGray021]

In your specific case - Load a Win11 ISO onto your Host's datastore, attach a CD/ROM drive to your new VM (Image from Datastore), Find your ISO, and boot into a fresh install of Windows 11. From there, follow this guide on how to bypass TPM 2.0 on a fresh install: https://www.maketecheasier.com/safely-bypass-tpm-windows/

I would recommend using the Remote console view - IMO it makes it a bit easier to go between windows/tabs on a VM that does not have VMwareTools installed.

EDIT: The steps you want are all the way at the bottom of the article " 2. Modify the Registry on a Fresh Windows 11 Install "

[LabMasterBeta]

I strongly recommend against the Windows 11 non-compliant hardware Windows Registry hacks, they were intended only for Microsoft-internal Development, and will blow up on you during certain Windows Updates!

VMware now officially supports vTPM as a formal working method, which is strongly recommended to avoid future issues with Windows 11 and Server 2022.

See this VMware KB article:

https://kb.vmware.com/s/article/86037

That KB 86037 provides a VMware-Supported walkthrough on how to properly do this.

[alex2364]

This doesn't help people that are trying to install Windows 11 on ESXi 7.x WITHOUT vSphere. For people running the free version of ESXi 7 like homes labs, there is no vSphere available. Currently Windows 11 is basically not supported by ESXi 7 without vSphere, or you have to hack the registry. VMware should address this issue ASAP by adding native vTPM to all versions of ESXi without the need for vSphere.

[jaredmb]

I am on esxi 8 home lab.  From what I have seen so far this is still the case.  Meaning I may have to just ditch VMware all together and go with Proxmox or totally different hypervisor in order to virtualize windows in my home lab. 

Not meaning to necro but this does come up as a top search when searching for the TPM windows 11 error on vmware.

If I am wrong in this feel free to correct me please.

[jaredmb]

Yeah looks like this is still a thing.  In case anyone from vmware is reading this.  The inability of esxi alone to install the latest versions of windows means that it would be removed from consideration as a hypervisor platform for small footprint client software implementations (only around two esxi servers with no vcenter per deployment) for solutions like the one my companies provide.  In other words I have to take the resource hit of vcenter or no windows support.   Doesn't seem like a smart call but hey, it's vmwares to make.  Just trying to give a business justification for adding this functionality to esxi alone.

In summation, I have to go with Hyper-V or Proxmox inside my home lab and push for it as a hypervisor elsewhere in my org when possible.

Feel free to update this thread if/when this changes or if I am wrong.

[alantz]

 I would just like to note that my earlier registryr suggestion worked on my physicals, most of which I assume had TPM 1.2. However, when I went to upgrade my Windows 10 VM, it did't work. I not only had to enable the Native Key Provider and upgrade my Hardware version to the latest (I think I was on 17 and upgraded to 19), I also had to run mbr2gpt /convert /allowFullOS to convert my MBR to GPT and change the VM options/boot from BIOS to EFI and also do hardware/add the Trusted Platform Module. Then I was able to run the Windows 11 upgrade successfully, no registry changes needed. Oh, one last note. You can't do the hardware/add Trusted Platform Module if you have any snapshots on the VM.

 

--Alan--

 

 

[AlexAckerman]

As many have stated, the requirements are outlined on both the VMware and Microsoft documentation.  I recently published a blog entry that will walk you through the setup on a vSphere 7.0 system (with screenshots).  If you like it, please like and share!

https://www.vmhomelab.org/2021/10/prepare-homelab-for-windows-11-desktops/

Thanks!

Ack