Microsoft has released Windows 11 Insider Preview Build 26220.8575 to testers in the Beta Channel on June 8, 2026. This update brings a highly requested feature—repeatable pause extensions for Windows Update—while also officially confirming a new Beta channel fork for the upcoming Windows 11 26H1 feature update.

The build arrives as both the Dev and Canary channels continue their rapid pace, but this Beta build is particularly notable for two reasons: it hands more control to users over update scheduling for the current 25H2 release, and it signals the early beginnings of the 26H1 feature update cycle. This dual-purpose build highlights Microsoft’s evolving strategy for Windows servicing and Insider rings.

Repeatable Update Pauses Come to 25H2

The headline feature in Build 26220.8575 is the ability to extend update pauses beyond the previous one-time limit. For years, Windows Update has allowed users to pause updates for up to 35 days in Windows 11 Pro, Education, and Enterprise editions. Once that pause elapsed, the system would resume updates automatically, and the pause button would be disabled until updates were installed.

With this build, Microsoft introduces a repeatable pause mechanism. After the initial 35-day pause ends and updates are installed, users can immediately initiate another pause. This cycle can be repeated indefinitely, effectively letting users defer non-security updates for as long as they want, while still allowing critical security patches to install automatically after a set grace period.

The feature is specifically targeted at Windows 11 version 25H2—likely the current production version at this point in 2026. Testers in the Beta Channel running 25H2 will see a new “Pause updates” section in Settings > Windows Update, now accompanied by a “Continue pausing” option that becomes active after a previous pause has expired. This gives users unprecedented flexibility to avoid feature updates or buggy cumulative updates until they are confident in their stability.

Enterprise and IT admins will also benefit from the change. While they have always had granular update control through Windows Update for Business policies, this client-side improvement simplifies update testing and rollback strategies for small businesses and power users who manage their own machines. The build doesn’t change the underlying 35-day maximum per pause, but by removing the one-and-done limitation, it turns the feature from a temporary reprieve into a permanent scheduling tool.

Historically, Windows enthusiasts have resorted to registry hacks or third-party tools to continuously block updates, often disabling the entire Windows Update service. The new official method provides a safe, supported way to pause updates without sacrificing security patches. It strikes a balance between user control and Microsoft’s desire to keep devices protected and up to date.

A New Beta Path for 26H1 Emerges

Perhaps more consequential for Windows enthusiasts is the confirmation of a new Beta channel fork for Windows 11 26H1. The build notes indicate that Insiders who upgrade to Build 26220.8575 are not only testing features for 25H2 but are also being moved onto a separate Beta branch that will culminate in the 26H1 feature release. This is reminiscent of how Microsoft handled the transition from 23H2 to 24H2, where a dedicated Beta (or previously Dev) branch was used to bake the next feature update long before its official launch.

Microsoft typically uses the Beta Channel to preview the final servicing builds for an already-shipped release, while the Dev Channel gets newer platform changes for an upcoming release. The fact that a 26H1 Beta path is being carved out suggests that 25H2 is nearing the end of its feature complete phase and that Microsoft is now shifting its attention to the next major update. Insiders who choose to remain in the Beta Channel will likely need to opt into the 26H1 path to continue receiving new feature builds, while those sticking with 25H2 may only get cumulative servicing updates.

This split also hints at the potential timeline: if 26H1 is already in Beta, it could see a release in the first half of 2027 (hence the H1 moniker), though Microsoft has repeatedly cautioned that feature updates no longer follow strict annual schedules. The existence of a dedicated branch this early, however, points to a significant collection of new features and possibly a platform refresh—perhaps a more polished version of the AI and interface enhancements currently being tested in the Canary Channel.

For Insiders, the transition is straightforward but requires attention. After installing Build 26220.8575, your device will likely be on the new 26H1 development path. Microsoft typically provides a window for Insiders to switch to another channel if they’d prefer to stay on 25H2, but once the transition window closes, the only way to revert would be a clean install. This is standard operating procedure for cross-release channel migrations.

The repeatable pause feature will be instantly available on 25H2, but it’s unclear if it will be backported to older releases or carried forward into 26H1. Given that this is a client-side servicing improvement, it could eventually make its way to all supported versions, but for now it’s exclusive to the 25H2 Beta build.

The build itself is labeled as a “Beta Channel” build, not a “Release Preview” build, meaning it’s not yet in the final testing stage for 25H2. That role is currently held by the Release Preview Channel, which at this point may still be on an earlier 25H2 build. Microsoft’s blog will likely detail the eventual rollout of these features to the broader Windows ecosystem in the coming months.

Additional Improvements and Fixes

Beyond the two big-ticket items, Build 26220.8575 includes the usual crop of fixes and known issues that accompany any Insider flight. Notably, Microsoft has addressed a number of reliability problems with File Explorer, including a crash that occurred when dragging tabs between windows. The taskbar has also received attention, with fixes for the hidden icons flyout occasionally appearing off-screen on multi-monitor setups.

Windows Update improvements are a major theme of this build. In addition to the repeatable pause, the Settings page now provides clearer information about update types and their sizes, and the notification system has been refined to reduce unnecessary restarts. Users can now specify “active hours” more precisely, with a new “manual” mode that lets you block restarts for up to 18 hours without guessing.

Known issues are par for the course with Insider builds, and Build 26220.8575 has its share. The new pause mechanism may not appear for some testers right away, and Microsoft advises waiting up to 48 hours after install for the feature to light up. Some users on the 26H1 path might experience compatibility issues with third-party antivirus software, and a few have reported that the Windows Subsystem for Android is not functioning correctly. As always, Insiders should ensure their feedback is submitted via the Feedback Hub.

The Bigger Picture: Windows Servicing in Flux

Microsoft’s decision to extend update pause controls comes at a time when Windows update cadence and quality are under intense scrutiny. Users and IT pros have long clamored for more flexible deferral options, especially after several high-profile buggy patches that caused blue screens or data loss. While Windows 11’s monthly quality updates have generally been reliable, the cumulative nature means that a single flawed patch can roll up multiple issues. The new repeatable pause gives users a safety net without forcing them to resort to registry hacks or third-party tools.

Simultaneously, the early appearance of the 26H1 Beta path underscores Microsoft’s commitment to a more open development process. By getting next-release feature builds into the hands of Insiders earlier, the company can gather data and feedback on new APIs, UI changes, and under-the-hood improvements months before they hit Release Preview. This model was successfully used for 24H2, where the Beta Channel previewed the update almost six months before its eventual launch.

For developers, an early Beta branch means access to new tools and features for testing app compatibility. For example, if 26H1 includes a new version of the Windows App SDK or updated graphics APIs, developers can start adapting their applications now. It also lets hardware vendors work on drivers and firmware updates well in advance.

How to Get Build 26220.8575

If you’re not already a Windows Insider, you can join the program by going to Settings > Windows Update > Windows Insider Program and linking your Microsoft account. Choose the Beta Channel to receive builds like 26220.8575. Note that once you install a Beta build, you’ll be on the fast track to the next feature update (in this case, 26H1). Make sure to back up your data—Insider builds can be unstable—and leave feedback to help shape the final release.

For those already in the Beta Channel, the update should appear in Windows Update under “Check for updates.” As with any Insider flight, the first restart may take longer than usual.

Conclusion

Build 26220.8575 is a significant milestone for Windows Insiders. The repeatable update pause for 25H2 addresses a long-standing user request and signals that Microsoft is listening to feedback about update autonomy. At the same time, the new 26H1 Beta path sets the stage for the next major chapter in Windows 11’s evolution, promising fresh features and improvements that will be tested and refined with the help of the Insider community. As the lines between servicing and feature releases continue to blur, builds like this one remind us that Windows remains a living, breathing platform—and Insiders are at the heart of its development.