sodcalculator

10 Tech How-To

Can’t Install Windows 11 on VM? Fixes That Work

Guide 10-44904 · Updated · Step by step

Yes, you can install Windows 11 on a virtual machine (VM), but only if the VM meets Microsoft’s strict hardware requirements—most importantly, TPM 2.0, Secure Boot, and a supported CPU. If your VM fails with errors like “This PC can’t run Windows 11,” it’s almost always because one of those virtual hardware features is missing or disabled. This guide walks you through the exact settings to enable in VMware, VirtualBox, and Hyper-V, plus workarounds for older hardware.

Why Windows 11 Is Harder to Install in a VM

Windows 11 introduced a mandatory hardware baseline that Windows 10 didn’t have. Microsoft requires TPM 2.0 (Trusted Platform Module), UEFI with Secure Boot, 4 GB RAM, 64 GB storage, and a compatible 64-bit CPU (Intel 8th gen or AMD Zen 2 and newer). Virtual machines are just software-emulated hardware, so they must expose these features to the guest OS. Many hypervisors default to legacy BIOS, no TPM, and an older virtual CPU—which triggers the install blocker even though your physical PC is perfectly capable.

The good news: every major hypervisor now supports the needed virtual hardware. The bad news: you have to know where to click, and the steps differ per product. Below are the exact settings for the three most common VM platforms.

Enable TPM 2.0 and Secure Boot in VMware Workstation / Player

VMware Workstation 15.5.5+ and Player 16+ can add a virtual TPM. The VM must be created with UEFI firmware first—you can’t add a TPM to a BIOS-based VM.

  1. Shut down the VM completely.
  2. Open VM Settings → Options → Advanced → set Firmware type to UEFI.
  3. Go to Hardware → Add → Trusted Platform Module → Finish.
  4. Check Options → Advanced → Secure Boot (enable it).
  5. Power on the VM and install Windows 11 normally.

If you don’t see the TPM option, your VMware version is too old—update to Workstation 16 or Player 16+. Also, the virtual TPM requires the VM to be encrypted in some versions; VMware will prompt you to set a password if needed.

VirtualBox: TPM and Secure Boot (Version 7.0+)

Oracle VirtualBox 7.0 finally added a virtual TPM 2.0 chip and Secure Boot support. Older versions (6.x and below) don’t have these features, so you must upgrade.

  1. Install VirtualBox 7.0 or newer and create a new VM with Windows 11 as the type.
  2. In the VM settings, go to System → Processor → check Enable TPM (choose TPM 2.0).
  3. In System → Motherboard, set EFI (not legacy BIOS) and check Enable Secure Boot.
  4. Increase RAM to at least 4 GB and disk to 64 GB.
  5. Start the VM and install.

If your CPU is older than Intel 8th gen, VirtualBox still won’t pass the CPU check. In that case, you have two options: use a compatibility bypass (explained later) or install Windows 11 on physical hardware instead.

Hyper-V: Built-in Support on Windows 10/11 Pro

Hyper-V is Microsoft’s own hypervisor, so it fully supports Windows 11 guests. You just need to create a Generation 2 VM—that’s the key. Generation 1 VMs use legacy BIOS and no TPM, so they’re automatically blocked.

  1. Open Hyper-V Manager → New → Virtual Machine → choose Generation 2.
  2. Assign at least 4 GB RAM and a 64 GB virtual disk.
  3. In the VM settings, under Security, enable Secure Boot (use the Microsoft template) and Trusted Platform Module.
  4. Boot from the Windows 11 ISO and install normally.

Hyper-V also lets you enable Virtualization Based Security (VBS) if you want, but it’s not required for installation.

What to Do If You Still Get “This PC Can’t Run Windows 11”

Even with TPM and Secure Boot enabled, you might see the error if the virtual CPU isn’t on the supported list. This happens on older physical CPUs or when the hypervisor emulates a generic CPU. Check the exact error message:

  • “TPM 2.0 is required” → TPM not enabled or not set to 2.0. Re-check your hypervisor settings.
  • “Secure Boot is not enabled” → Switch firmware to UEFI and enable Secure Boot.
  • “The processor isn’t supported” → Your CPU is too old for the official requirement. You can try a registry bypass (below) or use Windows 11 LTSC if you have access.

For the CPU issue, Microsoft allows an unofficial workaround: during installation, press Shift+F10 to open Command Prompt, type regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup, create a key named LabConfig, and add the following DWORD values: BypassTPMCheck (1), BypassSecureBootCheck (1), BypassRAMCheck (1), and BypassCPUCheck (1). Then close the registry and continue installation. This is a known community workaround, not an official Microsoft method—use it at your own risk, and note that updates might fail later.

Common Mistakes and Misconceptions

Many people assume that enabling TPM in the hypervisor is enough, but they forget to set the firmware to UEFI. Others try to install from an old ISO that doesn’t contain the latest compatibility checks—always download the official ISO from Microsoft. Another frequent mistake: using a VM created with default settings (legacy BIOS) and then trying to add a TPM—you can’t; you must recreate the VM as UEFI.

A common misconception is that you need TPM 2.0 on your physical PC to run a VM with Windows 11. That’s false—the virtual TPM is independent of your physical hardware. Even if your PC has no TPM, you can still create a VM with a virtual TPM (as long as your hypervisor supports it).

Comparing Hypervisors for Windows 11

  • Hyper-V: Best integration, but only on Windows Pro/Enterprise. Generation 2 VMs are straightforward.
  • VMware Workstation/Player: Works on Windows and Linux, but the free Player lacks some features. TPM support is solid in recent versions.
  • VirtualBox: Free and cross-platform, but TPM support is newer (7.0+) and sometimes buggy. Also, performance is generally lower than VMware or Hyper-V.
  • Parallels Desktop (Mac): Supports Windows 11 on Apple Silicon via virtualization, but requires a paid license.

For most users, VMware Workstation Player (free) or VirtualBox 7 are the easiest starting points. If you’re on Windows Pro, Hyper-V is the most reliable.

Frequently Asked Questions

Can I install Windows 11 on a VM without TPM?

Officially, no. Windows 11 setup checks for TPM 2.0 and will block installation. However, the registry bypass (described above) can skip the check, but it’s unsupported and may cause issues with future updates. It’s better to enable the virtual TPM if your hypervisor supports it.

Why does my VM say “This PC can’t run Windows 11” even though I have TPM enabled?

Usually, it’s because Secure Boot is off, or the VM is using legacy BIOS instead of UEFI. Double-check both settings. Also, ensure the virtual CPU is set to a recent model (e.g., host CPU or a modern Intel/AMD core).

Does Windows 11 run well in a VM?

Yes, for basic use and testing. You’ll need at least 4 GB RAM and 2 CPU cores. For smooth performance, allocate 8 GB RAM and 4 cores. Graphics are limited—don’t expect gaming or heavy 3D work.

Can I use a Windows 10 VM and upgrade it to Windows 11?

Yes, but the same hardware requirements apply. The VM must have TPM 2.0 and Secure Boot enabled before you run Windows Update. If your Windows 10 VM was created without those, you’ll need to recreate it as a UEFI/TPM VM.

Is it legal to install Windows 11 in a VM?

Yes, as long as you have a valid license. Microsoft allows Windows 11 to run in virtual machines, but the license terms are the same as for physical hardware—you need a product key. You can use the same key on multiple VMs only if you have volume licensing.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →