Microsoft has taken a firm stance against upgrading older Windows 10 PCs to Windows 11, implementing stringent hardware compatibility requirements since the operating system’s launch in 2021. Users attempting to install Windows 11 on machines equipped with CPUs from 2018 or earlier are met with error messages and a subtle suggestion to consider purchasing a new device. This has sparked a familiar dance between the tech giant and the Windows enthusiast community, where each new development raises the stakes in this ongoing chess match.
Community Responses and Workarounds
The latest feature update for Windows 11, version 24H2, saw Microsoft tightening the compatibility checks during the upgrade process. These new restrictions effectively blocked a popular workaround that utilized the open-source Rufus utility to create installation media for incompatible hardware. However, the community quickly adapted, discovering a method to circumvent these compatibility barriers by manually entering a series of commands to modify the registry. In response, Pete Batard, the developer of Rufus, has released a beta version of the utility that automates this process, albeit with some features that may raise eyebrows.
At first glance, Rufus 4.6 beta appears similar to its predecessor. When users opt to bypass the Windows 11 hardware compatibility checks, the utility replaces the official compatibility appraiser, Appraiserres.dll, with a 0-byte file, just as before. However, to navigate the new restrictions introduced in version 24H2, it employs several innovative techniques.
The most notable change involves renaming the official Windows Setup program, Setup.exe, to Setup.dll, while simultaneously introducing a new custom program called Setup.exe. Additionally, it creates an $OEM$ subfolder within the Sources folder, containing various subfolders and a single file. Executing the newly created Setup.exe prompts a permission dialog, indicating that the file is a Windows Setup Wrapper, signed by Akeo Consulting, the parent company of Rufus.
For those curious about the inner workings of this wrapper, the code is available for inspection on GitHub. Running this wrapper performs the necessary registry modifications to bypass compatibility checks before invoking the original Windows Setup program. Batard acknowledges that this method might raise concerns about potential malware vectors, which is why the embedded setup executable is built using GitHub Actions and can be validated through SHA-256 checks.
Batard reassures users that Rufus adheres strictly to the official bypasses provided by Microsoft, avoiding any broad measures that would disable all hardware checks. He emphasizes that this approach should ensure that installations utilizing these bypasses remain functional in the future.
Reports indicate that this new workaround is effective on nearly any PC capable of running Windows 10. One user shared their experience, stating, “I waited for your subsequent article, and then the 4.6 Beta version of Rufus. Everything ran flawlessly and the machine is now running 24H2 with an old processor and no TPM. It certainly makes me wonder why Microsoft insists on the hardware parameters.” However, some older configurations, particularly those dating back to the Windows Vista era, may still face restrictions due to the operational requirements of Windows 11.
As it stands, the Rufus installer once again provides a pathway for users to upgrade to Windows 11 on unsupported hardware. The ball is now in Microsoft’s court.
