Issue performing in-place upgrade to Windows 11 24H2 #2568
Comments
|
Similar problem, used rufus 4.5 and chosen "Remove requirement for 4GB+ RAM, Secure Boot and TPM 2.0", but the installation program promotes "TPM 2.0 is mandatory" thing. |
|
For in-place upgrades, you need to run the following from an elevated command prompt before running 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 1I'll add this batch script to the created media in a future version of Rufus. |
pbatard
changed the title
|
Seems like you wrongfully included "CompatMarkers" in the second and following paths. |
Ah my bad. Fixed. NB: So that people don't copy the wrong data, I removed the part you quoted from your post. |
|
I also needed to put quotation marks around the path of the add command, without that I got wrong syntax. |
|
OK, fixed that too. For the record, I tested the above by editing the registry manually, and I am still working on the script that I'm going to have Rufus copy over (which I will test properly of course...) |
|
Thanks, looks good now and is currently installing. |
Great. Thanks for the help! |
|
Thanks pbatard and others members. |
It should fix the new restrictions for in-place upgrade if you manually run a batch script that will be placed at the same level as It will not change anything for clean install, since I haven't found breakage in the clean install bypasses while testing, meaning that if a clean install of 24H2 doesn't work with Rufus 4.5, then it also won't work with Rufus 4.6. For what is worth, I tested in-place upgrade from 23H2 to 24H2 on an Intel I7-5930K/X99 system using the registry trick above, and was able to upgrade without issues. I have not tested a clean install on such a system yet, but I tested on a much older system, and so no issue either. At any rate, I can NOT EVER promise anything with regards to what the next release of Rufus might do or not do. You will find out when it is released. |
|
I used the batch file above and I was successful installing on a Ryzen PC with TPM disabled. Now it's installing 24H2, let's see if my laptop blows up after this :-) |
|
@jovan2009 you won't fix this with any hacks, new Windows is compiled with these CPU instructions in use, so it won't boot on these very old CPU. |
|
@Juraj-Masiar Oh well... It is to be expected. I am on my way to revert to Win 10 anyway, it was the last thing I was going to try with Win 11 before that. Win 11 has become progresively very slow, borderline unbearable, I booted a Win 10 WintoUSB install from a portable SDD a few days ago and it felt like an upgrade a few generations of hardware for my old laptop. So long Win 11, you will not be missed. |
|
Hello Pete Batard,
Thanks for your help.
I am focused only on in-place W11 23H2 upgrade to W11 24H2 on my ASUS Intel I7-5930K/X99 machine.
As I am not skilled , not familiar and not aware how to do for « you manually run a batch script that will be placed at the same level as setup.exe and that will contain the registry commands posted above. » ,
Please can you explain me in detail how you apply that Registry modification ?
Do you use the RegEdit Tool ?
Sorry for my ignorance.
At the moment I am stopped on my current W11 23H2 version.
Thanks for your patience.
100PIER
|
|
@100PIER you can also run those commands one by one in an Admin terminal:
|
This should work. At least that's what I've done. |
|
Many thanks for your help Juraj,
I do understand the procedure.
I will try soon and let you know the results.
At the moment I have copied the script in a text file format, so I can copy/paste line per line.
Regards,
Alain
|
HwReqChkVars value is truncated |
|
If you're talking about the last comma, it is very much required as it's a If you're talking about the CPU stuff from the Win 11 Boot And Upgrade FiX KiT, that's very much intentional. |
|
Those values will not be enough for all machines / CPUs |
|
I am not planning to add extra CPU bypasses besides the main bypass from |
|
I have W11 23H2. I tried to INSTALL W11 24H2 from USB created with Media Creation Tool, then using the trick of creating an empty appraiserres.dll on the USB and it works for clean installs. |
|
If it can help, I have applied AIO 2a fix from Enthousiast tool on 24H2 ISO and created an UEFI USB key with Rufus 4.5p. I installed the OS on a empty partition like a charm (the machine is 11 years old, i7 4th gen). As I have checked the five others Rufus options for Windows iso (unchecked the 1st one), it seems that they are all still operational at last, I have the username set, it skipped privacy questions, no Ms account asked… |
|
For clean install, all the options of Rufus 4.5 should work. Especially, you should not have to do anything special to clean install 24H2 as the current Rufus bypass should work. This thread, and the registry commands, are only about in-place upgrades, where you run |
|
Thank you, that's good to know, I wasn't sure of that. I can retry with all options, it's very quick. I can also confirm the 5 registry commands are ok to have setup.exe bypass the requirements to upgrade. As that in-place upgrade got stuck at 31 % for two hours on that machine (nearly nothing installed, probably stuck on some old drivers…) I did try a clean install. Edit: I confirm the first option is also working on a clean install, far easier! |
|
It also works by upgrading from 23H2 to 24H2 by putting: |
though the gdrv.sys driver problem is unrelated to rufus, you need to update your Gigabyte App Center or Gigabyte Control Center software as Gigabyte released updated apps to resolve the problem. |
|
Running 24H2 as we speak! Thanks! :) |
|
POPCNT and SSE4.2 requirement could be bypassed if someone figures out how to emulate and embed the instruction sets into the Win 11 24H2 installation and also have emulator boot before Win 11 24H2 boots every time. |
|
Much appreciation to Peter. One possible source of odd failures I found was that the in-place upgrade also needs to have at least TPM 1.2 visible to the install process. If TPM is turned off in BIOS the first boot after doing the install fails with error message and reverted to my prior 23H2 install. The HP Z620 workstations only have a TPM 1.2 chip on motherboard but the install wants to at least see it. That was after confirming the processor was POPCNT enabled, SSE4.2 listed in CPUz, and the CMD batch file run correctly. Once I fixed that everything went smoothly. |
That sounds strange, considering that I (and, from what I can tell, many others) performed multiple in-place upgrades on machines that have no TPM at all (which, a machine that has TPM 1.2 turned off should behave, in the exact same way, otherwise something has to be quite wrong in the manner in which the TPM was turned off). I therefore suspect that there was something else at play with your environment, because I'm certainly not getting any other reports of TPM needing to be turned on for an installation to proceed... |
Not true in my case. I have a Ryzen 2600x with TPM disabled in UEFI since forever. I installed (courtesy to Rufus and the batch in this thread) and I'm running 24H2 with no problem. |
|
Used rufus-4.6_BETA.exe and it worked perfectly not just for Win11 23h2 --> 24h2 Great work, thank you ! |
|
Glenn… thanks for the update. I need to do a proper experiment with an Acronis image and set the HP workstation BIOS to “hide” TPM. It turns out that in the more recent HP workstations one can hide TPM or make it available but disable it. So, it can be unhidden but disabled. I bet this is the issue I ran into earlier.
Thanks for the update.
|
|
I have tried W11 23H2 -> W11 24H2 with Rufus 4.6 on my Dell Precision T3600. Secure Boot problem "Error 0xC1900101 – 0x20017, The installation failed in SAFE_OS phase with an error during BOOT operation" after restart and the return to 23H2. |
|
@Marek-P-Miller, have a look at the upgrade logs whose location is documented here. All I can say is that I am pretty confident that your issue has nothing to do with Rufus or the bypasses, but something like drivers that are incompatible with 24H2, like others have previously reported in this tread. Especially, per Microsoft's documentation:
So you will need to identify precisely what driver you are using that is causing the issue, as you're unlikely to get external software like Rufus or people in this thread to be able to sort this out for you. |
|
Hello Pete, how are you ?
I joyfully used disk Genious, a very nice app. It did the copy fine but on
termination, it failed to make the Destination " bootable ", much to my
regret.
Do you think that it has to do with Secure boot or whatever it could be ?
I had selected that option on setting up the operation and as it mentioned
its inability to so do, that means that it had been selected.
I would really like to have that 1Tera HD operational. Any help
tremendously appreciated. Have a great day. JP
… Message ID: ***@***.***>
|
|
Sadly, I am still encountering the same impossibility to upgrade a live 23H2 system, even using Rufus v4.6beta or "Win 11 Boot And Upgrade FiX KiT" v5.0 / method 2a. This is a VirtualBox VM I am using to compile Windows builds of my programs, so it got no exotic driver (and yes, I do have ICH9 configured for the VM chipset emulation, since PIIX3 now crashes Win11 24H2 while it worked just fine with previous versions). I get error "0x8007042B - 0x2000D" during phase SAFE_OS / MIGRATE_DATA So there must be something else to find about, for some systems... Note that this VM has been migrated multiple times (from the first Win10 version to Win11 23H2) without a single issue so far. It got one peculiarity, in excess of not having secure boot neither TPM: it is using a MBR virtual drive with BIOS boot. Maybe this could be the problem ? On the other hand, I have no trouble installing a fresh Win11 24H2 VM (so I might end up reinstalling the whole shebang in a new VM). Micro$oft's hostile practices are really a total PITA: I just don't understand why they make things so difficult for the final users ! >:-( You guys are admirable for spending so much time finding workarounds for all the obstacles built by M$ with each new Windoze version. |
|
Henry, my problem ( solved ) was that I am sure that the boot sector have to be on the first one on the HD. Mine had multiple sectors there. So I used Gparted and flushed the whole sheebang. It then worked as a charm, I am on it now. What you can use to achieve the same result, is up to you. Have faith. Daopa-2 |
Not sure what you mean by "multiple boot sectors"... There is only one MBR on a DOS-formatted disk (from byte 0 to 446, in the the first disk sector), and that MBR is Windows' one. Then there are boot flags for each partition, but my VM disk only got such a flag on the first partition (the Windows boot partition). I verified with fdisk (attached the VM disk to a Linux VM and examined it from there) and there is no problem with partition flags, types, etc. (*) Or perhaps even Win7, immediately upgraded to Win10, to benefit from the free upgrade: it was years ago, so I don't remember the gory details, but it won't change a thing in how the disk partitions and boot sector are used. EDIT: using a cloned VM I also tried to convert the VM disk to GPT (with MBR2GPT.exe: very straightforward to use), and then activated EFI in the cloned VM and tried to update it to 24H2. Same failure... And before someone asks, yes, I also did the sfc /scannow and DSIM /HealthRestore procedures, etc, all to no avail. |
|
I could not do anything until I flushed the whole disk, I just pasted it on
for what it was worth.
Doing a format in the Windows system does not really fully flush it all,
that is why I used Gparted.
You obviously have another set up where I can not help you further. J.
… Message ID: ***@***.***>
|
|
Hello, |
|
For those of us that attempted the upgrade before the registry fix was known. Is there a fix for us? The upgrade seemed to mess with my master boot record and I'm now unable to boot back into windows. |
Hello, It is more easiest to recover the whole disk instead to install all of them from the beginning. Plus you will able to resolve your files as well. As it seems the build 24H2 contains a large volume of bugs and Microsoft frozen it's rollout till they fix them. So we have to wait them to fix the bugs before install this build on our PC's. |
That's not a Rufus generated problem. The Microsoft installer is supposed to revert changes if it fails to upgrade a platform, so if that hasn't happened, you need to take it to Microsoft.
I'm afraid there won't be especially as my guess, and I might be a bit harsh here, is that you guys might have tried things at random to proceed with the upgrade (because again, without alterations, Windows setup would just refuse the upgrade if your platform does not fill the hardware checks), which of course makes it impossible for someone external to just throw a "Just do X, Y, Z" one-size-fits-all kind of solution. There will be NO "magic bullet" solution from Rufus coming to your rescue here. |
|
I suppose it's time to leave Windows systems and jump on Linux Systems. It really hard decision but M$ making our lives more difficult with these "security restrictions". So it's our time to decide depending on our financial state either will buy new PC's which are supported by windows either to jump to Linux distributions. As it seems they are trying to block unsupported hardware. So they are not many options. Just two of above. |
|
Thanks, did not make any changes. Just ran the in place upgrade using 4.6 and after reboot noticing that I cannot bypass the "press any key to boot from usb." I can boot from usb with 4.5 using the same stick, and other sticks as well as other usb PE utilities. The 4.6 was downloaded today with 24H2 multiple times on multiple machines, same result. When I try with 4.5, 23H2, it does indicate that an upgrade was in progress. Options are to reboot or attempt a clean install. |
|
Installed 24H with rufus,but unable install Cumulative Update on dev channel. |
(Please don't take this the wrong way) By asking your question on a Windows user forum, which this issue tracker isn't. I hope you can appreciate that what you are asking has nothing to do with Rufus or the topic at hand, which is about problems when trying to install 24H2 (which you don't have). I am going to either lock this thread or delete entries if people start to post off-topic questions here. |
|
Just want to say I appreciate the feedback and apologize for upsetting you. I realize how annoying it may be to get so many submissions from folks who do not follow the issues direction laid out such as logs etc. I am new to GitHub and will try to be a better community member going forward. As a Rufus user, just want to express my sincere gratitude to you and any other contributors that continue to make this possible. |
|
Dears, Regs |
|
Hi. |
This was indeed the only option when installing Win11 on a Mac Mini (late 2012, no TPM). It doesn't support booting from NTFS (Rufus 4.6 cannot create exFAT USB) so I first had to install Win10 using Bootcamp (creates an exFAT Win10 installation USB with the necessary drivers) and then do an in-place upgrade to Win11. I also wanted to an in-place upgrade from Win10 to Win11 (24H2) on a Lenovo T420 (i5 2540M, has SSE4.2) but running setup.exe from the Rufus-created USB resulted in the attached screen. Will try the regedit commands above and retry. If it doesn't work |
Microsoft have apparently added a new warning about running Windows 11 on unsupported devices, these new warnings just require acknowledgment by the user to allow installation to proceed |
|
If this warning is true, "If you proceed with installing Windows 11, your PC will no longer be supported and won't be entitled to receive updates", I'm afraid that I will get stuck with the 24H2 buggy version and perhaps won't receive any security updates either. I'll stay with Win10 Pro 22H2 for now or upgrade to the 24H2 server product. |
No: I already had this message when I upgraded a friend of mine’s former PC (with a Core i7-4730K, no TPM) he gave me, one year ago, from W10 to W11 23H2; I clicked on “Accept” and the upgrade went fine. I get all Windows Update security updates. The only thing that I probably won’t have is the upgrade to 24H2 with WU, but I’ll just have to use Rufus again and do it that way. Not a real problem (as long as I won’t have some performances or network problems that some users who don’t have all the requirements for 24H2 got)… Remember that this kind of warning is just for MS to cover themselves and is the same as the big “ABSOLUTELY NO WARRANTY” you can read in the free softwares licence terms. It doesn’t mean that it won’t work, only that if it doesn’t, you’ll be by yourself and won’t have their support, that’s all. |
and others
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
The FUFUS created W11 24H2 64bit FR USB key does refuse W11 installation on my PC running W11 23H2
Log
Click to show the log
The text was updated successfully, but these errors were encountered: