When installing Windows 11 on a VMware virtual machine (Workstation, Player, or ESXi), it’s common to run into a frustrating roadblock:

“This PC can’t run Windows 11” or “TPM 2.0 requirement not met.”

This error occurs because Windows 11 has stricter security requirements than its predecessors, mandating features that are not enabled by default on most virtual machines.

Fortunately, this is easy to fix. This guide will walk through the best ways I found to resolve the TPM error, from the official VMware method to simple bypasses.

The “Why”: Understanding the Windows 11 Requirements

The Windows 11 installer checks for three key security features before it will proceed:

  1. UEFI Firmware: The VM must be configured to use UEFI, not the legacy BIOS.
  2. Secure Boot: A UEFI feature that ensures only trusted software is loaded during boot.
  3. Trusted Platform Module (TPM) 2.0: A security chip (or virtual equivalent) that provides hardware-based security functions.

If any of these are missing, the installation will stop. The solutions below address how to either meet these requirements or tell the installer to ignore them.

Method 1: The Official VMware Way (Adding a Virtual TPM)

The best and most compliant method is to add a virtual Trusted Platform Module (vTPM) to my VM. This creates a virtual TPM 2.0 device that satisfies the Windows 11 requirement without any hacks or bypasses.

Step 1: Encrypt the Virtual Machine

For security reasons, VMware requires that a VM be encrypted before I can add a vTPM.

  1. Shut down my virtual machine completely (do not suspend).
  2. Go to VM Settings → Options → Access Control.
  3. Click the Encrypt button and set an encryption password. I will need this password to change the VM’s settings in the future, but not to power it on.

Step 2: Add the Virtual TPM Device

  1. With the VM still powered off, go to VM Settings → Hardware.
  2. Click Add → Trusted Platform Module.
  3. Click Finish and then OK.

That’s it! My VM now has a vTPM 2.0 device. I can now start the VM and install Windows 11 without any compatibility errors.

Method 2: Bypassing the TPM Check During Windows Setup

If I don’t want to encrypt my VM or prefer a quick workaround, I can instruct the Windows 11 installer to bypass the TPM and Secure Boot checks.

Step 1: Open the Registry Editor During Setup

When I saw the “This PC can’t run Windows 11” error screen:

  1. I pressed Shift + F10 on my keyboard. This opened a Command Prompt window.
  2. Type regedit and press Enter to open the Registry Editor.

Step 2: Create the LabConfig Registry Key

  1. In the Registry Editor, navigate to the following key: 
    HKEY_LOCAL_MACHINE\SYSTEM\Setup
  2. Right-click on the Setup key, select New → Key, and name the new key LabConfig.

Step 3: Create the Bypass Values

  1. Select the new LabConfig key.
  2. In the right-hand pane, right-click and select New → DWORD (32-bit) Value.
  3. Create the following three DWORD values, setting the data for each one to 1:
    • BypassTPMCheck
    • BypassSecureBootCheck
    • BypassRAMCheck

Step 4: Continue the Installation

Close the Registry Editor and the Command Prompt. Click the back arrow in the top-left of the Windows Setup window, and then click Next again. The installer will now proceed without checking for TPM, Secure Boot, or RAM requirements.

Method 3: Using a Modified ISO (The Rufus Method)

For a more permanent bypass solution, I can use a free tool called Rufus to create a modified Windows 11 installer that automatically skips the TPM check.

  1. Download Rufus from its official website.
  2. Download the official Windows 11 ISO from Microsoft.
  3. Open Rufus and select my USB drive (if I’m creating a bootable USB) or leave it as is if I just want a modified ISO.
  4. Select the Windows 11 ISO file.
  5. When I click Start, Rufus will present a “Windows User Experience” dialog.
  6. Check the box that says “Remove requirement for 4GB+ RAM, Secure Boot and TPM 2.0”.
  7. Click OK.

Rufus will create a new ISO file (or a bootable USB) with the TPM check already disabled. I can then use this new ISO to install Windows 11 on my VM without any errors.

Comparison of Methods

Method Best For Pros Cons
Add Virtual TPM Production VMs, compliance Official and supported, most secure Requires VM encryption
Registry Bypass Quick, one-off installations No third-party tools needed Must be done manually each time
Rufus ISO Patch Repeated installations, convenience Creates a reusable, pre-patched installer Requires a third-party tool (Rufus)

Conclusion

The “TPM 2.0 requirement not met” error is a common hurdle when installing Windows 11 on a VMware VM, but it’s easily overcome.

  • For the most secure and compliant setup, always add a virtual TPM to your VM. This is the recommended approach for any long-term or production virtual machine.
  • For quick lab or testing environments, the registry bypass during setup is a fast and effective workaround.
  • For convenience, using Rufus to create a pre-patched ISO saved me time on future installations.

With these solutions, I could get any VMware VM ready for Windows 11 in just a few minutes.