Microsoft has pushed Windows 11 version 25H2 into the Release Preview channel, giving enterprise and education customers a near-final build that activates features already lying dormant in the 24H2 servicing stream. Build 26200.5074, announced by the Windows Insider team on August 29, 2025, arrives as a tiny enablement package (eKB) rather than a monolithic update—a flip of the switch for code that has been shipping inside monthly cumulative patches. The move cements Microsoft’s modern servicing model, but it also forces organizations to finally deal with two long-deprecated tools: PowerShell 2.0 and WMIC.

The update is not a visual overhaul. Instead, it delivers incremental user experience polish, hardens security by stripping out legacy runtimes, and gives IT administrators new controls to strip down managed images. For organizations that stay current with patches, the upgrade will feel almost invisible—a single restart after a few hundred megabyte download. For those who have ignored the warnings about PowerShell 2.0 and WMIC, it could be a rude awakening.

The enablement package model: what it means for rollouts

Under Microsoft’s shared servicing strategy, both 24H2 and 25H2 run on a common codebase. New features for the annual release are integrated into the monthly cumulative updates (LCUs) for the active branch (currently 24H2) but remain dormant. When Microsoft declares the milestone ready, it ships a lightweight enablement package—a few hundred megabytes—that turns on those dormant features and bumps the version label. Devices already on the 24H2 branch and fully patched get the shortest path: a quick download, one reboot, and they’re on 25H2.

For IT teams, this model dramatically simplifies patch management. There’s no separate LCU tree to maintain, and the delta between versions is limited to activated features rather than a full binary swap. The Release Preview marks the point where organizations should begin validation using Windows Update for Business (WUfB) or WSUS. Microsoft expects a broader rollout (general availability) later in the fall, but the Release Preview is the official starting gun for compatibility testing.

UX improvements: small polish, big impact

Users will notice a collection of modest but welcome refinements across the shell. The Start menu now supports wider layouts, new All apps views (Category, Grid, List), and an optional collapsible sidebar that integrates Phone Link information. These changes aim to make Start more scalable on large screens and less frustrating when many apps are installed. File Explorer gains better dark-mode adherence and responsiveness, and notification behavior improves on multi-monitor setups. The Settings app introduces summary “cards” on its home page and an experimental on-device AI agent (dubbed Settings Mu) that can interpret natural language queries—though only on hardware that meets Copilot+ requirements.

None of these tweaks rewrite the Windows UI. They are the kind of evolutionary polish that reduces daily friction. But exactly which tweaks appear on a given device will depend on hardware capability and licensing, because many of the flashier AI enhancements are gated.

Copilot and on-device AI: hardware and licensing gates

Microsoft continues to weave AI into Windows, but 25H2 makes it clear that the full Copilot experience is a tiered offering. Advanced on-device AI features—such as real-time content summarization, image editing, and the Settings Mu agent—require Copilot+ certified PCs with dedicated NPUs. Devices without that hardware will either fall back to cloud-assisted features or see these AI surfaces hidden entirely. Additionally, some semantic search and productivity capabilities demand Microsoft 365 Copilot entitlements.

For enterprises planning to roll out AI-assisted workflows, this fragmentation is a critical consideration. A fleet with mixed hardware and licensing will deliver an inconsistent user experience, complicating training and support. IT teams must map their hardware profiles and subscription tiers to the feature set they intend to deploy. The Release Preview is the ideal time to verify which Copilot features actually light up on representative devices.

Security hardening: killing PowerShell 2.0 and WMIC

The most operationally significant changes in 25H2 are the removals of two legacy tools that have been deprecated for years. Microsoft is finally excising the PowerShell 2.0 engine from shipping Windows images. The removal was confirmed in a support document (KB 5065506) published on August 11, 2025. PowerShell 2.0 will not appear in new Windows 11 installations starting with 24H2, and it is absent from 25H2 previews. Any script or installer that explicitly calls powershell.exe -Version 2 will either fall back to the default engine or fail outright.

Alongside PowerShell 2.0, WMIC (wmic.exe) is also being phased out of preinstalled images. WMIC has been a favorite tool for system administrators and, unfortunately, for attackers exploiting living-off-the-land techniques. Microsoft’s guidance is clear: organizations must migrate WMIC-dependent automation to PowerShell CIM/WMI cmdlets (like Get-CimInstance) or programmatic WMI APIs.

Both removals are overdue security wins. They reduce the attack surface and eliminate outdated code that often escapes rigorous security auditing. But they also create immediate work for organizations that have let legacy scripts and installers accumulate. The Release Preview gives teams a concrete deadline to inventory and remediate these dependencies.

Enterprise manageability: removing inbox Store apps

On Enterprise and Education SKUs, 25H2 introduces a new Group Policy / MDM Configuration Service Provider (CSP) path that lets administrators remove selected preinstalled Microsoft Store apps during provisioning. This capability allows IT to craft leaner, more locked-down images by eliminating inbox apps that aren’t needed in a managed environment. It also simplifies compliance with security baselines that call for minimal attack surface. The policy applies only to managed devices; consumer editions won’t see this control.

A practical checklist for IT teams

With the Release Preview now available, organizations should start their validation cycles immediately. Here’s a prioritized list of actions:

  • Inventory legacy dependencies—Search your entire environment for any scheduled task, script, or installer that references powershell.exe -Version 2 or calls wmic.exe. Flag these for remediation; they are almost certainly broken in 25H2.
  • Migrate WMIC calls—Replace wmic logicaldisk get size,freespace with PowerShell equivalent: Get-CimInstance -ClassName Win32_LogicalDisk | Select-Object DeviceID,Size,FreeSpace. Validate that your monitoring tools and operational scripts parse the new output correctly.
  • Update PowerShell 2.0-targeted code—Any code written for the ancient v2 runtime must be refactored for PowerShell 5.1 or 7.x. Run scripts in a test environment with strict mode enabled to surface hidden incompatibilities.
  • Build a representative pilot ring—Include hardware with varying NPU capabilities, your standard EDR/AV agents, storage drivers, and firmware versions. Test the eKB activation path via WUfB or WSUS, measuring both installation time and rollback reliability.
  • Validate Copilot and AI surfaces—Confirm that AI features appear and function as expected on both Copilot+ and non-Copilot+ hardware. Verify that your privacy and telemetry policies can control on-device AI agents.
  • Prepare communications—Notify stakeholders about the retirement of PowerShell 2.0 and WMIC. Ensure break-glass rollback plans exist in case low-level drivers or third-party agents behave unexpectedly after feature activation.

Risks: legacy dependencies and gated AI

The biggest pitfall is underestimating the reach of legacy tooling. PowerShell 2.0 might be lurking in ancient installer wrappers, vendor-generated scripts, or deeply buried automation that nobody remembers. WMIC is similarly pervasive; one survey of enterprise environments found WMIC references in everything from backup scripts to network inventory tools. A failure to remediate can lead to silent failures that break monitoring and patching workflows.

Gated AI features present a different kind of risk: user confusion. If half your devices show new Copilot capabilities and the other half don’t, helpdesk tickets will spike. Clear communication during deployment is essential, as is rigorous testing on your exact hardware mix.

Third-party endpoint agents and low-level drivers remain a perennial source of post-update blues. Even an enablement package can change runtime behavior enough to expose edge cases in vendor code. Piloting with actual agents—not just a clean image—is mandatory.

Finally, treat Release Preview as a validation milestone, not a green light for broad deployment. Microsoft has not announced a general availability date beyond “later this fall,” and jumping the gun risks hitting compatibility issues that haven’t been discovered yet.

Timeline and rollout strategy

  • Release Preview availability: August 29, 2025 (Build 26200.5074).
  • Anticipated GA: Fall 2025, with ISOs and Azure Marketplace images expected to follow the final validation period. Community reports suggest a gradual rollout starting in late September or October.

A sane rollout sequence: establish a pilot ring now; inventory and remediate legacy tooling; validate the eKB activation path and third-party agents; expand to a broader staging ring; then schedule phased deployment after stabilization. The enablement model makes the technical upgrade fast, but the organizational work—remediation, testing, and communication—requires weeks of lead time.

Why 25H2 matters

This release is the mature expression of Microsoft’s new update philosophy. It’s not about flashy new features; it’s about making Windows updates faster, simpler, and more secure. The enablement package cuts downtime for up-to-date devices. The common servicing branch eliminates duplicate testing. The removal of PowerShell 2.0 and WMIC closes two long-standing attack vectors. And the new MDM controls give IT a firmer grip on managed images.

But that efficiency comes with a price: organizations must finally do the housekeeping Microsoft has been urging for years. The legacy tool deprecations are not new announcements; they’ve been telegraphed since Windows 10. 25H2 is simply the moment the grace period ends. The Release Preview is your early warning system. Use it.