Microsoft has quietly pushed this year’s Windows 11 annual feature update — version 25H2 — into the Release Preview channel, and for most up-to-date PCs the actual work is already done: Microsoft shipped the bulk of the code over the last several months and the public upgrade is simply an enablement package that flips features on. This means the visible upgrade will often feel like a regular Windows Update and — in many cases — will be finished after a single restart. (blogs.windows.com)
Windows feature updates have been evolving away from the old “big rebase” model toward a shared‑servicing approach. Microsoft stages feature code in monthly cumulative updates (LCUs) for the current servicing branch (24H2 in this case) and keeps those features disabled until the company publishes an extremely small enablement package (eKB) to flip the staged functionality on. That is exactly how 25H2 is being distributed: most updated systems already contain the necessary binaries, and the eKB simply activates them. The Windows Insider blog confirms the Release Preview availability and that 25H2 will be delivered as an enablement package (Build 26200.5074 in Release Preview). (blogs.windows.com)
Why this matters practically: the upgrade experience is designed to be fast and low‑impact for PCs that were kept current — fewer gigabytes to download, shorter reboot windows, and less disruption for users and IT. That’s deliberate: Microsoft now treats version labels largely as feature‑activation milestones rather than wholesale rebuilds of the OS.
Key themes in 25H2:
Critical items for IT to validate now:
The practical advice is straightforward: pilot widely, verify compatibility for key line‑of‑business workflows, and use Microsoft’s configuration controls to manage where and when staged features become visible to your users. With careful preparation 25H2 should deliver meaningful day‑to‑day improvements — fast installs, better recovery, and smarter search — while minimizing the disruption that historically came with annual Windows feature updates.
Source: ITC.ua Windows 11 25H2 is already on your PC, but you don't know it
Windows feature updates have been evolving away from the old “big rebase” model toward a shared‑servicing approach. Microsoft stages feature code in monthly cumulative updates (LCUs) for the current servicing branch (24H2 in this case) and keeps those features disabled until the company publishes an extremely small enablement package (eKB) to flip the staged functionality on. That is exactly how 25H2 is being distributed: most updated systems already contain the necessary binaries, and the eKB simply activates them. The Windows Insider blog confirms the Release Preview availability and that 25H2 will be delivered as an enablement package (Build 26200.5074 in Release Preview). (blogs.windows.com)Why this matters practically: the upgrade experience is designed to be fast and low‑impact for PCs that were kept current — fewer gigabytes to download, shorter reboot windows, and less disruption for users and IT. That’s deliberate: Microsoft now treats version labels largely as feature‑activation milestones rather than wholesale rebuilds of the OS.
What Microsoft shipped (high level)
25H2 is best described as polish, manageability, and AI‑surface rollout rather than a major UI overhaul. The Release Preview build series sits in the 26200 code line (some Release Preview snapshots are reported as Build 26200.5074) and is intended for pilot validation before a broader rollout later in the second half of the year. Expect the wider deployment to accelerate in September, though Microsoft stages features by telemetry and device capability. (blogs.windows.com)Key themes in 25H2:
- Enablement package delivery model — quick activation if your device is current. (blogs.windows.com)
- Incremental UX polish — tidier context menus, taskbar/hover animation refinements, Start and File Explorer tweaks.
- Expanded AI surfaces — Click‑to‑Do, File Explorer AI actions, semantic/“natural language” search and an AI agent in Settings for Copilot+ devices. (windowscentral.com, learn.microsoft.com)
- Manageability and cleanup — removal of legacy components (PowerShell 2.0 engine and WMIC), plus new policies for administrators.
New and changed features: what you'll actually notice
The 25H2 release is a collection of targeted improvements that impact daily workflows. Below are the core user‑facing additions and where they matter.Start: a more functional, mobile‑aware launch surface
- Mobile sidebar (Phone companion in Start): Start can show a collapsible panel that surfaces a connected phone’s battery, messages, calls, photos and recent notifications. It’s built on Phone Link technology and does not replace Phone Link; it’s a lighter, glanceable companion inside Start. The feature is rolling out gradually and requires Phone Link updates and appropriate connectivity (Bluetooth LE for iPhone, Wi‑Fi for Android). (support.microsoft.com, techtrickz.com)
- New Start layouts and categories: The All apps area gains Category, Grid, and List views. Category view automatically groups apps into logical buckets (Productivity, Games, Utilities, etc.), and users can choose to hide the Recommended feed and show more pinned apps. This is aimed at reducing friction when you have many installed programs. The redesigned, scrollable Start has been tested in Insider channels and is making its way to Release Preview / staged rollouts. (windowslatest.com, theverge.com)
Settings and search: cards, an AI agent, and semantic search
- Settings “cards” and a smarter Home: Settings now surfaces concise cards at the top of the app with device summary information (processor, RAM, storage, GPU, connection and security state). The layout is meant to make essential diagnostics and actions discoverable at a glance. (pureinfotech.com)
- AI agent in Settings (Settings Mu): An on‑device agent uses a compact Mu model to interpret plain‑English queries and recommend actions or apply them with user consent. This functionality is initially gated to Copilot+ PCs and is subject to region and hardware requirements. IT organizations can control the agent via Group Policy / MDM CSP. Microsoft’s documentation describes configuration options and privacy/Responsible AI steps taken for the agent. (learn.microsoft.com, windowscentral.com)
- Semantic (natural‑language) file search: Windows Search/Copilot is gaining semantic indexing so you can search for files by content and intent rather than exact filenames—for example, “presentation for the city council” could find the correct PowerPoint even if the filename is different. This capability has been tested on Copilot+ hardware and is being widened selectively. Expect hardware, licensing and indexing limits initially. (theverge.com, techradar.com)
AI actions, Click‑to‑Do, and File Explorer
- Right‑click “AI actions”: Context menus gain AI tasks — describe an image, summarize a document, or convert a table into Excel with a single menu action. Some of these actions are local, while others will require Copilot+ hardware, Microsoft 365 / Copilot licensing, or cloud fallbacks according to feature gating.
- File Explorer AI tools: Quick image edits (background blur/remove objects), document summarization, and improved Home view / recommended cards are being staged. These are designed to reduce app‑switching and accelerate routine file work. Some actions require NPU acceleration or a Copilot+ license.
Quick Machine Recovery (QMR)
- Resiliency upgrade: Quick Machine Recovery (QMR) is a recovery feature that lets a device enter WinRE, connect to Windows Update, look for remediations and apply them — automatically where allowed. QMR is a “best‑effort” cloud remediation process intended to dramatically reduce manual recovery work after boot failures. It can be configured, tested in a simulated mode, and controlled via policies. Microsoft’s Learn documentation explains the detection, cloud remediation and auto‑remediation flows in detail. (learn.microsoft.com, techcommunity.microsoft.com)
Enterprise and IT: what to validate and prepare for
For IT teams the 25H2 delivery model is a mixed blessing: it greatly reduces reboot and bandwidth impact for upgrade campaigns, but because features are staged over months and gated by server‑side controls, two identical machines might not show the same behavior at first. The Release Preview push signals readiness for pilot testing, not a mass rollout.Critical items for IT to validate now:
- Confirm build and delivery path: Verify the preview build (Release Preview reports Build 26200.5074 in early snapshots) and confirm how you’ll expose the eKB (WUfB, WSUS, or user‑initiated seeker). Check Settings → System → About or run winver. (blogs.windows.com)
- Script and automation compatibility: 25H2 removes legacy components such as PowerShell 2.0 and phases out WMIC from shipping images. Any scripts, installers, or monitoring tools that rely on these must be updated to PowerShell 5.1 / PowerShell 7+ or to PowerShell CIM/WMI cmdlets. Test scripts in a controlled lab before mass rollout.
- Agent and Copilot+ gating: Many AI features depend on Copilot+ hardware and/or Microsoft 365 licensing. Inventory which devices are Copilot+ capable and plan rollout rings accordingly.
- Quick Machine Recovery policy & test: QMR can be life‑saving for wide scale outages, but it involves network access and cloud remediation. Configure and test QMR in a pilot group; use the test mode to simulate issues before enabling auto‑remediation in production. Documentation provides reagentc commands and CSP settings. (learn.microsoft.com, techcommunity.microsoft.com)
- Feature gating and telemetry: Because Microsoft stages features server‑side, don’t rely on a single build number to predict feature availability. Use telemetry and incremental rings to validate actual feature presence across hardware profiles.
- Build a pilot group (5–10% of fleet) with representative hardware and software.
- Capture full system images / VM snapshots for rollback.
- Verify LOB app functionality, AV/endpoint agent behavior, and driver compatibility.
- Test scripts for WMIC/PowerShell v2 calls and migrate where required.
- Configure and simulate Quick Machine Recovery in test mode.
- Monitor stability, telemetry and user experience over 1–2 weeks before broader rings.
Deployment details for end users and admins
- If you’re in the Release Preview Channel and your device meets hardware requirements, you can “seek” the update via Settings → Windows Update: the 25H2 eKB will appear as an optional preview offer. ISOs will be posted for clean installs to the Insider ISO page shortly after Release Preview. Commercial customers can validate via WUfB/WSUS and Azure Marketplace images will follow. (blogs.windows.com)
- If you want to delay the installation on a particular PC, use Pause updates to defer cumulative patches (including the eKB) for up to seven weeks; after that Microsoft may force install cumulative updates that include 25H2. For broad administrative control, use Windows Update for Business ring policies.
- How to check if your PC already has 25H2 enabled: run winver or go to Settings → System → About; the enablement package will flip the version label and Build string when applied. If you’re fully patched on 24H2, the package download and activation will usually be very small.
Security, privacy and risk analysis
25H2 introduces both helpful resiliency and new surface areas that deserve scrutiny. Below is a risk‑aware breakdown.Strengths and benefits
- Minimized disruption: eKB model shortens reboot windows and reduces large downloads for most users. That’s particularly valuable for remote or bandwidth‑constrained fleets.
- Improved recovery: QMR can drastically reduce mean time to repair for boot‑blocking failures, especially in mass incidents. Properly configured, it reduces manual recovery labor. (learn.microsoft.com)
- Modernized admin surface: Removing deprecated engines (PowerShell v2, WMIC) reduces legacy attack surface and encourages migration to supported tooling. New Group Policy/MDM CSPs give admins cleaner control over inbox app provisioning.
- On‑device AI & semantic search: When running locally on a Copilot+ NPU, semantic search and agents reduce the need to leak file contents to the cloud — in many cases these AI models operate on‑device. Microsoft documents privacy safeguards and on‑device model execution where applicable. (learn.microsoft.com, theverge.com)
Risks and unknowns
- Telemetry and staged enablement inconsistency: Because features can be turned on server‑side, reproducibility across devices and lab tests can be uneven. That complicates validation for large fleets where behavior must be deterministic. Test widely and monitor telemetry.
- QMR cloud interactions: QMR’s remediation process requires network access and the device may upload diagnostic state to Windows Update; admins must review privacy policies and control QMR via CSPs for enterprise deployment. It’s a powerful tool but one that must be managed. (learn.microsoft.com, techcommunity.microsoft.com)
- Legacy compatibility breakage: Automated removal of PowerShell v2 and WMIC may break older installers, scheduled tasks or monitoring scripts. Inventory and migrate scripts before mass rollout.
- Feature dependence on hardware and licensing: Many AI features are gated by Copilot+ hardware or Microsoft 365/Copilot licenses; users on older devices will not see the same experience and documentation should reflect that. (theverge.com, techradar.com)
- Unverifiable/ambiguous claims: Some press or community writeups suggest things like “ability to run apps on your PC that you started on your phone” as a universal feature. In practice, the Start phone panel provides a quick resume or shortcut to Phone Link activities and can surface “recent” mobile content; it does not magically turn every mobile app into a native Windows app. Treat those broader claims as functionality ambivalence until a feature is explicitly documented by Microsoft for all platforms. Flagged as partially unverifiable or overstated in some summaries.
How to prepare: checklist for power users and small IT teams
- Keep devices fully updated with monthly LCUs on 24H2 before applying 25H2; that makes the eKB install as light and fast as possible.
- Run winver or Settings → System → About to check your build string and confirm when the 25H2 label appears. (blogs.windows.com)
- Inventory scripts and scheduled tasks for WMIC/PowerShell v2 calls; update to modern PowerShell cmdlets or PowerShell 7+.
- If you manage recovery/backup policies, test QMR in test mode and document rollback options for any forced remediation. (learn.microsoft.com)
- For privacy‑conscious deployments, review QMR cloud interactions and configure policies to match organizational governance before enabling auto‑remediation broadly. (techcommunity.microsoft.com)
Conclusion and bottom line
Windows 11 25H2 is not a revolution; it’s the next logical step in Microsoft’s servicing model: staged features, smaller activation packages, and a focus on everyday polish plus tighter AI integration for supported hardware. For end users the headline is simple: if you’ve kept Windows 11 updated, 25H2 is already mostly on your device — turning it on will often be fast and unobtrusive. For IT professionals, the model reduces downtime but shifts the validation focus from wholesale reimaging to feature activation testing: confirm build numbers, migrate legacy management scripts, pilot Quick Machine Recovery safely, and plan for hardware/license gating of AI features.The practical advice is straightforward: pilot widely, verify compatibility for key line‑of‑business workflows, and use Microsoft’s configuration controls to manage where and when staged features become visible to your users. With careful preparation 25H2 should deliver meaningful day‑to‑day improvements — fast installs, better recovery, and smarter search — while minimizing the disruption that historically came with annual Windows feature updates.
Source: ITC.ua Windows 11 25H2 is already on your PC, but you don't know it