The nightmare named “This PC can’t run Windows 11”
Looking at a Dual Xeon Platinum server setup with 256GB RAM, yet Windows 11 still reports “unsupported configuration” is truly frustrating. This is a feeling many Lab or Proxmox enthusiasts have likely experienced. Microsoft flatly rejects machines worth thousands of dollars just because they lack a tiny security chip: TPM 2.0.
In real-world environments, setting up Windows 11 virtual machines for software testing or sandboxing is a huge requirement. However, default VM configurations on KVM or older Proxmox versions often use outdated standards. As a result, we get stuck right at the first installation screen.
Why does Windows 11 “reject” KVM/Proxmox virtual machines?
The reasons why Windows 11 is so “picky” with VMs usually revolve around these 3 critical points:
- TPM 2.0 (Trusted Platform Module): A security chip used for encryption. VMs do not have this hardware by default unless emulation is enabled.
- Secure Boot: A security feature for booting. It requires the VM firmware to be UEFI instead of traditional SeaBIOS.
- Outdated Chipset: Windows 11 requires a modern chipset. If you are still using i440fx (released in 1996), Windows will treat it as an ancient computer.
If you leave everything at default and click “Next”, Proxmox will provide a VM running an old BIOS without a security chip. Naturally, Windows 11 will reject it immediately.
Three popular “bypass” methods currently used
Each approach has its own pros and cons, depending on whether you want a quick fix or a proper setup:
1. Registry Bypass (Fast but not durable)
You press Shift + F10 at the error screen, type regedit, and add the BypassTPMCheck key. This allows for a very quick installation. However, the system will be flagged as “unsupported,” which can lead to issues with future Windows Updates or an annoying watermark in the corner of the screen.
2. Using Modified ISOs (Potential risks)
Using Rufus to create an ISO that removes the TPM requirement. This is convenient for old physical machines, but for VMs, managing multiple modified ISO files is a hassle. Not to mention, unofficial ISOs found online always carry extremely high security risks.
3. Hardware Emulation (Software TPM) – The Best Choice
This is the most “official” solution. Instead of tricking the OS, we provide exactly what it needs. KVM supports swtpm to create a high-quality virtual TPM chip, making the VM appear as a modern PC.
Standard Setup Guide on Proxmox (Version 8.x)
With my Lab setup running over 10 VMs, here is the standard process for a smooth Windows 11 experience with full weekly updates.
Step 1: Optimized Hardware Configuration
When creating a VM (Create VM), you need to pay special attention to the following tabs:
- OS: Select the Windows 11 ISO and remember to check “Add Windows guest agents/drivers” to automatically detect drivers later.
- System: This is the key part:
- Machine: Must be changed to
q35. - BIOS: Must choose
OVMF (UEFI). - Add EFI Disk: Check this to save Secure Boot configurations.
- Add TPM: Select version
v2.0. This is the ticket for Windows 11.
- Machine: Must be changed to
- Disks: Choose
VirtIO Block. Real-world speeds are 2-3 times faster than standard IDE or SATA.
Step 2: For pure KVM/QEMU users
If you manage via virt-manager on Ubuntu/Debian, install the TPM emulation support packages first:
sudo apt update && sudo apt install swtpm swtpm-tools ovmfIn the VM’s XML file, ensure the following declaration is present to activate the virtual security chip:
<tpm model='tpm-tis'>
<backend type='emulator' version='2.0'/>
</tpm>Step 3: Handling VirtIO Drivers during Installation
Many users panic when they don’t see their hard drive during installation. This is simply because Windows does not have built-in drivers for the high-speed VirtIO standard.
Mount the virtio-win.iso file (usually available in the Proxmox ISO library). When choosing a disk, click Load Driver and point to the vioscsi\w11\amd64 folder. The hard drive will appear immediately.
Step 4: Verify the Results
After reaching the desktop, open Device Manager. If you see Security devices -> Trusted Platform Module 2.0, congratulations, you’ve succeeded. Windows Update will work smoothly just like on a real machine.
Real-world Tips and Experience
Even with TPM, Windows 11 is resource-heavy. Don’t skimp on RAM; allocate at least 8GB if you’re coding or running heavy apps. Using an NVMe drive via the VirtIO standard will help the VM boot in just 5-7 seconds.
Emulating TPM isn’t just for installing Win 11. It also allows you to experiment with security features like BitLocker without risking your actual hardware. Good luck building your ideal Windows 11 VM!
