Windows 11 25H2 Update Arrives with Start Menu Overhaul and Phased Rollout

Windows 11’s next annual refresh is officially on the doorstep: Microsoft’s 25H2 update has reached final pre-release builds and is being distributed to partners and insiders, but the real headline for many users may be the overhauled Start menu — a change already living, dormant, in Windows 11 24H2 and rolling out separately via phased updates.

Background / Overview​

Microsoft has shifted Windows 11’s annual cadence into a model that often stages features inside an existing servicing branch and then flips them on with an enablement package. That approach — used historically in Windows releases such as 22H2 — keeps major engineering work inside a shared branch while letting Microsoft ship a small, fast-apply package that rebrands a device to the new version number. For 25H2, Microsoft confirmed the enablement-package delivery model and has been previewing builds in the Release Preview Channel.
The practical outcome: Windows 11 version numbers (24H2 vs 25H2) can represent the same underlying codebase, with 25H2 principally toggling features that were integrated earlier into 24H2 but held disabled for broader rollout. This is why the 25H2 rollout feels lightweight — small downloads, a single reboot and minimal disruption for most users.
At the same time, one of the most conspicuous user-facing changes — the redesigned, single-page Start menu that lets users hide Microsoft’s “Recommended” section — has been seeded into 24H2 builds and will be enabled gradually, meaning some machines running 24H2 may see the new Start menu before others who jump straight to 25H2. Multiple outlets and insider releases have shown the Start redesign in testing, and Microsoft’s rollout strategy for 25H2 explicitly calls out phased activation for some features.

---

What’s happening now: RTM builds, ISOs and the timing​

Microsoft’s Release Preview and Insider channels have been receiving 25H2 builds through late summer and early autumn previews. Independent reports indicate build numbers in the 26200 series — specifically a build that has appeared as the candidate RTM/GA image on Microsoft servers — signaling general availability is imminent. Official ISOs for the 25H2 build have been made accessible to testers and partners, and industry reporting suggests the final RTM candidate is circulating as build 26200.6584.
What this means in real terms:

• OEMs can begin shipping machines with the 25H2 image pre-installed.
• Enthusiasts and IT teams can download ISO media if they prefer manual installs or validation.
• The public feature rollout will be gradual: 25H2 will appear as an optional “seeker” in Windows Update for Release Preview Insiders and then be offered more broadly in the weeks following GA.

Microsoft has historically moved major updates into general distribution around late September or October when an enablement package is ready; with ISOs and release-candidate builds circulating now, that expected window looks consistent for 25H2 this cycle.

---

The Start menu overhaul: why it matters​

The most visible and user-impacting change in this cycle is the Start menu redesign. After years of criticism that Windows 11’s Start was constrained and cluttered with a prominent “Recommended” area, Microsoft has rethought the layout into a larger, single-scroll page that places pinned apps and the apps list in closer proximity, gives new layout choices (grid, category or list views) and, importantly, introduces a toggle to hide the Recommended content entirely. This gives users more control and reduces Microsoft’s “nudges” and promotional placements inside Start.
Key user-facing elements of the redesign:

• A single, vertically scrolling Start page combining Pinned, Recommended and All apps into a unified view.
• New layout modes: grid (alphabetical), category grouping, and a compact list.
• Larger pin capacity and adaptive columns depending on screen size.
• A user-accessible option to hide the Recommended section (or reduce its prominence) from Settings or via enterprise policy.

Because Microsoft has already placed the updated Start code into the 24H2 servicing branch, the company can flip the flag to make the new menu appear on 24H2 devices via cumulative servicing and a phased rollout — which explains the curious situation where a user on 24H2 might see the new Start before another user who freshly installs 25H2. That staggered activation is a deliberate part of Microsoft’s deployment strategy to limit risk and iteratively monitor telemetries and feedback.

---

What else is in 25H2 (and what's being removed)​

25H2 is a “small-but-not-empty” update. Its public messaging and release notes make clear the release is enablement-first, but it also bundles a few curated changes:

• Feature activations originally staged in 24H2 (Start menu redesign, UI tweaks and personalization settings).
• Removal of legacy components such as PowerShell 2.0 and the WMIC command-line tool.
• Enterprise-focused controls allowing IT admins to remove select preinstalled Microsoft Store apps via Group Policy/MDM on Enterprise and Education SKUs.
• Ongoing “under the hood” tweaks: security hardening, servicing-stack updates and incremental fixes that prepare Windows for the next servicing cycle.

These are meaningful for specific groups (IT admins, organizations with legacy-dependency concerns), but they are not the kind of platform overhaul that changes day-to-day responsiveness or dramatically rewrites core Windows subsystems.

---

Performance: reality check on claims of uplift​

Expectations for a big performance bump from 25H2 have been tempered by engineering facts and independent tests. Because 25H2 is implemented as an enablement package on the same servicing branch, its changes rarely include wholesale kernel or scheduler rewrites that materially influence CPU-bound workloads.
Independent benchmark suites that compared preview builds of 25H2 and 24H2 reported no measurable performance advantage for 25H2 on average; in some CPU-heavy test suites the two Windows builds were essentially identical, and Linux distributions continued to outperform both in certain multi-threaded creator workloads. In short: 25H2’s primary value is manageability and feature activation, not raw performance gains for compute-heavy tasks.
Microsoft is aware of performance criticisms and continues to collect telemetry and user feedback to iterate on slow or sluggish experiences, but those efforts are ongoing and are not functionally tied to the enablement flip itself. Expect targeted fixes in monthly updates rather than a single “silver-bullet” speedup in 25H2.

---

The rollout paradox: why some 24H2 users will see 25H2 features first​

This release cycle creates an unusual migration paradox:

• The feature code for the Start menu and other improvements was integrated into 24H2 earlier and kept dormant.
• 25H2 switches those features on with an enablement package, but Microsoft also uses incremental cumulative updates and controlled feature-flighting to enable features on 24H2 directly.
• As a result, a particular user’s device may see the Start redesign via Windows Update while staying at version 24H2, depending on the phased roll pattern, device configuration, and signals Microsoft uses to gate activation.

In practice this means the “upgrade” to 25H2 is more about the version label and support timelines than an obvious suite of new capabilities for end users. The most visible change — Start — might land for a subset of 24H2 users weeks before wide reaching 25H2 adoption completes.

---

Support lifecycle and enterprise implications​

One technical advantage to installing 25H2 is an extended servicing window: devices that move to the newly minted version receive a full support lifecycle tied to that specific release, which can be important for organizational patch planning and compliance calendars.
For consumer users, the practical benefit is small: if you’re already on 24H2 and are content with how updates are applied, you’ll continue to receive monthly security and quality updates. For enterprises, the 25H2 enablement package simplifies mass deployment and reduces image churn, while giving extra flexibility in managing preinstalled apps and legacy removal.

---

Preparing for the update: a short checklist​

• Check compatibility: run the PC Health Check and confirm your device meets Windows 11 hardware requirements.
• Back up: create a current system image or at least a robust file backup before applying major feature updates or changing OS versions.
• Test on a representative device: IT admins should validate images and Group Policy/MDM behavior against internal apps before broad deployment.
• Monitor phased rollouts: watch Windows Update offerings and the Windows Insider/Release Preview channel messaging to see staged activations for the Start menu or other features.
• Decide on timing: since this is an enablement-style release, there’s little urgency for most users — waiting a few weeks for a gradual rollout is typically sensible.

---

Strengths and opportunities in Microsoft’s approach​

• Less friction: the enablement package model minimizes downtime and the size of the update. For organizations, quicker installs and fewer reboots mean less user disruption and simpler change control.
• Reduced risk profile: phased and targeted activation lets Microsoft observe telemetry and rollback or refine feature rolls before mass exposure.
• User-focused polish: real user control over Start’s Recommended section addresses a long-standing complaint and restores a degree of cleanliness and predictability to the primary launcher experience.

---

Risks, limits and what to watch out for​

• Perception vs. substance: Microsoft’s model produces small, safe updates, but it also makes marketing a challenge; consumers may feel disappointed when a major-number update contains only a veneer of change.
• Fragmentation of experience: phased rollouts and feature flags can create inconsistent UI states across users, making support and documentation trickier for help desks and knowledge base authors.
• Legacy removal surprises: the removal of legacy components like PowerShell 2.0 and WMIC could break custom scripts or tooling in poorly managed environments — organizations should validate automation before upgrading.
• Performance expectations: users seeking a tangible performance uplift for CPU-bound workflows should temper expectations; independent benchmarking shows parity with 24H2 rather than improvement.

---

How this fits into the broader Windows strategy​

25H2’s modest, enablement-focused nature is a deliberate move in Microsoft’s platform lifecycle — prioritize reliability and iterative feature delivery while preparing the stack for future investments (including AI, Copilot features and deeper hardware integration). With Windows 10’s end-of-support date approaching, a low-friction path to the latest Windows 11 version helps drive migration while keeping update disruption to a minimum. The new Start menu is a pragmatic UX win that improves day-to-day usability without destabilizing the platform.

---

Final analysis: who should upgrade and when​

• Casual users: there’s no pressing reason to rush. If you prefer to wait for fully rolled-out features and stability signals, delaying a few weeks is reasonable.
• Power users and enthusiasts: if you want the new Start menu immediately and don’t mind running preview ISOs or checking for phased feature activation, you can get early access via Release Preview builds or by grabbing the official ISOs that are already hosted on Microsoft’s servers.
• IT administrators: validate workloads, test legacy scripts (PowerShell 2.0/WMIC removals), and plan deployment timelines around the support lifecycle extension that comes with 25H2. The enablement package reduces image churn, but you should verify Group Policy and MDM behavior in a pilot ring first.

---

Unverified or evolving claims (caution)​

• Exact rollout timing: while ISOs and release-candidate builds indicate imminent general availability, the final consumer rollout cadence and the exact days when specific devices will see enabled features remain controlled by Microsoft’s phased flighting. Any specific “GA date” reported outside Microsoft’s official channels should be treated as tentative until announced.
• Micro-performance changes: small UI animations or localized responsiveness tweaks may vary by hardware and build; while broad benchmarks show parity, some systems may report perceptible smoothing in specific interactions after feature activation — these are anecdotal and should be verified on representative hardware.

---

Conclusion​

Windows 11 version 25H2 is arriving with the quiet confidence of a mature platform: it’s engineered to be low-friction, low-risk and operationally simple to adopt. The real consumer-facing payoff is the Start menu overhaul — a sensible, user-centered redesign that finally makes it practical to remove the Recommended feed and reclaim Start’s real estate for what matters most.
For most users, 25H2 won’t feel like a dramatic upgrade; it’s less a reimagining and more a tidy roll forward. That’s not a failing — it’s a reflection of Microsoft prioritizing reliability, staged feature delivery and enterprise manageability as the company steers Windows through its annual cadence and the transition away from Windows 10 support. If your priority is immediate access to the refreshed Start menu or you need the extended servicing timeline, prepare and test now; otherwise, the phased rollout means there’s no rush to flip the switch the instant 25H2 appears in Windows Update.

---

Source: TechRadar Windows 11 25H2 update is now imminent – but big Start menu upgrade could arrive on 24H2 first