Microsoft pushed out Windows 11 Insider Release Preview builds 26100.8728 and 26200.8728 to testers on June 12, 2026, delivering a suite of recovery and update management features that promise to reshape how users handle system failures. The rollout arrived alongside Canary-era build 28000.2333, marking a rare triple-channel update day. Windows Insiders in the Release Preview channel—split between the imminent 24H2 and the next-generation 25H2—now have access to point-in-time recovery, refined update pause controls, and a handful of usability tweaks that inch closer to final release quality.
These builds represent the final stretch before 24H2’s general availability and lay the groundwork for the 25H2 feature update expected later this year. Microsoft’s decision to test recovery improvements across both versions signals the company’s commitment to shoring up Windows 11’s resilience, a move that likely stems from user feedback and telemetry data highlighting the pain of unbootable systems.
Point-in-time recovery: a safety net for the daring
The marquee addition in these builds is point-in-time recovery, a feature that allows users to roll back their entire operating system to a specific snapshot. Unlike System Restore, which only protects system files and registry settings, point-in-time recovery captures the complete state of the OS, applications, and user data. Microsoft has been developing this capability under the name “Windows Recovery” and first teased it in a Build 2025 session on enterprise resilience.
In practice, the feature works by taking scheduled snapshots—daily by default—and storing them on a separate drive or partition. Users can trigger a recovery from the Windows Recovery Environment (WinRE) if the system becomes unbootable, or from within Windows if the OS is still functional but misbehaving. The recovery process itself is designed to be fast, leveraging differencing technology to avoid duplicating unchanged data. Early testing shows a 64 GB snapshot completing in under four minutes on NVMe storage, with restoration taking roughly the same time.
Microsoft has baked the feature directly into the Settings app under a new “Recovery” hub. There, users can view available snapshots, adjust storage allocation, and manage retention policies. The interface displays each snapshot with a timestamp and a user-assignable label, making it easy to identify a known-good state. For enterprises, IT admins can control snapshot frequency and storage targets via Group Policy or MDM, integrating with existing backup strategies.
One nuance: point-in-time recovery requires at least 30 GB of free space on the target drive. The system warns users if space runs low and automatically deletes the oldest snapshots to make room. Microsoft has also implemented integrity checks to verify snapshot health before restoration, reducing the risk of recovering to a corrupted state. This addresses a long-standing gripe with System Restore, which could sometimes fail silently.
Update pause gets a meaningful upgrade
The other headline feature in 26100.8728 and 26200.8728 is a revamped update pause mechanism. Windows 11 already allowed users to pause updates for up to 35 days, but the process was binary: updates were either fully enabled or fully paused, with little granularity. The new builds introduce a tiered pause system that lets users selectively pause different update types—quality updates, feature updates, and driver updates—independently.
A new “Update Pause” page in Windows Update settings now presents three toggle switches, each with its own duration slider. You can, for example, pause feature updates for 60 days while allowing quality patches to flow through, or block driver updates from Windows Update indefinitely while still receiving monthly security fixes. The maximum pause duration has been extended to 180 days for feature updates, catering to power users and small businesses that prefer to defer major OS changes until they’ve been vetted.
Under the hood, Microsoft has decoupled the update pipeline services to respect these granular pauses. This required significant re-architecture of the Windows Update engine, as earlier builds treated all update classifications as a monolithic stream. The change should reduce unintended update reboots and give users more control over their system’s update cadence—something the community has been asking for since Windows 10’s aggressive update schedule.
During the pause period, the system will still download critical security intelligence updates for Microsoft Defender, ensuring endpoints remain protected. The settings page also offers a “catch-up” feature that recaps missed updates when a pause expires, allowing users to install them manually in a batch before the next automatic scan. This is particularly useful for those who’ve paused feature updates and want to review changelogs before committing.
Canary build 28000.2333: a peek at what’s cooking
Alongside the Release Preview builds, Microsoft shipped Canary channel build 28000.2333, which introduces the same recovery and pause features to the bleeding-edge development branch. Canary builds often contain experimental code that may never see the light of day, but the inclusion of point-in-time recovery here suggests the feature is mature enough for mainstream testing. The Canary build also adds an early version of a “Recovery Dashboard” that aggregates system health metrics and predicts failure risks using machine learning—think hard drive SMART data, Windows Event Log anomalies, and update history all funneled into one predictive score.
This dashboard, while clearly a work-in-progress, hints at Microsoft’s broader ambition: proactive system maintenance that alerts users before a crash happens. For now, it’s a Canary exclusive, but the insights gathered will likely shape future iterations of Windows Recovery in consumer builds.
Other notable improvements
Both Release Preview builds squash a long list of bugs. The taskbar no longer flickers when switching virtual desktops with animations enabled, a glitch that had plagued multi-monitor setups for months. File Explorer’s performance when opening folders with thousands of thumbnails has improved dramatically, thanks to thumbnail caching refinements. The Settings app now loads navigation entries asynchronously, reducing perceived launch time by nearly a second on older hardware.
Accessibility sees love too. Narrator’s OCR engine now supports 14 additional languages, and the live captions feature can transcribe audio from any app window, not just system-level audio. This is a boon for users who rely on real-time transcription during video calls or podcasts.
For enterprise IT, two new Group Policy settings arrived: “Specify snapshot storage location” and “Enable predictive recovery alerts.” These policies allow admins to enforce snapshot destinations across fleets and opt into the machine-learning-based failure predictions, even on devices that don’t run Canary builds. It’s a clear signal that Microsoft sees recovery as a differentiator in its Windows 11 Enterprise story.
Known issues and rough edges
No preview build ships without caveats. Microsoft’s release notes flag several known issues:
- Point-in-time recovery snapshots may fail on systems with smaller EFI system partitions (less than 100 MB). The workaround is to manually resize the EFI partition using third-party tools.
- Some third-party antivirus software may flag the snapshot creation process as suspicious activity, leading to performance degradation or block messages. Microsoft recommends adding Windows Recovery to exclusions.
- The new update pause toggles do not yet appear for Windows Server Insider builds, even though they share the same codebase.
- On ARM64 devices, restoration from a snapshot sometimes results in boot configuration issues if the system was originally installed in a dual-boot scenario.
Insiders are encouraged to file feedback via the Feedback Hub, as these issues are under active investigation.
Which Insider channel is right for you?
With so many builds flying around, clarity is key. Here’s a quick breakdown:
| Channel | Build | Version | Key Focus |
|---|---|---|---|
| Release Preview | 26100.8728 | 24H2 | Final validation before GA |
| Release Preview | 26200.8728 | 25H2 | Early feature preview for next feature update |
| Canary | 28000.2333 | Pre-release platform | Experimental features, recovery dashboard |
If you’re on the Release Preview channel and want stability, 24H2 build 26100.8728 is your best bet. Those who opt into 25H2 via the “Windows Insider Program” toggle will receive the same features but with a newer codebase that may have unforeseen bugs. Canary remains the wild west—expect crashes and broken drivers, but you’ll get first access to radical innovations.
How to get the builds
To install these builds, navigate to Settings > Windows Update > Windows Insider Program, select the appropriate channel, and check for updates. A clean installation using official ISO files is also an option, though Microsoft hasn’t yet published ISOs for these specific revision numbers. The updates are cumulative, so devices running previous Release Preview builds will download only the delta.
The bigger picture: resilience as a pillar of Windows 11
Point-in-time recovery isn’t just a feature checkbox. It represents a strategic shift for Windows, which has historically lagged behind macOS’s Time Machine and Linux’s Btrfs snapshots in system-level backup. By baking this capability directly into the OS—and tying it to Windows Update’s cadence—Microsoft is acknowledging that modern PCs need more than traditional restore points. The integration with Group Policy and the machine-learning-powered predictive alerts signal a long-term investment in endpoint resilience, a domain that has belonged to third-party vendors like Acronis and Veeam for decades.
The granular update pause is another olive branch to power users. Since Windows 10, the tension between forced updates and user autonomy has simmered. While the new toggles don’t give absolute control—critical Defender updates still flow—they inch closer to the flexibility that Linux distributions offer. It’s a pragmatic compromise: keep systems secure while respecting user workflows.
Looking ahead, the 25H2 feature update will likely ship these recovery and pause features alongside other enhancements still under wraps. The Canary build’s recovery dashboard hints at a future where Windows not only recovers from failure but avoids it altogether. Microsoft’s Azure-connected telemetry could enable a cloud-based failure prediction service, alerting users to imminent hardware or software issues before they spiral into data loss.
For now, Insiders have a solid preview build to test. If you rely on your PC for critical work, the point-in-time recovery alone is worth an upgrade to the Release Preview channel—provided you can tolerate the occasional quirk. As always, back up your data before installing pre-release software, even if the build’s marquee feature aims to make backups redundant.
Microsoft has not announced a date for 24H2’s general availability, but with Release Preview builds stabilizing, a broad rollout within the next 30 to 60 days seems plausible. The company typically times these releases to align with Patch Tuesday cycles. As for 25H2, expect a public preview to open in the fall, with final code landing in early 2027. In the meantime, the Insider community will keep pounding on these builds, uncovering bugs and shaping the recovery tools that millions will eventually depend on.