You'll need an in-place upgrade or clean install to get 24H2.
DennyZenny's is spot on. Just to expand upon that a bit - If you install on technically unsupported hardware, you will be offered all the updates within that version (for example, 23H2), but you will not be offered the update to the next major version. It will be up to you to install that manually.
My unsupported System Two has been running Windows 11 since October 2021 and is now on 24H2. It has received all the cumulative updates, same as any supported device would, but was never offered any of the feature updates to the next version. Each one had to be manually installed, most as an in-place upgrade with an ISO and a workaround. The exception to the rule was the 22H2>23H2 update, which was simply a matter of manually installing the small enablement package (no workaround needed). Apparently 25H2 is expected to be another enablement package upgrade.
I recognized the same thing in my unsupported system's 22H2 to 23H2 migration. Glad to hear 25H2 will be a similar deal especially since we won't need a huge platform shift to get those bigger features user-facing features. Hopefully it'll be like that time when we got relatively big changes like File Explorer's new tabs or the address bar in simple moment updates (back when those were still a thing).
The signs are good. According to the article linked to by FrancoDT in post #1 here: Windows 11 25H2 Update 25H2 will be based on the current 26200 Dev build, which is 26100 with an enablement package.
setup.exe /product server for upgrades without a problem.
This tutorial is what I use for 24H2.
www.elevenforum.com
How do you do option 2 and 3 from a bare metal clean install?This tutorial is what I use for 24H2.
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...
Some swear by Rufus (Option One) but I prefer the registry fixes, Option Two or Option Three.
I have my reg commands in a .bat file on a standard install usb created by the MCT. I boot from the install usb then use Shift+F10 to get a command prompt. I can then run my batch file before continuing with the install.
The easy way is to download the ISO and use Rufus to create a patched USB flash drive that bypasses compatibility checks. Then boot from that USB and start Setup. The other option (mostly useful for virtual machines to avoid creating a USB flash drive), is to download the ISO and create a USB flash drive without patching (or just mount it if installing in virtual machine). On first setup screen or next one, you should see an option to use the old Setup interface. (at least there is one such option in 24H2). Select it, just in case, and then press SHIFT+F10 to open a Command Prompt. Execute
regedit to open Registry Editor and then follow these instructions:HKEY_LOCAL_MACHINE\SYSTEM\SetupLabConfig inside the Setup.BypassTPMCheck and set to 1BypassSecureBootCheck and set to 1BypassRAMCheck and set to 1BypassCPUCheck and set to 1BypassStorageCheck and set to 1
Note: The BypassCPUCheck and BypassStorageCheck do absolutely nothing. Having those entries will not hurt anything just like any other fictitious entries but you can simply omit them since they do absolutely nothing.
Probably the BypassStorageCheck is not needed by an average computer, but the BypassCPUCheck allows you to install on unsupported CPUs! This is much more important along with the TMP and Secure Boot.
Wrong! BypassCPUCheck does NOTHING! Try removing this entry and install on a system with an unsupported CPU. It will work fine without it. I do this multiple times a week.
<?xml version="1.0" encoding="utf-8"?>
<!--
Last updated on Mar 21, 2025
The purpose of this answer file is to bypass the Windows 11 system requirement checks, create a local user account, and
eliminate the need for an internet connection during setup. It does NOT perform an unattended installation of Windows.
This answer file will also bypass the installation of quality updates during Windows setup.
It includes a Windows 10 / 11 Pro key.
It will create a local user account named "WinUser" with a full name of "Windows User" and a password of "Password1".
END OF NOTES
-->
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserData>
<ProductKey>
<Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
</UserData>
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>2</Order>
<Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>3</Order>
<Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>UABhAHMAcwB3AG8AcgBkADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<DisplayName>Windows User</DisplayName>
<Group>Administrators</Group>
<Name>WinUser</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<OOBE>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>powershell.exe -Command "Get-NetAdapter | Enable-NetAdapter -Confirm:$false"</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>powershell.exe -Command "Get-NetAdapter | Disable-NetAdapter -Confirm:$false"</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
</unattend>
