It's a joke
The hardware is the hammer!
I agree - don't be concerned - I'm running the Beta on an old Lenovo T61 ( in fact it's still IBM! ) - all good just had to change the HDD to SDD ... no rounded corners but I couldn't be bothered to look for graphics drivers - it works OK.
So that's why I couldn't upgrade my Windows! Where do I get one of those?
Hint: It's a Craftsman...
You can just burn a usb using Rufus, which removes the tpm and secure boot requirements :). So you just download the Windows 11 ISO, burn it to usb with the correct version of Rufus (selecting the options to bypass tpm and secure boot). Then just install from USB as you would with Windows 10. Apparently it can now bypass the requirements for in place upgrades as well.
Rufus 3.18: bypass Windows 11 system requirements during Inplace upgrades - gHacks Tech News
The latest version of Rufus, a tool to create bootable USB Flash drives, supports bypassing Windows 11 system requirements during Inplace upgrades.www.ghacks.net
Latest version is here. As I discovered recently, you have to burn and select "next" or "finish" or whatever, before you reach the dialogue that gives the option to tick to remove TPM and secure boot. Explains (vaguely) further down this page - about the "separate dialogue" - it's not immediately visible as it used to be in 3.16 beta.
Rufus - Create bootable USB drives the easy way
Rufus: Create bootable USB drives the easy wayrufus.ie
reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /freg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f
The trouble with those is that they might work for one or two specific releases but they can't be guaranteed to work after any new release. In any case running that type of command line from the install medium can lead to all sorts of errors. Since I like to test a new build with a VM first it suits me fine and taking and restoring a macrium dump doesn't wreck a system when the install for whatever reason fails. !!! Since if a VM won't install it's pointless even thinking about installing on a Real machine. !!No offense, Jimbo, but that's the easiest way?
How about this:
Start setup as normal by booting from your installation media. At the first static screen, press SHIFT + F10 to open a command prompt. Run this command:
reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f
Follow up with 4 more commands as shown below:
reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f
TIP: Since these commands are all identical except for the text in the middle of the command, just hit the up arrow after running the first command, then change that string. Also, you may not need to run all of these commands, but it won't hurt to do so. For example, if the only requirement you don't meet is the TPM, just run the first command.
That's all! Close the command prompt and continue installation in exactly the same way you would normally.
However this method won't usually guarantee Activation --with a VM so long as you copy the GUUID the build will stay activated on almost any kit you care to name.
