The recovery partition is probably not big enough to fit the new WinRE. You might need to resize the recovery partition to make it larger, ensuring it can hold the updated WinRE. However, modifying system partitions can be risky and should be done with caution, ideally using tools provided by the system manufacturer or Windows itself. Consider performing a clean installation. This involves wiping the hard drive and starting from scratch, which can sometimes resolve issues related to partition sizes and system file corruption. Before taking any of these steps, it's crucial to back up your important data to an external drive or cloud storage. This will ensure that your files, documents, and other valuable information are safe and can be restored after the process is complete. Backing up your data will prevent loss in case something goes wrong during the partition modification or clean installation process.
@antonio, and please define the hardware specs and from what build to what build you want to upgrade or what ISO you are using for the clean install/upgrade.
@Carlos Detweiller what is "a halfway-modern chipset! that is not blocked by MS (in 2025)? I asking just for educational purposes...
It disables the phonelink companion if you have new all apps list in the same page as the pinned (new startmenu experiment) For those of you wanted companion, don't enable 49402389. You can enable the others to get the updated grouping etc in all apps list. Personally i think its nasty as hell, the startmenu flyout looks huge without the separated companion, what happens when they finally (if) they add the companion? no thanks.
This PC is quite old. I believe it's from 200X. If the SSE 4.2 instruction set is needed then maybe that's the reason why it can't boot or upgrade from 23H2... Thanks for your help! At least now I know what could be wrong
26100.3775 bug forever not fixed yet ... The issue where the Microsoft Store appears to redownload all app updates, even when they are already up-to-date, is a known bug, and it's often linked to Microsoft's server-side issues rather than a problem with your system. While there's no definitive fix, some users have found temporary relief by signing out and back into the Microsoft Store, checking their Microsoft Account Order History, and even performing a repair or reset of the Microsoft Store.
just wanna confirm, KB5043080 [26100.1742] is still the last released checkpoint update for 24H2, right? No KB flagged as next checkpoint update after that KB5043080?
I know for a fact that the intel PIIX3 chipset is blocked. Will not boot, stuck on logo or boot loop. Like the SSE4.2 issue, it started suddenly with one Insider build, and there is no way around it..
Seems that the new xbox usb device driver is causing ppl to gsod when connecting there xbox devices via Bluetooth and usb. Don't know if retail got this driver update