Bypassing Windows 11 Hardware Requirements via Registry Modification and Setup Command

After Windows 11 was released, Microsoft raised hardware requirements, causing many older PCs to fail the compatibility check when running setup.exe from a local ISO.

The author previously shared a simple workaround: instead of double‑clicking setup.exe, run the command setup.exe /product server, which tricks the installer into thinking it is installing Windows Server, thereby bypassing the hardware test. This method works for most older versions but was blocked starting with Windows 11 build 27686.1000 (Canary channel).

To address the newer restriction, the article provides a registry‑based method:

Open the registry and delete the keys CompatMarkers, Shared, and TargetVersionUpgradeExperienceIndicators under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags

.

Create a new key named HwReqChk under AppCompatFlags.

Within HwReqChk, create a multi‑string value called HwReqChkVars and set its data to the following lines:

SQ_SSE2ProcessorSupport=TRUE</code><code>SQ_SSE4_2ProcessorSupport=TRUE</code><code>SQ_NXProcessorSupport=TRUE</code><code>SQ_CompareExchange128=TRUE</code><code>SQ_LahfSahfSupport=TRUE</code><code>SQ_PrefetchWSupport=TRUE</code><code>SQ_PopCntInstructionSupport=TRUE</code><code>SQ_SecureBootCapable=TRUE</code><code>SQ_SecureBootEnabled=TRUE</code><code>SQ_TpmVersion=2</code><code>SQ_RamMB=9999</code><code>SQ_SystemDiskSizeMB=99999</code><code>SQ_CpuCoreCount=9</code><code>SQ_CpuModel=99</code><code>SQ_CpuFamily=99</code><code>SQ_CpuMhz=9999

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup, create a new DWORD (32‑bit) value named AllowUpgradesWithUnsupportedTPMOrCPU and set its value to 1.

After applying these changes, you can double‑click setup.exe in the ISO to install Windows 11 without the hardware check.

For convenience, the author also offers a ready‑made .reg file (named “24H2绕过硬件检测.reg”) that applies all the above modifications with a double‑click. The download link is provided in the article.

The author notes that the registry method works for the current 24H2 preview and is expected to remain effective for future Windows 11 versions, while the original setup.exe /product server command is only blocked in builds 27686.1000 and later.