Windows forced 25H2 rollout

Microsoft has started automatically moving unmanaged Windows 11 Home and Pro computers from version 24H2 to version 25H2, which means personal machines outside tools like Microsoft Intune will be upgraded on Microsoft’s schedule, not the owner’s. (bleepingcomputer.com) “Unmanaged” is Microsoft’s dividing line here: a school laptop or company machine under central policy can usually be held back, but a home computer running the standard update settings gets treated more like a phone that quietly jumps to the next release overnight. (bleepingcomputer.com) Version 25H2 is not a brand-new operating system so much as the next yearly Windows 11 release, and Microsoft said on September 30, 2025 that it would ship as an “enablement package,” which is a smaller switch-flip style upgrade built on the same servicing base as version 24H2. (blogs.windows.com) That shared base is why Microsoft can move people faster now: in Release Preview on March 12, 2026, the company was already shipping paired builds for 24H2 and 25H2 side by side, with build 26100 for 24H2 and build 26200 for 25H2. (blogs.windows.com) At the same time, Microsoft is changing how it tests unfinished Windows builds. On April 10, 2026, the company said the Windows Insider program will center on a new Experimental channel for features still in motion and a refreshed Beta channel for features planned to ship in the coming weeks. (blogs.windows.com) The Experimental channel adds something Windows testers have wanted for years: a Feature flags page that lets them turn specific test features on or off, instead of waiting for Microsoft’s random rollout bucket to decide what appears on their machine. (blogs.windows.com) Microsoft also said most testers will now see build tracks labeled 25H2 or 26H1, and the Experimental channel gets a “Future Platforms” option for people who want code that is even earlier and not tied to a retail Windows release. (blogs.windows.com) The odd part is timing: even while Microsoft said it is ending gradual feature rollouts in Beta, the April 10 Beta build post for build 26220.8165 still described features arriving first to people who turn on “get the latest updates as they are available,” which shows the old rollout machinery is still visible during the transition. (blogs.windows.com) That same Beta track is already carrying fixes that matter outside the test crowd. On April 3, 2026, Microsoft said build 26220.8148 fixed a sign-in problem affecting some apps and improved startup app launch performance after boot. (blogs.windows.com) The more urgent fix landed on March 21, 2026 as update KB5085516. Microsoft said the patch repaired a bug introduced on or after March 10 that could show a false “no Internet” message and block Microsoft account sign-ins in apps like Microsoft Teams Free and OneDrive. (support.microsoft.com) Microsoft also said KB5085516 is cumulative, which means it bundles earlier security and non-security fixes, and devices with “Get the latest updates as soon as they’re available” turned on receive it automatically once the earlier March update is already installed. (support.microsoft.com) Put together, the message is simple: Microsoft is treating Windows 11 more like a continuously serviced platform, where consumer machines get pushed onto the newest yearly branch and serious compatibility testing moves earlier into Insider channels with finer-grained feature controls. (bleepingcomputer.com) (blogs.windows.com)