windows 11 24h2

[superrootplus]

windows 11 24h2?

[geissbuehler]

lzw29107 has added support for Win11 24H2 to his fork https://github.com/lzw29107/MediaCreationTool.bat. Unfortunately the installation fails on unsupported hardware, but fortunately I was able to enable the upgrade from Windows 11 23H2 to 24H2 with the registry modifications according to the rufus FAQ.

I'm hoping that this registry modifications can be added to MediaCreationTool.bat to re-enable the installation of 24H2 on unsupported hardware. My understanding is that this will also work for upgrades from Windows 10 22H2 to Windows 11 24H2. Can someone test this upgrade on unsupported hardware?

[lacelestc]

Hello Yes Itested the fork modified script worked great for me to upgrade an unsupported hardware PC from w11 21H2 TO 24H2 but not directly .
look at modified script written by lzw29107 https://github.com/lzw29107/MediaCreationTool.bat
I had the blue screen crash so i figured out that my sdds drivers arnt compatible i disabled all of them except c where i put the iso and it s ok

[geissbuehler]

I have now performed more detailed tests with virtual machines running Windows 10 22H2 and Windows 11 23H2 using https://github.com/lzw29107/MediaCreationTool.bat/blob/main/MediaCreationTool.bat. Without the Rufus registry edits, on both machines the Windows 11 Setup was blocking the update because the PC does not meet the system requirements:

Unfortunately, the registry commands have been removed from the Rufus FAQ, but they are still preserved here, together with an explanation. I also pasted the commands below.

I assume that the 24H2 update via MediaCreationTool.bat fails because the /product server trick has been blocked by Microsoft. AveYo might need to include the registry modifications to reenable the 24H2 installation on unsupported hardware?

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\HwReqChk" /f /v HwReqChkVars /t REG_MULTI_SZ /s , /d "SQ_SecureBootCapable=TRUE,SQ_SecureBootEnabled=TRUE,SQ_TpmVersion=2,SQ_RamMB=8192,"
reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1

[bdog549]

Just a FYI for anyone that sees this. I've used this bat file the last few years to go from 21H2 to 22H2 to 23H2 and just now upgraded to 24H2 successfully. As soon as I mounted the ISO, and ran the setup.exe, the script ran via a command prompt that opened for a few seconds and the install process resumed and it worked as intended.

I can't recall which file I ran three years ago, either the auto.cmd or the ship TPM check on dynamic update. I'm guessing the latter. If AveYo knows or anyone else please chime in so I can pass on the info. I just can't remember what I ran originally lol.

[khadzic]

To follow up on in this thread, is 24H2 in the pipeline to be added to the MediaCreatioTool?