23H2 to 24H2?

hsehestedt said:

For an upgrade installation, you can simply do this:

Take the lines below and save them to a text file. Name that file "WinUpdate.reg". NOTE: Any name is fine, just use a ".reg" file extension.

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\PCHC]
"UpgradeEligibility"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup]
"AllowUpgradesWithUnsupportedTPMOrCPU"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]
"BypassCPUCheck"=dword:00000001
"BypassDiskCheck"=dword:00000001
"BypassRAMCheck"=dword:00000001
"BypassSecureBootCheck"=dword:00000001
"BypassStorageCheck"=dword:00000001
"BypassTPMCheck"=dword:00000001

Double-click that .reg file to merge the contents into the registry. That is all. You can now install 24H2 as an upgrade. Note that this will work to upgrade you to the latest 24H2 Preview Release builds as well. At the time of this writing, the latest ISO image from Microsoft is the 26100.1150 build which is completely up to date including the July Patch Tuesday updates.

Reference:

Bypass Windows 11 System Requirements on Unsupported PC

This tutorial will show you how to bypass the Windows 11 CPU, RAM, Secure Boot, and TPM 2.0 system requirements allowing you to clean install or upgrade to Windows 11 on a unsupported PC that doesn't meet these requirements. Installing Windows 11 on a device that does not meet Windows 11...

www.elevenforum.com

Click to expand...

Silvio said:

Great post, many thanks.

Click to expand...

hsehestedt said:

Thanks! I appreciate the comment. Please do let us know if you need any further help.

Click to expand...

Silvio said:

When I first came to this site, I was a bit snobby about all this "tinkering", to install W11 on "unsupported" machines, as I had actually bought a supported machine to avoid all this.

Now after being able to install W23H2, on much cheaper and more powerful "unsupported", Dell Precision 5810, I actually have the "supported" Dell 7090 up for sale !!!

Click to expand...

hsehestedt said:

For an upgrade installation, you can simply do this:

Take the lines below and save them to a text file. Name that file "WinUpdate.reg". NOTE: Any name is fine, just use a ".reg" file extension.

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\PCHC]
"UpgradeEligibility"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup]
"AllowUpgradesWithUnsupportedTPMOrCPU"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]
"BypassCPUCheck"=dword:00000001
"BypassDiskCheck"=dword:00000001
"BypassRAMCheck"=dword:00000001
"BypassSecureBootCheck"=dword:00000001
"BypassStorageCheck"=dword:00000001
"BypassTPMCheck"=dword:00000001

Click to expand...

garlin said:

Not to be harsh, but I see a lot of false information repeated online.

1. AllowUpgradesWithUnsupportedTPMOrCPU only applies to in-place (live system) upgrades. You can update this setting right before running Setup from the mounted ISO.

2. HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig only applies to a clean install (booting from ISO). It does nothing for in-place upgrades.

Half of these BypassChecks are garbage and don't exist for real. The only working Bypass values:

BypassTPMCheck​

BypassSecureBootCheck​

BypassRAMCheck​

There's an entire GitHub issue for Rufus which covers this fact in more detail. Rufus no longer bothers with the fake Bypasses. The only storage check that's performed is Setup expects to see a minimum of 54 GB for Windows partition. That's hardcoded inside Setup. If you want to get around it, then boot WinPE and run DISM /Apply-Image to extract the image onto a smaller volume, and then run bcdboot to finish up.

I'll add a note on Brink's tutorial thread.

Click to expand...

hsehestedt said:

Thanks Garlin. I was already aware that the DiskCheck and StorageCheck were no longer needed. I left them in place to match what was shown in the tutorial just to avoid confusion over me show one set of vales and the tutorial showing something else. From now on, since the tutorial is updated, I will omit those entries. However, the fact that the CPUcheck is no longer needed was new to me.

Click to expand...