{
"title": "Windows 11 25H2 Release Preview: Enablement Package Arrives with Legacy Tool Removal",
"content": "Microsoft has released Windows 11 version 25H2 (Build 26200.5074) to the Release Preview channel, the final testing ring before the update reaches all eligible Windows 11 devices later this year. Delivered as a small enablement package on top of the existing 24H2 servicing stream, the update promises a fast, light‑weight upgrade — but it also forces IT administrators to confront two major legacy deprecations and test new enterprise‑only controls.
The Release Preview build, announced on August 29, 2025, is “production‑adjacent,” meaning its code is essentially what will ship to consumers and businesses. While Microsoft has not set a specific general availability date, industry watchers expect a phased rollout starting in September or October, expanding gradually as telemetry confirms stability.
The Enablement Package Model Explained
Since Windows 10 version 20H2, Microsoft has increasingly used enablement packages for annual feature updates. The idea is straightforward: instead of downloading a colossal new OS build, the necessary feature binaries are slipped into monthly cumulative updates (LCUs) throughout the year, but kept inactive. When the company is ready to release the new version, it pushes a tiny enablement package (typically a few hundred kilobytes) that flips feature flags, “waking up” the dormant code. A machine that has regularly installed patches can transition from 24H2 to 25H2 with a download measured in kilobytes, followed by a single reboot.
This approach slashes downtime. In enterprise environments, where a full feature update can take 30 minutes or more, the enablement package often finishes in five minutes. It also means that the servicing stack — the component that handles updates — remains identical between 24H2 and 25H2, so both versions receive the same security fixes every Patch Tuesday. For IT teams managing fleets of thousands, that unified servicing cuts the testing matrix in half, as there’s no need to validate separate updates for separate OS versions.
Yet, the model is not without pitfalls. Although the binary files are present, enabling them can alter runtime behavior. Drivers, security agents, and deeply embedded scripts that work perfectly on 24H2 may stumble once the new feature set is exposed. The Release Preview window exists precisely to give organizations a chance to catch these regressions before broad deployment.
What’s New in the User Experience
25H2 is an evolution, not a revolution. Insider builds and community reports point to a handful of interface refinements:
- Start menu: A wider layout and a redesigned “All apps” list that groups items more logically.
- File Explorer: Better dark‑mode consistency and smoother folder navigation, addressing long‑standing visual quirks.
- Notifications: The system tray clock on secondary monitors can now show seconds, a small but often‑requested flexibility.
- AI integration: The Click to Do feature, which scans content on screen and offers contextual actions, gains free‑form and rectangular selection modes, plus the ability to select multiple items with Ctrl+click. The Snipping Tool can now record videos within a window, expanding its capture capabilities.
For IT support, this fragmentation is a headache. A helpdesk script that says “launch Click to Do and select the text” will fail on a non‑Copilot+ PC. Team training materials must account for multiple interface variants. Before rollout, administrators should catalog device hardware and license entitlements, then create separate documentation for each cohort.
Enterprise Changes That Demand Immediate Attention
The most muscular changes in 25H2 are under the hood, and they directly affect manageability and security.
PowerShell 2.0 Removal
PowerShell 2.0, first introduced with Windows 7, has been removed from the shipping image. This ancient engine lacks modern logging, constrained runspaces, and other security features that have become standard in PowerShell 5.1 and 7+. Many organizations still have scripts, scheduled tasks, or even software installers that explicitly call powershell.exe -Version 2. On 25H2, those calls will simply fail. Microsoft’s recommendation is to migrate everything to PowerShell 5.1 (included) or the open‑source PowerShell 7+, which runs side‑by‑side. The removal reduces the attack surface and encourages best practices, but it demands a thorough inventory sprint before the update reaches production machines.
WMIC Removal
The Windows Management Instrumentation Command‑line (WMIC) tool has been deprecated since 2016 and is now absent from the 25H2 image. WMIC has been a convenient way to query system information in batch files: wmic csproduct get name, wmic os get lastbootuptime, and countless other snippets are scattered across company networks. Without WMIC, those scripts break. The path forward is to rewrite them using PowerShell CIM cmdlets (Get-CimInstance -ClassName Win32_ComputerSystem) or the underlying WMI .NET classes. This conversion is generally straightforward but requires finding every instance of wmic.exe in the automation estate.
New Inbox App Removal Policy
On a more positive note, 25H2 introduces a Group Policy and MDM Configuration Service Provider (CSP) that allows IT admins on Enterprise and Education editions to uninstall selected inbox Microsoft Store apps during device provisioning. Previously, removing built‑in apps like Xbox, Mail, or OneNote required custom PowerShell scripts or image‑hacking tools that often broke after feature updates. Now, administrators can specify a list of apps in a policy, and they will be stripped out before the user sees the desktop. This native control simplifies image creation and reduces “bloat” on corporate devices. However, as with any provisioning change, it must be tested in a pilot environment to ensure that dependent components or Start menu layouts don’t break.
Validation: The Release Preview Is Your Last Chance
The Release Preview channel represents the final build that will go to the public, barring critical fixes. Microsoft itself recommends that commercial customers use this window to “validate apps, drivers, and configurations” before the update reaches general availability. The timeline is aggressive: although no firm GA date exists, many expect the update to begin hitting consumer devices in October, with enterprise deployments following in waves.
Here is a concrete action plan for IT leaders:
- Inventory legacy scripts. Deploy a script scanner that searches for “powershell.exe -Version 2” and “wmic.exe” across all endpoints and file shares. Prioritize by business impact.
- Remediate. Allocate developer or admin time to rewrite WMIC calls and PSv2 scripts as soon as possible. Commit the updated scripts to source control and test them on a 24H2 machine before rolling them to the pilot.
- Download the official ISO. Microsoft said a full ISO of 25H2 will be available “later this week” after the Release Preview announcement. Use it (or Azure Marketplace images) to build representative test images and validate provisioning workflows, including the new inbox app removal policy.
- Pilot with Windows Update for Business or WSUS. Select a small, diverse set of endpoints and push the enablement package. Monitor application compatibility, driver behavior (especially for endpoint protection and VPN clients), and user-reported issues.
- Engage third‑party vendors. Contact suppliers of critical security, backup, and monitoring agents to confirm their support for 25H2. Some may release updated versions only after GA; coordinate your pilot schedule accordingly.
- Test rollback. Even though the eKB can be uninstalled via Settings > Windows Update > Update History > Uninstall Updates, recent cumulative updates sometimes bundle the servicing stack in a way that complicates removal. Have VM snapshots or a tested recovery plan for pilot machines.
Risks and Realities
The enablement package model is operationally elegant, but it doesn’t eliminate all upgrade risks. Three areas deserve special caution:
- Legacy automation breakage: Scripts depending on PSv2 or WMIC will fail silently or loudly, disrupting workflows. This is the most predictable risk and the hardest to fix after the fact.
- Vendor update lag: If your endpoint protection or backup vendor hasn’t certified 25H2, you may face support gaps in the early weeks. Align your rollout timing with vendor readiness.
- User experience inconsistency: As noted, AI features will be absent on many devices, leading to confusion and helpdesk calls. Mitigate this with targeted communication and training.