Microsoft released Windows 11 Insider Preview Build 26300.8772 to the Experimental channel on July 6, 2026, introducing a “Cloud Rebuild” feature that can wipe and reinstall the operating system using files downloaded directly from the internet. The tool, buried in the Windows Recovery Environment (WinRE), automates what was once a manual, multi-step process—no USB stick or recovery partition required.
The build arrives with a cloud-first recovery tool
Build 26300.8772 is an Experimental flight, which means it tests concepts that may or may not ship. Microsoft dropped it into the Canary equivalent for early feedback, and the star of the show is Cloud Rebuild. Unlike the existing “Reset this PC” option that pulls system files from a local recovery image, Cloud Rebuild reaches out to Microsoft servers over an active internet connection. It downloads a fresh copy of Windows 11 and device drivers tailored to the PC’s hardware.
The option appears inside the Windows Recovery Environment. When a machine won’t boot or a user wants a clean start, they can boot into WinRE (typically by holding Shift during restart or triggering automatic repair). From there, under the Troubleshoot menu, they’ll find Cloud Rebuild. The tool warns that all personal files, settings, and apps will be removed, then prompts for an internet connection—wired Ethernet or Wi-Fi with drivers baked into WinRE. Once connected, it fetches the latest build of Windows 11 matching the installed edition and language, along with drivers from Windows Update’s catalog. The feature effectively performs a network-based clean installation without any local media.
Microsoft hasn’t detailed the exact partition layout it expects, but the process likely wipes the existing Windows partition and lays down a fresh system image in the same way a traditional USB installation would. The key difference is the source: Microsoft’s cloud endpoints replace the recovery partition or USB drive. Early testers report that the download size is roughly 4–5 GB, comparable to an ISO, and the whole process can take anywhere from 20 minutes to over an hour depending on internet speed.
What Cloud Rebuild means for different users
For home users, this is a rescue net that removes a major friction point. Many consumer PCs ship without a recovery drive or with a bloated recovery partition that fails when the hard drive is swapped or corrupted. Cloud Rebuild sidesteps those pitfalls. If the machine can connect to Wi-Fi and access WinRE, it can restore itself. The downside: you lose everything. Microsoft’s wording in the build explicitly says it removes “all personal files, apps, and settings,” so it’s not a repair tool. It’s a factory reset from the cloud, not an in-place upgrade.
IT administrators managing fleets will see both promise and peril. On the plus side, Cloud Rebuild could slash the time technicians spend re-imaging machines with custom images. A standardized cloud-sourced OS ensures every device gets the same baseline build and up-to-date drivers, which can simplify compliance and patching. But the feature raises security and control questions. IT departments often rely on custom recovery partitions with preloaded corporate software, security tools, and domain-join configuration. Cloud Rebuild would deliver a vanilla Windows 11 that still needs to be manually integrated into the corporate environment, potentially adding steps. Moreover, without a way to inject custom scripts or answer files, the feature may be less useful for enterprises that aren’t using Windows Autopilot—which already performs a similar cloud-based provisioning during OOBE. Admins will likely demand group policies to disable Cloud Rebuild or redirect it to internal servers.
Developers and enthusiasts get a faster path to a clean environment for testing. Instead of hunting down ISOs for the latest Insider build, they can blow away a VM and let Cloud Rebuild fetch the newest bits. It also opens the door for easier recovery on devices with limited USB ports or on tablets like the Surface Pro, where attaching external media is awkward.
How we got here: the long road to cloud recovery
Windows recovery has evolved slowly. Windows 8 introduced PC Reset and Refresh, which leaned on local component stores. Windows 10 unified the options under “Reset this PC” with choices to keep or remove files, but still required a local recovery image—either a dedicated partition or installation media. If that image was corrupted or missing, the reset would fail, often leaving users stuck.
Microsoft has been inching toward cloud reliance for years. Windows 10’s Setup and Upgrade processes could download updates during installation, but the base OS still came from local media. Surface devices pushed the envelope with cloud recovery; since 2020, Surface owners could create a bootable USB using Microsoft’s Surface Recovery Image downloader, which pulls an entire factory image from the cloud. That tool, however, still required a working PC and a USB drive to transfer the image. Cloud Rebuild removes the USB middleman entirely, putting the download functionality right into the recovery environment.
Industry peers have already gone further. Chromebooks can be recovered with a Chrome Recovery Utility and a network connection, and macOS users have relied on Internet Recovery since 2011. Windows has lagged, partly because of its hardware diversity and the complexity of driver injection. Build 26300.8772 shows Microsoft finally catching up, with cloud-based driver injection—a non-trivial engineering feat given the thousands of device combinations Windows supports.
The “Experimental” nature of the build suggests Microsoft wants to test the download infrastructure and driver-matching algorithms at scale before committing to a public rollout. Insiders in the Canary channel typically receive bleeding-edge code that may never reach production, so nothing is guaranteed. Still, the feature aligns with Microsoft’s broader push toward cloud-powered Windows experiences, from Windows 365 to feature updates delivered via the Windows Update mechanism.
What to do now: testing Cloud Rebuild safely
If you want to try Cloud Rebuild, you’ll need a device enrolled in the Windows Insider Program’s Canary or Experimental channel. Keep in mind: Canary builds can be unstable, and this one will erase all data if you run the tool. Do not test on your daily driver unless you have a full backup you trust.
Here’s a safe testing path:
- Enroll a spare PC or a virtual machine in the Windows Insider Program. Go to Settings > Windows Update > Windows Insider Program, choose the Canary channel, and install Build 26300.8772.
- Ensure your device has an internet connection available before reboot. Wi-Fi credentials must be saved in Windows, or use a wired connection. Cloud Rebuild needs to download around 4–5 GB, so a metered connection will be problematic.
- Boot into WinRE. You can do this by holding the Shift key while clicking Restart in the Start menu, or by repeatedly interrupting the boot process to trigger Automatic Repair. Navigate to Troubleshoot > Cloud Rebuild.
- Follow the prompts. The tool will confirm your actions, warn about data loss, and then begin downloading. The PC may reboot several times.
After the process completes, you’ll land at the Windows Out-of-Box Experience (OOBE), just as with a fresh installation. You’ll need to go through setup, sign in with a Microsoft account, and reinstall apps.
Back up everything before starting. Even though you’re testing, you don’t want to lose personal data accidentally. Use File History, OneDrive, or a third-party backup tool to save an image of your system. Cloud Rebuild offers no option to keep files—it’s an all-or-nothing wipe.
For IT pros, now is the time to provide feedback through the Feedback Hub. Microsoft is expressly collecting input on the feature’s reliability, driver compatibility, and download times. If your organization relies on custom recovery solutions, submit your concerns so the company can shape the final implementation.
What to watch next
Cloud Rebuild is still in its infancy, and the “Experimental” tag means it could be months or years before it lands in stable Windows 11. The immediate next step is for Microsoft to gauge Insider telemetry and decide whether to promote it to the Dev or Beta channels. If feedback is positive, expect a slow rollout, possibly first to consumer editions of Windows 11. Enterprise editions will likely get controls to disable or redirect the feature.
Rival platforms have proven that cloud recovery works at scale. Now Microsoft must bridge the gap without breaking the complex recovery ecosystem that IT departments rely on. The arrival of Build 26300.8772 signals that cloud recovery is no longer an afterthought for Windows—it’s a foundation for a simpler, USB-free future.