The important distinction is what must still work. Your installed copy of Windows can be badly damaged, but the Windows Recovery Environment, or WinRE, must remain functional and able to connect to the internet. Microsoft’s documentation therefore supports a useful but qualified promise: Cloud rebuild can rescue an unbootable Windows installation, not every unbootable computer.
What changed—and which update you need
ZDNET’s Lance Whitney identifies the November 2026 Patch Tuesday release, KB5132061, as the update bringing Cloud rebuild to users. Microsoft dates that release to November 10, 2026, with these operating-system builds:
| Windows 11 version | Build in KB5132061 | Editions listed for the update |
|---|---|---|
| 26H2 | 26300.9974 | All editions |
| 25H2 | 26200.9974 | All editions |
| 24H2 | 26100.9974 | Enterprise and Education |
Those edition boundaries describe this particular security update; they should not be read as a blanket statement about every recovery feature on older installations.
There is also an important timing correction. Microsoft Support says Cloud rebuild and data sanitization require the October 2026 non-security update or later for the applicable Windows 11 version. November’s cumulative update is therefore a qualifying route, not the sole starting point. Microsoft’s November release notes also list the October 28, 2026 preview, KB5127936, among the updates incorporated into that release.
For readers preparing a working PC, the practical takeaway is to install the applicable Windows updates before trouble arrives. The instructions below apply to updated Windows 11 systems with Cloud rebuild available—not Windows 10, and not an arbitrary Windows 11 installation simply because it has a recovery menu.
Before clicking anything: protect the data
Cloud rebuild has no “keep my files” option. Microsoft says it reformats the system disk and removes the local user environment. Files already stored in OneDrive or another cloud service are unaffected, but that does not protect documents that existed only on the computer.
Before proceeding:
- Back up important files. If Windows still starts, do this before launching recovery.
- Confirm your cloud copies exist. Treat an unsynced local document as local data, not as a backup.
- Connect the charger or external power supply. Leave the machine plugged in throughout.
- Arrange internet access. Have Ethernet available or know the Wi-Fi credentials.
- Have your BitLocker recovery key accessible. Microsoft says most WinRE recovery options require it when BitLocker is enabled.
- Contact IT for a work or school PC. Recovery policy and restoration arrangements may be centrally managed.
If Windows cannot start and the only copy of an important file is on that PC, stop before approving erasure. The appropriate priority is preserving that data, not making the desktop appear as quickly as possible. A successful Windows reinstall and successful file recovery are different outcomes.
Check the recovery environment while you can
Microsoft Learn specifies three prerequisites: Windows 11 hardware eligibility, a healthy WinRE installation, and a compatible networking driver inside WinRE. Administrators can check whether WinRE is enabled by opening an elevated Command Prompt and running:
reagentc /info
This checks WinRE’s enabled status; it is not a comprehensive test of networking, storage, or the entire rebuild process. A connection that works in ordinary Windows does not, by itself, establish that the recovery environment has the necessary driver.
The resulting planning lesson is straightforward: recovery readiness includes the environment outside Windows, not just the operating system you use every day.
How to start Cloud rebuild
Microsoft documents two entry points. Both lead to the same destructive reinstall process, so starting from the recovery screen does not make it a less disruptive operation.
If Windows still starts
- Open Settings.
- Select System > Recovery.
- Find Rebuild this PC.
- Select Rebuild PC.
- The computer restarts into WinRE and starts Cloud rebuild.
These are the labels in Microsoft’s current support instructions. There is no need to invent an additional confirmation button if the documented sequence does not show one.
If Windows will not start
- Enter Windows Recovery Environment. Microsoft says repeated failed starts can cause the computer to enter it automatically.
- At Choose an option, select Troubleshoot.
- Select Cloud rebuild.
- Allow it to prepare and establish its network connection.
Ethernet connects automatically when a working connection is available. For Wi-Fi, select the network and provide its credentials if prompted. Cloud rebuild then contacts Windows Update to determine the target Windows build and obtain the required networking drivers.
If WinRE itself is inaccessible or cannot support the required connection, Cloud rebuild is not a substitute for those missing foundations. Microsoft’s fallback options include a recovery drive, Windows installation media, or recovery media supplied by the PC manufacturer.
Choose removal or sanitization carefully
Once preparation finishes, the recovery interface offers two approaches. They both remove the existing Windows user environment; their difference is how thoroughly the underlying data is erased.
Remove files: for a PC you are keeping
Remove files is the faster option. It removes local data and reinstalls Windows, but Microsoft warns that specialized recovery software might still recover some information afterward. That warning is about residual-data exposure—not a promise that you can retrieve your files later.
For this route:
- Select Remove files.
- Review the displayed Windows version or build, edition, and language.
- Read and acknowledge the data-loss warning.
- Select Continue to start the rebuild, following Microsoft’s documented flow.
The review screen matters. Check the proposed installation rather than assuming the word “cloud” means an automatic upgrade to whichever Windows release you had in mind.
Remove & sanitize: for a PC leaving your possession
Remove & sanitize asks the storage hardware to erase the targeted data more thoroughly before Windows is installed. Microsoft recommends this route when recycling, returning, or giving away the computer. It can take substantially longer.
On a machine with multiple disks, the selection becomes especially important:
- Windows disk only sanitizes the disk containing Windows and keeps files on other disks.
- All disks sanitizes every disk on the PC and can considerably extend the process.
A single-disk computer does not show that disk-selection screen. Review the summary, confirm the intended targets, and select Sanitize and install. Sanitization cannot be undone.
Microsoft also makes a limitation explicit: Windows requests the hardware’s erase operation and reports its result, but cannot independently verify what the storage device actually did. For organizations with formal erasure obligations, Microsoft advises confirming support with the manufacturer. A completed progress bar should not be treated as independent proof of compliance.
What completion looks like
During the rebuild, Windows moves through preparation, downloading, and installation. Sanitization, when selected, adds its own stage and can leave the computer looking idle for an extended period. The PC may restart several times. Do not manually restart it or disconnect power. Microsoft warns that an interrupted rebuild can leave Windows unable to boot.
Success means reaching Windows setup, also called the out-of-box experience—not simply returning to your previous desktop. Complete setup as you would on a new computer, then restore your working environment:
- Sign in to retrieve files stored in OneDrive.
- Copy back files from other backups.
- Use Windows Backup restoration during setup if you previously configured it.
- Reinstall applications that were not restored.
- Open Settings > Windows Update and install any available updates.
That final step qualifies the idea that Cloud rebuild eliminates all post-recovery updating. It downloads Windows and drivers through Windows Update, but Microsoft still explicitly tells users to check for updates afterward. The sensible expectation is a fresh installation with downloaded drivers—not a guarantee that nothing remains to install.
When Cloud rebuild fails
Microsoft documents several specific failure codes. They help distinguish a fixable prerequisite from a situation requiring another recovery method.
| Error | Meaning | Microsoft’s recommended response |
|---|---|---|
0x8007027F | The device is not connected to power | Plug it in and restart Cloud rebuild. |
0x800704C6 | No internet connection | Connect Ethernet or Wi-Fi, cancel the failed attempt, then return to Troubleshoot > Cloud rebuild. |
0xc1900200 | Windows 11 hardware requirements are not met | Check hardware eligibility; a disabled TPM is a common cause. |
0xc1900224 | A required driver is unavailable from Windows Update | Contact the manufacturer or use manufacturer recovery media or Windows installation media. |
These mappings and remedies come from Microsoft’s Cloud rebuild troubleshooting guidance.
For a TPM-related failure, Microsoft notes that firmware may label the setting PTT, fTPM, or Security Device. Follow the manufacturer’s instructions for the particular computer rather than guessing at firmware options.
A sanitization failure has a separate response screen: retry, skip sanitization, or copy logs to a USB drive. Skipping allows the reinstall to continue without completing secure erasure. Microsoft specifically warns against doing that when transferring or disposing of the PC; use a manufacturer-provided erasure tool instead.
If interruption leaves the machine unable to start, the documented fallback remains external recovery or installation media. Cloud rebuild reduces dependence on the rescue USB—it does not make one obsolete.
How it compares with Windows’ other recovery tools
Cloud rebuild belongs near the end of a troubleshooting sequence. Microsoft recommends trying less disruptive options first, and its recovery guide distinguishes several tools that can sound deceptively similar.
Reset this PC can preserve personal files, although it removes applications and settings. Cloud rebuild does not offer that preservation choice. Its defining combination is a fresh Windows image, drivers obtained through Windows Update, and execution from WinRE without relying on the installed Windows files.
Quick machine recovery, available on Windows 11 version 24H2 or later, addresses repeated startup failures caused by a known widespread problem. When enabled, it can look for and apply a Microsoft-provided fix without resetting the PC or removing files, applications, and settings. It is a targeted repair mechanism, not a clean-install service.
Point-in-time restore, also listed for version 24H2 or later, rolls back applications, settings, and personal files to an available automatic snapshot. Microsoft says these restore points are retained for up to three days. Changes after the selected point are lost. Traditional System Restore differs because it rolls back system changes without rolling back personal files.
A recovery drive remains another route to reinstalling an unbootable machine, but it does not preserve personal files, applications, and settings. Manufacturer recovery media can additionally provide hardware-specific drivers and factory software.
The decision is therefore about both repair and preservation. If a recent update caused the problem, removing that update may be more appropriate than rebuilding. If preserving documents is essential, do not mistake Cloud rebuild for Reset’s file-preserving option.
What administrators should know
Microsoft Learn describes enterprise controls through the Recovery configuration service provider, including permitting or blocking rebuild types and initiating supported remote rebuild operations. There is an implementation caveat: starting Cloud rebuild through a custom Intune OMA-URI configuration is not currently supported because the execution settings must be committed together atomically. Administrators should not equate documented CSP nodes with a ready-made custom-profile deployment recipe.
For appropriately configured Microsoft Entra–joined, Intune-managed devices registered with Windows Autopilot, setup can reconnect the machine to management, redeploy assigned apps and policies, restore settings through Backup for Organizations, and make OneDrive files available after sign-in. Those outcomes depend on the existing management and backup configuration; they are not an automatic recovery of everything formerly stored locally.
The broader value is practical: Cloud rebuild gives users and support teams another route from a damaged installation to a usable Windows system without first preparing installation media. Its usefulness rests on preparation—working WinRE networking, available drivers, reliable power, and recoverable data. Treat it as a well-equipped last resort, not a reason to retire your backups.