With the launch of Windows 11 in 2021, Microsoft introduced stringent hardware compatibility requirements that have become a topic of much discussion among users and tech enthusiasts alike. The upgrade process for Windows 10 PCs now involves a compatibility appraiser that assesses whether the hardware meets the necessary criteria. If a user’s CPU is not on the supported list or if the PC does not include a Trusted Platform Module (TPM) version 2.0, the upgrade is halted.
However, for many in the Windows community, this compatibility check has been more of a puzzle to solve than an insurmountable obstacle. Two primary methods have emerged that allow users to bypass these hardware restrictions and successfully upgrade to Windows 11, even on older machines. One of these methods has garnered significant attention, as detailed in a popular article on ZDNet titled How to upgrade your ‘incompatible’ Windows 10 PC to Windows 11: Two options.
Exploring the Workarounds
Microsoft has officially acknowledged one of these techniques, which is particularly aimed at corporate clients. This method involves a minor registry modification that permits the upgrade on systems with incompatible CPUs, provided the TPM is enabled—an older TPM 1.2 will suffice. Unfortunately, systems without any TPM cannot proceed with the upgrade.
The second method, which has gained traction for its simplicity, involves a more rudimentary hack: replacing the compatibility appraiser module (Appraiserres.dll) with a zero-byte file. The widely-used Rufus utility automates this process, allowing users to bypass the TPM requirement and even the need for Secure Boot. Many users have reported success with this technique, even on significantly outdated hardware.
However, a recent update from Microsoft, coinciding with the release of Windows 11 version 24H2 on October 1, has disrupted this workaround. Users have reported encountering error messages when attempting to upgrade using the Rufus-created installer, even after employing the compatibility bypass options.
In response to this setback, Rufus developer Pete Batard quickly provided a workaround. For in-place upgrades, users must execute a series of commands from an elevated command prompt to make additional registry changes before running the Setup.exe. These commands, originally shared by the developers of the Win 11 Boot And Upgrade FiX KiT, are crucial for navigating the new restrictions:
reg.exe delete "HKLMSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsCompatMarkers" /f 2>NUL reg.exe delete "HKLMSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsShared" /f 2>NUL reg.exe delete "HKLMSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsTargetVersionUpgradeExperienceIndicators" /f 2>NUL reg.exe add "HKLMSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsHwReqChk" /f /v HwReqChkVars /t REGMULTISZ /s , /d "SQSecureBootCapable=TRUE,SQSecureBootEnabled=TRUE,SQTpmVersion=2,SQRamMB=8192," reg.exe add "HKLMSYSTEMSetupMoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1
After implementing these commands, users have reported successful upgrades. The next iteration of Rufus is expected to include these adjustments in a batch script, simplifying the process for users needing to bypass the new restrictions.
For those systems equipped with a TPM and configured with UEFI and Secure Boot, the upgrade process remains relatively straightforward, regardless of CPU compatibility. Additionally, there appear to be no compatibility checks for upgrades on systems already running Windows 11, which should alleviate concerns for existing users.
Nonetheless, the enhanced compatibility checks for older hardware lacking TPM or utilizing Legacy BIOS configurations present a significant challenge, particularly for users who may not possess a technical background in Windows deployment. Ongoing testing and feedback from users encountering issues will be crucial in navigating these new developments.
For those experiencing difficulties with their upgrades, feedback can be directed to a dedicated inbox set up for this purpose, ensuring that user experiences are documented and addressed effectively.
