Skip to main content
CybersecurityIncident Response

Microsoft Tests Cloud Rebuild Feature to Streamline Windows 11 Recovery

Windows 11 laptop on a neutral surface with recovery menu on screen in a minimalist room with ambient daylight.

"We're introducing Cloud rebuild, a new recovery option that restores a Windows 11 PC to a clean, known-good state by performing a full OS reinstall, even when Windows won't boot," Windows Insider Communications Lead Stephen Lines said on Monday.

How Cloud Rebuild works in Windows 11 Insider Experimental Preview Build 26300.8772

Microsoft has started testing Cloud Rebuild inside the Windows 11 Insider Program's Experimental channel. Insiders who want to try the feature must install Windows 11 Insider Experimental Preview Build 26300.8772 and then trigger the flow from the Windows Recovery Environment (WinRE) by choosing Troubleshoot > Recovery and clicking "Cloud rebuild." According to Microsoft's description, the process includes a review of the target Windows build, edition, and language, and an explicit confirmation of a data-loss warning before the rebuild begins.

Microsoft distinguishes Cloud Rebuild from the existing "Reset this PC" option by describing a different source for the reinstall. Cloud Rebuild downloads both the target Windows image and the device's drivers from Windows Update so that "the device comes back fully functional without USB media, without a custom image, and without depending on the health of the currently installed OS," Stephen Lines said. The published test flow also notes an additional step phrased as "and finally uninstall" as part of the recovery sequence provided to Insiders.

Where Cloud Rebuild sits inside the Windows Resiliency Initiative

Cloud Rebuild was first announced at Microsoft's Ignite developer conference in November 2025 and is presented as one component of a broader Windows Resiliency Initiative. Microsoft frames these tools as designed to "help quickly restore devices when they can no longer start or function properly."

In that context, Cloud Rebuild addresses the scenario of a device that is inoperable or cannot boot, providing a full OS reinstall sourced from the cloud. The ability to retrieve drivers from Windows Update is intended to return a device to a "known-good state" without the need for physical media or a locally stored custom image.

Complementary features: Point-in-Time Restore, Quick Machine Recovery, and memory-scan recommendations

Cloud Rebuild is being rolled out alongside other recovery and resiliency technologies that Microsoft has begun testing or releasing. At Ignite, Microsoft also announced Point-in-Time Restore (PITR), described as a feature that lets administrators and users roll back a Windows 11 system to an earlier, healthy snapshot within minutes. According to the announcement, PITR began rolling out in June with the release of the KB5095093 preview cumulative update for Windows 11 24H2 and 25H2.

Microsoft began testing an updated version of Quick Machine Recovery (QMR) in November as well. QMR is aimed at resolving boot failures without physical access: when a Windows 11 device fails to start due to a new driver or configuration change, it automatically boots into WinRE, launches QMR, sends crash data to Microsoft, and — according to Microsoft’s published description — Microsoft can remotely remove buggy drivers or updates and adjust settings to fix boot issues. In the same November test cycle, Microsoft also began testing a feature that recommends running a memory scan after a Blue Screen of Death (BSOD) to improve system reliability.

What this means for technologists and security teams, enterprises and procurement leaders, and end users

  • Technologists and security teams: Cloud Rebuild centralizes recovery sources by pulling the OS image and device drivers from Windows Update. Teams will need to assess how remote rebuilds interact with existing imaging, driver whitelisting, and endpoint configuration controls, and how crash data flows during recovery and QMR operations.
  • Enterprises and procurement leaders: The PITR rollout tied to KB5095093 and Cloud Rebuild's cloud-based reinstall model may affect choices about backup strategies and imaging investments. Procurement and operations teams must watch compatibility with 24H2 and 25H2 deployments and any administrative controls Microsoft exposes for these recovery flows.
  • End users: For individuals facing a non-booting system, Cloud Rebuild promises a path to restore functionality without USB media or a custom image. Insiders trying the Experimental build will see explicit prompts to review build, edition, and language and must confirm a data-loss warning before proceeding.

Next steps and operational questions Microsoft will need to address

Microsoft has placed Cloud Rebuild, QMR and PITR into a single resilience narrative: tools to repair, rewind and reinstall when devices fail. For Insiders, the immediate step is practical testing in Build 26300.8772. For organizations and users, the more consequential questions that follow from the facts Microsoft has published include how these remote actions are controlled administratively, what telemetry or crash data is shared during recovery, and how driver downloads from Windows Update are managed in environments that use curated driver catalogs or custom images.

Microsoft's public materials tie these capabilities to the Windows Resiliency Initiative and show a multi-pronged approach to reducing downtime: restore a known-good system image, roll back to a previous snapshot with PITR, or use QMR to surgically remove the change that prevented startup. The company began testing the pieces at Ignite and in subsequent preview releases; what remains is how enterprises and users adopt policy and operational guardrails around them.

Original reporting: https://www.bleepingcomputer.com/news/microsoft/microsoft-testing-new-cloud-rebuild-windows-11-recovery-feature/