Microsoft has quietly posted official ISO images of Windows 11 version 25H2 for Windows Insiders in the Release Preview channel, handing IT administrators, OEMs, and security testers their first complete installer for the next feature update. The build—identified in the 26200.x family—arrives with surgical removals that will break legacy automation, including the elimination of PowerShell 2.0 and the venerable WMIC command-line tool from new installations.

What Just Dropped: The 25H2 ISO and What’s Inside

On the Windows Insider Preview Downloads page, Microsoft now lists a full ISO for Windows 11 Insider Preview (Release Preview) corresponding to the 25H2 development branch. Community reports and official communications pinpoint the Release Preview seed as Build 26200.5074, the first ISO-based deliverable for the update that will ship later this year.

This release follows a well-established pattern: most users already on Windows 11 24H2 will receive 25H2 through an enablement package (eKB)—a small, single-restart upgrade that turns on features already present on disk. But for clean installations, golden-image capture, OEM preloading, or reproducing out-of-box experience (OOBE) behavior, only a canonical ISO provides a true from-scratch installation path.

Access requires a Microsoft account enrolled in the Windows Insider Program, with the Release Preview channel selected. The portal generates time-limited download links; plan your bandwidth accordingly and download immediately.

Three Platform Changes That Demand Attention

The Release Preview guidance calls out three operational changes that will impact managed environments:

  • PowerShell 2.0 engine removal. The legacy PSv2 engine, long marked as deprecated, is no longer included in shipping images. Any scripts or installation routines that hardcode powershell.exe -Version 2.0 will fail. Migrate to PowerShell 5.1 (the default shipping engine) or PowerShell 7+.
  • WMIC (wmic.exe) deprecation and removal. The Windows Management Instrumentation Command-line tool, used for decades to query system information, has been stripped from the image. Microsoft directs admins to PowerShell CIM/WMI cmdlets (for example, Get-CimInstance) as replacement.
  • New provisioning controls for inbox Store apps. A fresh Group Policy and corresponding MDM CSP allow enterprise and education administrators to selectively remove preinstalled Microsoft Store packages during device provisioning, reducing clutter in managed deployments.

These changes are not cosmetic; they directly affect imaging workflows, deployment scripts, and automation that assumes the presence of WMIC or PSv2.

Smaller UX Touches

During the OOBE, users can now assign a custom device name before first sign-in, eliminating the need to accept a randomized hostname. A redesigned Clock app with Focus Sessions offers a built-in timer that can pause music while you work—a minor productivity experiment surfacing in Insider builds.

For enterprise imaging and device management teams, however, the platform housekeeping items outweigh the consumer-facing polish.

Who Needs to Act—and Why

The impact of this ISO release depends on your role:

Home Users

You’ll likely receive 25H2 through the enablement package when it becomes broadly available; the ISO is optional. If you want to preview the OOBE or perform a clean install ahead of time, you can enroll in the Insider program and download the image. Custom device naming and the new Clock app are the most visible changes.

Power Users and Enthusiasts

If you maintain personal automation scripts that rely on WMIC or PSv2, use this ISO in a virtual machine to test and remediate before the final release. Early cleanup avoids last-minute breakage when you upgrade your main machine.

IT Administrators, System Integrators, and Security Teams

The ISO is a critical validation artifact. You need it to:

  • Capture golden images for deployment pipelines (SCCM, MDT, custom provisioning).
  • Reproduce OOBE flows for Azure AD join, Autopilot provisioning, and MDM enrollment.
  • Validate security software—EDR/AV telemetry, installer-time scanning, and first-boot behavior—against the same bits that will ship to production hardware.
  • Certify drivers and firmware on the canonical image rather than an eKB-patched update.

If your organization uses scripts that call wmic.exe or the PowerShell 2.0 engine, schedule remediation immediately. The deprecation window is closing; the ISO gives you the exact target environment for testing.

How We Arrived at the 25H2 ISO

Microsoft has been steadily moving toward an enablement-package model for Windows 11 feature updates. The 24H2 release, last year’s major update, established the baseline platform upon which 25H2 will activate new functionality with minimal disruption for already-patched devices. This two-track approach—servicing stack plus capabilities activated on demand—is efficient, but it creates a gap: it does not replicate the experience of powering on a factory-fresh PC or re-imaging a fleet.

The Insider ISO closes that gap. Historically, Microsoft has made such ISOs available late in the Release Preview cycle, but the timing of this drop—with the WMIC and PSv2 removals already in place—signals that the final rollout is approaching and that these deprecated components will not be coming back.

WMIC has been deprecated since Windows 10, while PowerShell 2.0 has been listed as deprecated even longer. Their actual removal from new installation media marks the end of a multi-year effort to modernize the management stack. For anyone who hasn’t yet migrated, the clock is now loud.

Immediate Action Plan

Follow these steps to turn the ISO release into a controlled validation cycle:

  1. Enroll a test account in the Windows Insider Program (Release Preview channel) and sign in at the Windows Insider Preview Downloads page. Generate a download link for your required edition and language.
  2. Download and verify the ISO immediately—links are time-limited. Record the SHA-256 checksum reported on the portal and verify it post-download.
  3. Inventory legacy script dependencies. Search your environment for:
    - wmic.exe calls (common in logon scripts, health checks, and inventory tools).
    - powershell.exe -Version 2.0 or explicit PSv2 reliance in configuration items.
  4. Remediate scripts by replacing WMIC queries with Get-CimInstance, Get-WmiObject (still available in PowerShell 5.1 but deprecated), or direct .NET classes. Migrate any PSv2 requirements to PS5.1 or PS7.
  5. Build a test lab. Deploy the ISO to virtual machines or a representative hardware set. Validate:
    - OOBE flows (Azure AD join, Autopilot provisioning, MDM enrollment).
    - Core applications: VPN clients, line-of-business apps, security agents.
    - The new provisioning CSP for removing inbox Store apps, if you plan to use it.
  6. Coordinate with vendors. Confirm that your EDR, AV, and driver packages install and operate correctly on a fresh 25H2 installation. Early feedback to vendors can prevent rollout-day surprises.
  7. Plan a pilot deployment. After lab validation succeeds, deploy the enablement package (or new images) to a small, diverse device cohort. Document acceptance criteria, rollback procedures, and failure thresholds.

Checklist for Administrators

  • [ ] Enroll in Insider Release Preview and generate an ISO link
  • [ ] Verify ISO SHA-256 checksum
  • [ ] Inventory wmic.exe and PSv2 dependencies
  • [ ] Refactor scripts to modern CIM/WMI cmdlets and PowerShell 5.1+
  • [ ] Test OOBE provisioning and Autopilot with the new CSP
  • [ ] Validate security stack, drivers, and critical apps
  • [ ] Execute a structured pilot rollout

What to Watch Next

The arrival of the 25H2 ISO in the Release Preview channel suggests that a final public release is only months away. Microsoft will likely deliver additional Insider builds with polish and fixes, but the major platform removals are already locked in. Early adopters have a narrow window to validate imaging and automation before the enablement package flips the switch on production machines.

If your organization still relies on WMIC or PowerShell 2.0, use this ISO as an uncompromising test bench. Remediate now, and the transition to 25H2 becomes a smooth deployment exercise rather than a fire drill.