What can I do to make 24H2 work on VMware fling on ARM? Windows 10 and Windows 11 22H2 work fine, but 24H2 boots to black screen Is that something similar to POPCNT requirement?
Only LRCPC instruction is required for Arm, but that also required (or checked?) for Windows 11 22H2 too
Hi there, i'm failing to update to 24h2 using the first option of the fix. it's to upgrade a i7-7700 + asrock M-itx H270. don't know if i must try again the first option or trying the other options... when it fails, i'm going back to 23h2. I was on insider before, but did a rollerback to stable normal version before doing this updgrade. there is 260 000 lines in the log of $WINDOWS.~BT so don't know what to do to try to find why it failed...
Hi, i found the problem lol. after 3 installations. First, i thought it was the fact i was connected by internet but it's not. but in case i shutted it down. The main issue is more subtil. My Hardware config is set up that way : i use the video output of my motherboard as the FIRST screen, and use my PCI card (1050ti Nvidia 4Gb) only as a "renderer" Card (for Video editing Ai etc ...). Why ? because if i boot on the nvidia, the last nvidia drivers eat kind of 300mb of Vram at startup., which was making forbidding me to use some software as i was using them at the limit of the 4Gb. on the third instation (still the 1st method), when the screen went black , i had a doubt and plugged a monitor on the Nvidia Output.. and here both screen who appears, the background of my window desktop and the blue screen of the windows server installation. So the whole installation is in fact done under Windows 23H2. Then at some point the screen went black and both monitor turned off... but the hard disc was still working.. so i hit the poweron button one time, and it turned on both screen and with the instatlation who was continuing.. I assume that my motherboard or this installion has some difficulties with such case where "Graphics Onboard" is turned on in the bios, and the PCI is turned on too (with no screen attached). as now, as i have both screen turned on, the second screen is seen as the "first screen" in windows. It's certainly activated the extended mode at some point during the installation. So thanks a lot for the magic script, and hope this story can help people who would have the same installation as me. plug the screen on your Pci-e or remove the card or Shut it down in the bios. Edit : actually installing updates and it failed on the cumulative update for 24h2 , giving an error. Edit 2 : after a reboot, the KB5043178 is not available anymore and an another update is allowed. unfortunatly the new update refuse to install, it's the KB5044284, but it's certainly not related to this installation (i hope)
To install Windows 24h2 InPlace, simply run the code in cmd as administrator before clicking on setup.exe in the 24h2 iso, please test it. Code: 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
Looks this is no longer works i used option 1 & 2b options getting the failed to validate the product key? I am using the latest 26100.2033.241004-2336.ge_release_svc_refresh_CLIENTCONSUMER_RET_A64FRE_en-gb converted to WIM 2033
This has no relation to the tool, it is about activation, what is the current sku and how is it activated? It's either option 1 separately OR option 2a to fix the ISO and option 2b to prepare the current registry, or run the script copied to the ISO. And nothing is blocked, both options still work. If the bypass wouldn't have worked you would have seen something like: this pc doesn't meet the requirements, tpm or secureboot and such.
i injected the key have always used as my PC is activated through HWID and this works fine on version 1742 SORRY OK Scrap that i am using the wrong version of windows x64 needed not ARM time for a large coffee
Anyone know how to fix the error in my previous post? Seems a few ppl also had that error but didn't see any solution
my Hp is crashing after second boot failing into BSOD the message shown is Driver PNP Watchdog then it undos the 24h2 update. i disabled all unnecessary devices like i managed to install 21h2 , 22h2 and 23h2 in Place updates but still the error. how could i deal with that please ? thks for the help.
If you were able to select the desired SKU at boot, and install started, the tool worked and the problem is not caused by the win 11 system requirements.