Microsoft has begun rolling out Windows 11 version 25H2 to Insiders in the Release Preview channel, and it’s unlike any feature update in recent memory. Instead of a splashy list of new capabilities, this release is a tiny enablement package—no more than a few hundred kilobytes—that flips a switch on features already sitting dormant on your PC—and quietly retires two legacy tools that could break old scripts.

What’s New (and Newly Visible) in 25H2

Make no mistake: if you’ve kept your Windows 11 24H2 PC up to date and toggled “Get the latest updates as soon as they’re available,” you may already have most of these features. 25H2 simply ensures they’re turned on by default for everyone and stamps your system with a new version number that extends its servicing lifetime.

Start menu gets a mobile companion. Once you pair an Android phone via Phone Link, the Start menu gains a side panel with quick access to messages, calls, and photos. It’s unobtrusive—only appears when Phone Link is active—and is clearly designed for people who live between their phone and PC.

Lock screen widgets become customizable. You can now add, remove, and reorder widgets on the lock screen. Weather, sports, traffic, stocks, and even third-party widgets that support a small size can now be arranged to your liking. It’s a small touch, but for those who rely on a glance at the lock screen before signing in, it reduces friction.

The notification clock returns. After a previous update yanked the digital clock from the notification center, user pushback convinced Microsoft to restore it. Now, when you click the date/time on the taskbar, the clock appears above the calendar again. You can still toggle seconds on the taskbar clock if you wish.

Narrator gets smarter. Accessibility improvements include AI-powered image descriptions, a “recap” feature that lets you revisit or copy past screen-reader interactions, and new keyboard shortcuts in scan mode: comma jumps to the start of an item; period jumps to the end.

Quick Machine Recovery: less downtime when things go wrong. This feature extends the Windows Recovery Environment (WinRE) to automatically search for and apply cloud-based fixes when a device repeatedly fails to boot. On Home PCs, it’s enabled by default; on Pro and Enterprise, admins can control it via policy. It won’t fix every boot failure, but it’s a promising safety net that could save trips to a repair desk.

PC migration made easier. Windows Backup now supports a direct pairing between old and new PCs to transfer files and settings during setup. It’s aimed at consumers and small businesses; large enterprises will still use their own imaging tools, but for anyone setting up a new laptop, it’s a welcome simplification.

Copilot voice interactions mature. Separate from the OS version, Copilot’s voice features—press Alt+Space for two seconds to talk, or use the “Hey Copilot” wake phrase—have been rolling out through the Microsoft Store. In 25H2, the underlying hooks are all there, so if you have a Copilot+ PC or a compatible microphone, voice becomes a first-class input method.

Smaller tweaks for specific workflows. The touch keyboard now has a gamepad layout with button shortcuts (X for backspace, Y for space). The Windows share sheet gains an Edit button that opens the Photos app to crop or annotate images before sending. These are niche but illustrate Microsoft’s attention to smoothing edges.

What’s Being Removed—and Why You Need to Pay Attention

PowerShell 2.0 and WMIC are both stripped out of 25H2. PowerShell 2.0, a legacy engine that dates back to Windows 7, has been deprecated for years. WMIC, the command-line interface for WMI, has been superseded by PowerShell CIM cmdlets like Get-CimInstance. Their removal shrinks the attack surface and reduces maintenance overhead, but it creates a hard compatibility break: any script, scheduled task, or piece of management software that invokes powershell -Version 2 or calls wmic.exe will fail.

Microsoft isn’t backing down on this. The company wants organizations to modernize their automation before upgrading, and the enablement package model—where the feature update itself is a quick toggle—means you could flip the switch and only then discover that your old inventory script or software deployment tool stops working. For IT admins, this is the one non-negotiable preparation step.

What It Means for You (By Audience)

For home users and students. If you’re running Windows 11 Home or Pro on a personal device, 25H2 will feel like a small patch. The install will be quick—likely a single reboot—and you’ll probably notice only the restored clock and perhaps the lock screen widgets. The feature changes are minimal and non-disruptive. However, you should still upgrade when it’s offered in Windows Update. Not only will you get the usual security fixes, but upgrading resets your support clock: Home and Pro editions get 24 months of servicing from the release date, meaning a device that moves to 25H2 won’t fall out of support until roughly late 2027. If you stay on 24H2, your support ends earlier.

For power users and enthusiasts. You’ll appreciate the cleaner OS image without legacy PowerShell 2.0 and WMIC cruft, but you might need to audit any custom scripts or tools you rely on. If you use package managers, system tweak utilities, or automation that calls wmic.exe, test them on a 25H2 Insider build before the stable channel rollout. The enablement package approach means it’s trivially easy to upgrade, but just as easy to overlook a broken dependency.

For IT administrators and enterprise architects. 25H2 is essentially a security and lifecycle vehicle. The removal of PowerShell 2.0 and WMIC is your biggest risk vector. Before you deploy, inventory every script, logon task, Group Policy startup script, and software agent for references to wmic or powershell -Version 2. Migrate to PowerShell 5.1 or 7+ and use CIM cmdlets. The new Group Policy and CSP for removing default Microsoft Store packages is a bonus—it lets you trim inbox apps from corporate images without post-provisioning cleanup.

Also, test Quick Machine Recovery settings in your environment. It might upload diagnostic data during remediation, so review the privacy and network implications. Use pilot rings as always: start with a small, diverse set of hardware, validate your critical line-of-business apps, and then expand. Since the upgrade itself is fast, your rollout can be more about verification and less about scheduling downtime.

How We Got Here: The Enablement Package Strategy

Microsoft first introduced enablement packages with Windows 10 version 1903 and has refined the approach ever since. The idea is simple: instead of delivering a full feature update as a monolithic operating system replacement, the company ships feature code in advance through the monthly cumulative updates (the “B” releases on Patch Tuesday). That code sits dormant, guarded by feature flags, until a tiny enablement package flips the switches. This makes the update process vastly faster—on a fully patched 24H2 machine, moving to 25H2 can be a matter of minutes rather than an hour—and dramatically reduces the risk of regressions, because the binaries have already been soaking in the ecosystem for months.

For 25H2, this means the visual changes are modest because the heavy lifting—the core platform improvements, security mitigations, and driver refinements—has been happening incrementally throughout the 24H2 lifecycle. The version upgrade is, more than anything, a signal that your device is current and its support window resets. Microsoft is doubling down on “continuous innovation,” so we should expect future annual updates to follow the same pattern: a small eKB that steps up the version number, while feature work arrives whenever it’s ready, not just once a year.

What to Do Now: A Practical Checklist

  1. Check your Windows Insider settings. If you want to test 25H2 now, join the Release Preview channel. It’s stable enough for early validation on secondary machines. Go to Settings > Windows Update > Windows Insider Program and select Release Preview.
  2. Audit for legacy dependencies. On any machine that will receive 25H2, run a quick scan in PowerShell: Get-ChildItem -Recurse -Filter *.ps1, *.bat, *.cmd, *.vbs, *.wsf | Select-String "wmic|powershell.*-Version 2" will surface scripts that need attention. Do the same for Group Policy objects and SCCM packages.
  3. Modernize your automation. Replace wmic calls with Get-CimInstance or equivalent WMI queries. For example, wmic cpu get name becomes Get-CimInstance Win32_Processor | Select-Object Name. Migrate any PowerShell 2.0-specific code to PowerShell 5.1 or, better, PowerShell 7. The latter runs side-by-side with Windows PowerShell and supports modern features.
  4. Configure Quick Machine Recovery. For enterprise, decide whether to enable QMR and set policies for cloud remediation. By default, it’s off on Pro/Enterprise, so consider turning it on for remote devices that might otherwise require a desk visit.
  5. Plan your upgrade waves. Use Windows Update for Business or WSUS to roll out 25H2 in rings. Start with IT and early adopters, then expand to broad deployment after a few weeks of monitoring. If you use tools like Intune, the new RemoveDefaultMicrosoftStorePackages CSP can be tested in a lab first.
  6. Don’t skip this upgrade. Even if the feature list underwhelms you, the lifecycle extension and security hardening are critical. Each version of Windows 11 has a finite support window; delaying an upgrade puts you closer to an unsupported state where you’ll stop receiving patches. For Home/Pro, that deadline is 24 months from release; for Enterprise, 36 months. Time your move accordingly.

Outlook: What to Watch Next

The 25H2 release makes clear that Microsoft is comfortable shipping annual updates with little user-facing fanfare, using the enablement package as a lifecycle management tool rather than a feature vehicle. This likely sets the template for 26H2 and beyond. If you’re hoping for a blockbuster “Windows 12,” temper your expectations; the company’s focus is on weaving AI and cloud experiences into the existing product, not offering a clean break. However, the Copilot+ PC push—with dedicated neural processing units—will continue to gate experiences like Recall and advanced voice. For most users, your next desktop refresh will matter more than an OS version number. For now, treat 25H2 as what it is: a quiet, low-friction way to stay secure and supported for two more years.