How to Bypass the TPM 2.0 and Secure Boot Requirements During Windows 11 Installation

The Strict Hardware Requirements of Windows 11

When Microsoft announced Windows 11, they introduced highly controversial hardware requirements. Specifically, the operating system refuses to install unless the motherboard supports UEFI Secure Boot and possesses a Trusted Platform Module (TPM) version 2.0 chip. While these features significantly enhance security against rootkits and malware, they artificially obsolete millions of perfectly capable, older computers (mostly those built before 2017) that otherwise have plenty of CPU power and RAM to run the OS.

If you attempt to install Windows 11 via a bootable USB drive on an unsupported PC, you will be met with a hard stop screen stating: “This PC can’t run Windows 11.”

However, the installer checks for these hardware requirements using simple registry keys. By interrupting the installation process and modifying the registry in real-time, you can force the installer to skip these checks entirely.

Step-by-Step: Bypassing the Checks During Installation

These steps assume you have already created a standard Windows 11 bootable USB installation drive using Microsoft’s Media Creation Tool and have booted the unsupported PC from that drive.

Step 1: Trigger the Error

1. Boot from the Windows 11 USB drive.
2. Proceed through the initial language and keyboard selection screens.
3. Click Install Now.
4. When prompted, select your edition of Windows (e.g., Windows 11 Pro).
5. At this point, the installer will perform its hardware check and present the error screen: “This PC can’t run Windows 11. It doesn’t meet the minimum system requirements.”

Step 2: Open the Hidden Command Prompt

Do not click the back arrow or close the window. You must remain on the error screen.

1. On your keyboard, press Shift + F10.
2. A black Command Prompt window will instantly open over the graphical installer.

Step 3: Launch and Modify the Registry

1. In the Command Prompt window, type regedit and press Enter. The Registry Editor will open.
2. In the left-hand navigation pane, navigate to the following path:
   HKEY_LOCAL_MACHINE\SYSTEM\Setup
3. Right-click on the Setup folder, select New, and then click Key.
4. Name the new key exactly: LabConfig and press Enter.
5. Click on the new LabConfig folder so it is highlighted.

Now, you must create two specific values inside this folder to disable the checks.

Bypass the TPM Check

1. Right-click the empty space in the right-hand pane.
2. Select New > DWORD (32-bit) Value.
3. Name it exactly: BypassTPMCheck and press Enter.
4. Double-click the new BypassTPMCheck value.
5. Change the “Value data” from 0 to 1 and click OK.

Bypass the Secure Boot Check

1. Right-click the empty space again.
2. Select New > DWORD (32-bit) Value.
3. Name it exactly: BypassSecureBootCheck and press Enter.
4. Double-click the new BypassSecureBootCheck value.
5. Change the “Value data” from 0 to 1 and click OK.

Note: If your CPU is also deemed unsupported, you can create a third DWORD named BypassCPUCheck and set it to 1, though the TPM and Secure Boot checks are the most common blockers.

Step 4: Resume the Installation

1. Close the Registry Editor (click the red X in the top right).
2. Close the Command Prompt window.
3. You are now back at the “This PC can’t run Windows 11” error screen.
4. Click the Back arrow in the top left corner of the window.
5. This takes you back to the Edition selection screen. Select your edition again (e.g., Windows 11 Pro) and click Next.

The installer will run the hardware checks again. Because you modified the registry, the installer will skip the TPM and Secure Boot validation, presenting you with the Microsoft Software License Terms. You can now accept the terms, format your drive, and install Windows 11 as if you were on a brand-new computer.

Warnings and Considerations

Running Windows 11 on unsupported hardware comes with caveats. Microsoft officially states that unsupported PCs are not guaranteed to receive Windows updates, including critical security patches. While, historically, unsupported machines have continued to receive updates normally, you must accept the risk that future feature updates may require manual installation or that certain security features (like Core Isolation) will be unavailable.