How to Bypass TPM 2.0 Requirements for Windows 11 (And Why You Shouldn’t)

When Microsoft released Windows 11, they introduced a strict new set of system requirements that left millions of perfectly capable PCs stranded on Windows 10. The most controversial of these requirements? TPM 2.0 (Trusted Platform Module) and Secure Boot.

If you have tried to install or upgrade to Windows 11 on an older machine, you have likely encountered the dreaded “This PC can’t run Windows 11” error. While Microsoft designed these requirements to vastly improve hardware-level security, the tech community quickly found workarounds.

In this guide, we will explain exactly how to bypass the TPM 2.0 requirements for Windows 11 using official and unofficial methods. But more importantly, we will explain why you probably shouldn’t do it.

What is TPM 2.0 and Why Does Windows 11 Require It?

TPM stands for Trusted Platform Module. It is a tiny cryptographic chip on your motherboard (or built into your processor) designed to secure hardware by integrating cryptographic keys. Think of it as a physical vault inside your PC that protects your encryption keys, user credentials, and biometric data (like Windows Hello).

Microsoft made TPM 2.0 a mandatory requirement for Windows 11 to combat the rise of sophisticated firmware-level malware and ransomware. By forcing every Windows 11 PC to have a hardware root of trust, they significantly reduced the effectiveness of modern cyberattacks.

Method 1: The Official Microsoft Bypass (For TPM 1.2)

Surprisingly, Microsoft actually provides an official registry hack to bypass the TPM 2.0 check—but it only works if your PC at least has TPM 1.2.

Warning: Modifying the Windows Registry can cause system instability if done incorrectly. Proceed with caution.

1. Press the Windows Key + R to open the Run dialog.
2. Type regedit and press Enter to open the Registry Editor.
3. Navigate to the following path:
   HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
4. Right-click in the right pane and select New > DWORD (32-bit) Value.
5. Name the new value exactly: AllowUpgradesWithUnsupportedTPMOrCPU
6. Double-click the new value and set the Value data to 1.
7. Click OK, restart your PC, and attempt the Windows 11 installation again.

Method 2: Using Rufus to Create a Bootable USB

If your PC does not even have TPM 1.2, you cannot use the official Microsoft registry hack. Instead, the easiest and most popular method is to use a free tool called Rufus to create a modified Windows 11 bootable USB drive.

1. Download the official Windows 11 ISO file from Microsoft’s website.
2. Download and open the latest version of Rufus.
3. Insert a USB flash drive (at least 8GB) and select it under “Device” in Rufus.
4. Under “Boot selection”, click SELECT and choose your downloaded Windows 11 ISO.
5. Click START.
6. A special “Windows User Experience” dialog box will pop up. Check the box that says “Remove requirement for 4GB+ RAM, Secure Boot and TPM 2.0”.
7. Click OK and wait for Rufus to create your modified USB drive.
8. Boot your PC from this USB drive to install Windows 11 without any hardware checks.

Why You Shouldn’t Bypass the TPM 2.0 Requirements

Just because you can force Windows 11 onto an unsupported PC doesn’t mean you should. Here are the major risks you take by bypassing Microsoft’s hardware checks:

1. No Guarantee of Future Updates

Microsoft has explicitly stated that PCs running Windows 11 on unsupported hardware are not entitled to receive updates. While many users currently still receive standard monthly patches, Microsoft can choose to block major feature updates or critical security patches for unsupported devices at any time.

2. Severe Security Vulnerabilities

Windows 11 relies heavily on Virtualization-Based Security (VBS) and Hypervisor-Protected Code Integrity (HVCI). These features require a modern CPU and TPM 2.0 to run smoothly. By forcing Windows 11 onto older hardware, you are actively disabling the core security features that the operating system was built around.

3. Stability and Performance Issues

Microsoft data shows that devices on unsupported hardware experience 52% more kernel crashes (Blue Screens of Death) and 43% more app crashes compared to supported devices.

FAQ: Frequently Asked Questions