Microsoft Tests 'Cloud Rebuild' Windows 11 Recovery in Insider Preview

Microsoft has introduced Cloud rebuild, a new Windows 11 recovery option that restores a PC to a clean, known-good state by performing a full OS reinstall. The company describes it as working even when Windows won't boot.

According to Microsoft's documentation, the key difference from the existing Reset this PC flow is where the recovery bits come from: Cloud rebuild downloads both the target Windows image and the device's drivers from Windows Update. As a result, the device comes back fully functional without USB media, without a custom image, and without depending on the integrity of the currently installed operating system.

Traditional clean-reinstall recovery often depends on prepared USB media, a maintained custom image, or a bootable OS — all of which can be unavailable exactly when a device has failed. By pulling the image and drivers from Windows Update, Cloud rebuild removes those dependencies and can run from the Windows Recovery Environment even when the installed OS is unbootable.

For managed fleets, the post-rebuild flow is the notable part. After the rebuild completes, the device enters the out-of-box experience (OOBE), and Microsoft Entra–joined, Intune-managed devices registered with Windows Autopilot can re-provision automatically — Intune redeploys assigned apps and policies, Backup for Organizations restores settings, and files are available via OneDrive once the user signs in.

In the current Insider preview, Cloud rebuild can be started by a user with physical access from the WinRE troubleshooting menu, or by a local administrator from an elevated command prompt in Windows. Microsoft says remote initiation from an enterprise endpoint management solution such as Intune will arrive in a later release.

From WinRE, the high-level flow described by Microsoft is:

1. Enter the Windows Recovery Environment (automatically after repeated boot failures, or via Settings > System > Recovery > Advanced startup).
2. On the Choose an option screen, select Troubleshoot, then Cloud rebuild.
3. Connect to the network — Ethernet connects automatically; for Wi-Fi, select a WPA-Personal network and enter the passkey.
4. Cloud rebuild contacts Windows Update to determine the target build and download networking drivers.
5. Review the target state (build, edition, language), acknowledge the data-loss warning, and select Continue.
6. The device moves through preparation, download, and install phases, restarting one or more times, then boots into OOBE.

Note on the menu path: the Insider release notes describe reaching the feature via Troubleshoot > Recovery and uninstall > Cloud rebuild, while the dedicated documentation page lists Troubleshoot > Cloud rebuild directly. Which path is current should be confirmed against the latest build before relying on it.

Microsoft lists the following requirements for Cloud rebuild in the preview:

• The device is running Windows 11 with a healthy Windows Recovery Environment (verify with reagentc /info from an elevated prompt).
• The manufacturer has included a compatible networking driver in WinRE.
• The device can reach the internet from WinRE via wired Ethernet or a WPA-Personal Wi-Fi connection.
• The device meets Windows 11 minimum hardware requirements.

Microsoft's documentation calls out two common error codes during the preview:

• 0x800704C6 — no network connection. Cloud rebuild needs internet access to download the image and drivers; only WPA-2 Personal Wi-Fi is supported in WinRE.
• 0xc1900200 — the device doesn't meet Windows 11 minimum hardware requirements, or a required driver is missing from Windows Update. The most common cause is that TPM is not enabled.

For the TPM-related failure, Microsoft suggests enabling TPM in firmware (sometimes labeled PTT, fTPM, or Security Device) and confirming via tpm.msc that the status reads 'The TPM is ready for use.' If it persists, a missing driver is the likely cause.

If Cloud rebuild fails, logs can be collected from X:\$Windows.~BT\Sources\Panther, X:\Windows\Logs\MoSetup, and X:\Windows\Logs\Rebuild, then reported via Feedback Hub under Recovery > Cloud rebuild. If the device won't boot, fallback options include a Recovery Drive, reinstalling with installation media, or manufacturer-provided recovery media.

Cloud rebuild should not be confused with Quick Machine Recovery, a separate, already-released feature (available on Windows 11 24H2 build 26100.4700 or later). Quick Machine Recovery builds on Startup Repair and uses a connected WinRE to scan Windows Update for remediations to automatically recover from widespread boot failures.

In short, they solve different problems: Quick Machine Recovery auto-remediates boot failures without wiping the device, while Cloud rebuild performs a full clean reinstall that erases local data.

• A general availability date and the target shipping Windows version outside Insider preview have not been stated.
• Whether a specific Windows 11 baseline (24H2/25H2/26H2) is required is not spelled out — docs only say 'the device is running Windows 11.'
• The exact elevated command-prompt syntax to initiate Cloud rebuild was not shown in the published docs.
• Remote initiation via Intune is described as coming in a later release, with no date given.

Cloud rebuild introduces a media-free, cloud-sourced clean reinstall path for Windows 11 that can run from WinRE even when the OS won't boot, but it is preview-only and erases local data.

Security: Restores a device to a clean, known-good state, which can help recover from a compromised or corrupted OS install.

Privacy: Removes all locally stored files, accounts, apps and settings; cloud-stored data such as OneDrive is unaffected.

Microsoft is previewing Cloud rebuild in Windows 11 Insider Build 26300.8772 — a recovery option that reinstalls the OS and drivers from Windows Update, works even when Windows won't boot, and re-provisions managed devices via Autopilot and Intune.