Microsoft released Windows 11, version 25H2 (Build 26200.5074) to the Release Preview Channel on August 29, 2025, giving IT administrators an early shot at validating this year’s annual feature update before its general availability later this year. The update arrives as a lightweight enablement package, a small switch that activates features already dormant in the 24H2 servicing branch. That means the jump from 24H2 to 25H2 is a single restart—fast, nondisruptive, and ideal for managed fleets. But buried in this release are two critical removals and a long-awaited enterprise management control that demand immediate attention.

The enablement package model: a servicing shortcut

Microsoft’s shared servicing branch strategy has been evolving over recent releases. New feature code is shipped in monthly cumulative updates for the current version (24H2) in a disabled state. When Microsoft decides to flip the switch for a named feature update, it publishes an enablement package (eKB)—a kilobyte-sized payload that toggles a few registry flags and activates the latent features. The result is a near-instant upgrade that sidesteps the traditional full-image replacement. For IT, this means compatibility testing can laser in on the newly enabled features rather than re-validating the entire OS surface, though thorough validation of line-of-business apps and management agents remains essential.

What’s new, what’s gone, what’s manageable

Legacy tooling hits the chopping block

Two long-deprecated Windows components have been removed outright:

  • PowerShell 2.0 engine: Any script, scheduled task, or remote management tool that explicitly calls powershell -version 2 or relies on PSv2 modules will fail. Microsoft recommends migration to PowerShell 5.1 or, better, PowerShell 7 (Core).
  • WMIC (Windows Management Instrumentation Command-line): The wmic.exe utility is gone. Scripts, installers, monitoring agents, and build processes that parse WMIC output must switch to CIM/WMI PowerShell cmdlets (e.g., Get-CimInstance, Get-WmiObject on older hosts) or modern REST APIs.

Remediation is straightforward but often overlooked until production breaks. IT teams should audit their estates now using simple scanning scripts:

# Find PowerShell v2 calls
Get-ChildItem -Path C:\Scripts -Recurse -Include .ps1,.bat,.cmd | 
  Select-String -Pattern "PowerShell.-Version 2|\-v 2" -List

Find WMIC usage

Get-ChildItem -Path C:\ -Recurse -Include .ps1,.bat,.vbs,.inf | Select-String -Pattern "wmic " -List

Replace common WMIC queries with their CIM equivalents:

  • Old: wmic logicaldisk get name,size,freespace
    New: Get-CimInstance -ClassName Win32LogicalDisk | Select-Object DeviceID,Size,FreeSpace
  • Old: wmic process where name='notepad.exe' get processid
    New: Get-CimInstance -ClassName Win32Process -Filter "Name='notepad.exe'" | Select-Object ProcessId

Policy-based removal of pre-installed Store apps

25H2 introduces a device-level policy to strip select Microsoft Store apps that ship with Windows 11 Enterprise and Education. Configured via Group Policy (Computer Configuration → Administrative Templates → Windows Components → App Package Deployment → Remove Default Microsoft Store packages) or via MDM CSP (./Device/Vendor/MSFT/Policy/Config/ApplicationManagement/RemoveDefaultMicrosoftStorePackages), this capability lets IT de-clutter the user experience without resorting to custom scripts or provisioning packages.

Community testers, however, have reported a rough edge: apps are unprovisioned, but empty Start menu shortcuts may linger. PatchMyPC and other early adopters noted that the backend removal works, but UI artifacts remain until a subsequent servicing update cleans up the stale icons. IT teams should test this policy on pilot devices and verify the Start menu, All apps list, and event logs before scaling out.

Copilot and UX refinements

Several feature refinements already seen in Dev and Beta channels surface in this Release Preview: Click-to-Do selection modes, File Explorer AI actions, and incremental Copilot+ rollouts. These are staggered via A/B feature gates, so not every device will see them immediately. IT should validate that any business-critical workflows relying on legacy UI elements remain intact.

How Insiders can install 25H2 today

Devices enrolled in the Release Preview Channel that meet Windows 11 hardware requirements (TPM 2.0, Secure Boot, supported CPU) can “seek” the update:

  1. Confirm your channel: Settings → Windows Update → Windows Insider Program. Switch to Release Preview if needed.
  2. Check for updates: In Windows Update, click “Check for updates.” The 25H2 feature update appears as an optional download.
  3. Install and restart: Because it’s an enablement package on 24H2, the restart is typically quick—under 10 minutes in lab tests—but always schedule the deployment and back up critical data.

Business customers can validate via Windows Update for Business (WUfB), WSUS, or Azure Marketplace images (available the same day). Full ISOs drop next week via the Windows Insider ISO page for clean installs and VM preparation.

IT validation: a phased pilot blueprint

Treat this Release Preview as the opening of your validation window. Microsoft’s intent is clear: this is a production-adjacent build for managed pilots, not a curiosity.

Phase 1: Assemble a representative pilot

Select 5–10% of your fleet, covering top hardware models (Surface devices, major OEM SKUs, and your most common third-party images). Include both managed and unmanaged BYOD devices if relevant.

Phase 2: Pre-flight checks and backups

  • Capture full VM snapshots or system images.
  • Document rollback steps: uninstall the feature update via Settings or revert with a recovery image.
  • Verify BitLocker recovery keys are accessible.

Phase 3: Validation checklist

Category Test Steps
Line-of-business apps Launch core apps, test all workflows, monitor agent health (AV, EDR, VPN).
Scripts & automation Run inventory scans for WMIC/PSv2 dependencies. Validate replacement scripts.
Enterprise sign-in Test Azure AD join, domain authentication, Conditional Access policies.
Imaging & recovery Run Sysprep and Push-Button Reset; confirm that app removals persist after reset.
New management policy Apply the Remove Default Microsoft Store packages GP/CSP on a small group; check Start menu cleanliness and event logs.
Drivers & peripherals Test printing, USB devices, docking stations, virtual drivers.
Accessibility Verify Narrator, NVDA, and other assistive tools function correctly.

Phase 4: Telemetry and scale

Collect crash dumps, Event Viewer logs, and agent telemetry from pilot devices. Monitor Windows Release Health and the Flight Hub for emerging issues. If your pilot uncovers a blocking bug, Microsoft Support is available for Release Preview customers—document steps to reproduce and gather logs before contacting them.

Scale in rings: Pilot → Broad pre-production → Production. Never skip broad validation if your organization has thousands of endpoints.

Known issues and community warnings

  • Dead Start menu shortcuts: The Store app removal policy leaves non-functional icons; plan a post-cleanup script or wait for the next cumulative update that addresses the issue.
  • Automation breakage: WMIC and PowerShell v2 removals are the most likely blockers. Audit now.
  • Staggered feature rollouts: Some Copilot and AI enhancements are A/B tested. Don’t expect them on every device; confirm feature visibility via Windows Update policies and device telemetry.
  • App compatibility surprises: Even with the enablement model, behavior changes can creep in when dormant features activate. Thoroughly test your full suite.

References for your lab

What to do this week

If you’re an enthusiast or Insider: Spin up a test VM, join Release Preview, install 25H2, and explore the new features. Back up beforehand and send feedback via the Hub.

If you’re an IT admin:

  • Launch a pilot ring of 5–10% of devices right away. Cover your hardware diversity and critical apps.
  • Run the WMIC/PSv2 audit scripts across your environment. Remediate any findings before upgrading.
  • Test the new Store app removal policy on lab hardware; document the Start menu state and any cleanup steps needed.
  • Use WUfB or WSUS to control deployment timing—don’t let users pull the update until your pilot gives the green light.

With PowerShell 2.0 and WMIC now fully removed, the clock is ticking for organizations still clinging to legacy tooling. The enablement package makes the upgrade trivial, but the compatibility debt is very real. Start validating now to ensure a smooth rollout when 25H2 reaches general availability.