The TPM 2.0 requirement for Windows 11 was one of the most talked-about changes from Windows 10, especially since it effectively locked many perfectly good machines out of an upgrade path.
There are ways and means of getting around this requirement to upgrade your laptop or desktop PC, but what if you just want to fire up a quick virtual machine? There are products out there, such as those from VMware, that can inject a virtual TPM to allow Windows 11 to install.
But the easier method is to just skip it altogether. Here's how to quickly and easily install a Windows 11 virtual machine if you're being blocked.
What you need
All you need for this is a Windows 11 ISO (opens in new tab) and some software to make a virtual machine. For the purposes of this guide, I will be using VMWare ESXI 7, but the process shouldn't be any different if you're using something else such as Hyper-V or VirtualBox.
How to install a Windows 11 VM without TPM
This method would, of course, also work on bare metal, but we're not necessarily suggesting it as a good idea since the requirements exist for a reason. But in a virtual machine, everything is sandboxed, so the risk factor is lower.
Essentially what we're going to do is tell Windows 11 during the installation process to skip the TPM check. Once you do this, Windows 11 will install with no issue.
In your virtual machine manager of choice, set up a VM and begin the Windows 11 installation process. The first steps are normal, choosing a language and such. But you will soon find yourself looking at the screen above telling you that your PC can't run Windows 11.
When you reach this screen, follow these steps:
- Hit Shift + F10 on your keyboard to open Command Prompt.
- Enter the following command:
REG ADD HKLM\SYSTEM\Setup\LabConfig /v BypassTPMCheck /t REG_DWORD /d 1
- When you see the operation completed message, close the Command Prompt.
- Go back one step in the installation process.
- Now proceed as normal.
Now, as you continue with the installation you'll no longer see a warning that your PC can't run Windows 11 and everything will continue as planned. If you'd prefer, you can type
into the Command Prompt to open the GUI Registry Editor to add the key detailed above, but simply typing that single line into the terminal is definitely the fastest way.
As an additional step, you may need to add one further registry key. If after doing the above you still get the error, open up the Command Prompt again and enter this command:
REG ADD HKLM\SYSTEM\Setup\LabConfig /v BypassSecureBootCheck /t REG_DWORD /d 1
Some VM software, such as VMware used here, seem to handle secure boot requirements, but others, such as Virtualbox, do not. So you may need to also disable this.
That's all there is to it. Your Windows 11 VM will now install as normal with no warnings, and you can get onto some top-level virtualizing.
Windows Central Newsletter
Get the best of Windows Central in in your inbox, every day!
Richard Devine is an Editor at Windows Central. A former Project Manager and long-term tech addict, he joined Mobile Nations in 2011 and has been found on Android Central and iMore as well as Windows Central. Currently you'll find him covering all manner of PC hardware and gaming, and you can follow him on Twitter and Instagram.
Even with the register-hack Windows 11 setup keeps saying that it cannot install Windows 11. And what is with the waiting before posting?
Because you don't have a "compatible" processor.
Amazing information providing by your article, thank you so much for taking the time to share a wonderful article.
I'm glad Parallels now has virtual TPM support.
Certainly can be handy. VMware has the same, but after some quick internetting this seemed to be the quickest way for me. Still finding my feet with VMware as it is!
Has VMware finally released their version with Apple Silicon support? They were non-committal about ever supporting it when I first got my M1 Mac. Otherwise, I might be running it now instead of Parallel$.
Easiest method to install Windows 11 if your PC don't support TPM and Secure Boot
1. Download rufus, you must download v3.17 or newer, otherwise this method doesn't work.
2. Open rufus, select your USB flash drive and then click "Select" button on the right and find your Windows 11 ISO.
3. See at Image option, change "Standard Windows 11 installation" to "Extended Windows 11 installation (no TPM 2.0/no Secure Boot).
4. Look at partition scheme, if your PC support UEFI select "GPT" and target system "UEFI (non CSM)", if not then choose "MBR" and "BIOS (or UEFI-CSM).
5. Make sure File system are set to "NTFS".
6. Click start and wait until the process 100% complete.
7. Reboot your PC, go to BIOS and set first boot order to your USB flash drive.
8. Finally you can install Windows 11 without any problem. You can thanks me later.
And yet this method is basically not applicable to a virtual machine where you're not creating a bootable USB drive. Which is entirely what this post is about.
Does it have to be restricted in relevance to Virtual machines if the information he is giving might be of assistance to others? This is a forum for all things Windows - try not to be so fickle mindedly sensitive.
I've not tried yet, but is this also needed using Microsoft's own Hyper-V for the VM, or does it then know to auto-bypass this check? In any case, thanks for the very helpful tip, Richard!
Not sure as I don't use Hyper-V, you would hope Microsoft could pass it through but we all know how easy it is to be disappointed! At least these steps are universal if needed, I've tried them on a few different VM systems. Though it was only VMware of the ones I tried that didn't also need to bypass Secure Boot as well.
In looking into this a bit more, I see that Hyper-V does have options right in its GUI (nice) on the Security tab to turn on TPM and Secure Boot. I assume these work regardless of the capabilities of the host, but I suppose it's possible they only appear as options if the host already has them (my PC's have this and I don't feel like to turning off TPM in BIOS to check). In any case, yes Hyper-V makes these trivial, at least on PC's with TPM. For the processor, Hyper-V appears to pass along the CPU code of the host, so that could still be a problem if the CPU is pre-8th Gen. There's a different registry entry to bypass the 8th Gen CPU requirement (this could also be converted into a command line, like in the article) to enable upgrading from Windows 10 (a bit different from a clean install, but this might also be helpful for some): HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
New DWORD (32-bit)
Set Value to 1 I think that handles both CPU and TPM.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.