Anyone who has fought a boot loop at 2 a.m. while hunting for a working USB stick will appreciate this one. Microsoft’s October 28 optional preview update, KB5127936 (OS builds 26300.9818 and 26200.9818), introduces Cloud rebuild. It’s a new recovery option that reinstalls Windows 11 using an image and device drivers downloaded from Windows Update. Microsoft says it works “including when Windows is unable to start,” and needs no USB media or custom image.
Inside Windows, it lives under Settings > System > Recovery > Rebuild PC. That restarts into the Windows Recovery Environment and begins the rebuild. If Windows can’t boot, the device enters WinRE, where the option is also available.
You can also choose to remove your files, or securely erase the drive using the storage hardware’s own erase capability before the reinstall. Microsoft notes that sanitization can’t be undone. IT admins can trigger Cloud rebuild remotely through the Recovery CSP, either on the installed build or a specified target build.
A companion change lets WinRE reuse Wi-Fi profiles already saved in Windows, including certificate-based networks. Recovery tools can now get online without you typing a password into a bare-bones recovery screen. That matters, because a cloud reinstall is useless if the recovery environment can’t reach the internet.
A fresh install that already has chipset, network, and storage drivers beats the old dance of downloading a NIC driver on another machine. It also gives Microsoft a cleaner answer to update-induced disasters like the April update that triggered BitLocker recovery screens and boot loops.
The caveats: this is a preview release, and you’ll want your BitLocker recovery key backed up before testing anything that wipes or rebuilds a drive. A full reinstall is also still a full reinstall, so keep backups of anything you care about. Expect the feature in the standard cumulative update cycle soon. Let us know your thoughts in the forums.
Discussion (4 replies)
Join Discussion →Glad to see they have caught up to every other OS circa 2003
I thought this had years, maybe on server only?
How soon until Cloud Rebuild becomes Forced Upgrade?
I've got some HP laptops at the day job that've been giving me grief with various updates from 25h2 on (had a couple stuck in a perpetual 25h2 repair loop/crash rinse and repeat), and I've had to reset more than a few of them. Btw, done with HP for a spell because of this and some other models before them with other build quality issues.
Meanwhile, unless MS manages to fix said bugs that create catastrophically unstable OS problems, this won't mean squat because I've let some attempt to do resets for up to a week using cloud and local reinstall options only to fail repeatedly because of recurring system crashes. Now, as IT is only one of my many hats and I've got enough working spares on hand, I like to see how things play out when I see recurring issues arise on the same hardware across multiple machines. I've done the homework in checking reports and error codes, and finding online solutions, and occasionally jumped through all the hoops to manually fix, but it's often like rolling the dice, and ultimately I end up using a flash drive to end run this crap when my patience runs out.
Used to like cloud install options if for nothing more than being able to click away and let it do its thing. However, since we have the bandwidth to spare and I can walk away and check back on it later, I've seen how if the OS is unstable enough, it's meaningless, so I don't see how this will help either. To be fair though, the next time it comes up, I'll give it a try. Ironically just finished reinstalling the last one, that I know of, which is having update-related BSOD issues today. The problem that I've encountered is that if the PC is dependent on the on-drive Windows OS to handle or at least begin, the reinstall process, even when reaching out to the cloud to finish the job, if it is unstable enough, the system will inevitably crash during the process, and using a flash drive is the only way around this since it bypasses whatever is on the system drive during the BIOS handoff.