With the end-of-life for Windows 10 rapidly approaching, Microsoft has been actively encouraging users to upgrade to Windows 11. However, one of the major hurdles for many users has been the stringent hardware requirements, particularly the requirement for TPM 2.0. This requirement has posed a challenge for owners of older or custom-built PCs that lack the necessary chip.
To circumvent this requirement, many users have utilized a well-known workaround involving the ‘setup.exe /product server’ command. However, Microsoft has recently patched this workaround in a beta build of Windows 11. While this patch is currently limited to Insider builds, it is expected to be rolled out to the general public soon.
The TPM (Trusted Platform Module) is a microchip responsible for handling encryption tasks and is considered a standard security feature for modern PCs. While most computers purchased within the last eight years readily meet the TPM 2.0 requirement, older machines have presented a significant hurdle for users eager to upgrade to Windows 11.
The recent patch could prove to be a major inconvenience for users who relied on the workaround. With this option removed, users are left with a limited set of alternatives:
*
Find another workaround:
While likely more complex, users can search for alternative workarounds, many of which can be found online.*
Upgrade hardware:
This option involves upgrading the existing PC to meet the Windows 11 hardware requirements, which can be a costly endeavor.*
Switch to Linux:
Alternatively, users can consider switching to a Linux distribution, which typically does not have the same stringent hardware requirements.*
Revert to Windows 10:
The easiest option is to revert back to Windows 10, which will continue to receive security updates until October 2025. This option is likely the most appealing for users who were initially hesitant to upgrade to Windows 11 due to the TPM requirement.Microsoft has yet to officially announce this patch and a specific release timeline for the general public remains unclear. However, given the growing prevalence of the workaround, it’s only a matter of time before the patch becomes widely available. Users who have been using the workaround should prepare for a potential transition to one of the available alternatives.
