In case you haven’t heard, Microsoft is getting things ready to release the latest version of Windows 11, Windows 11 version 25H2. In this one, Microsoft isn’t just dropping a massive new overhaul but it is using something they have now used before called an enablement package to switch on features ready to include in the current 24H2 release. This seems to be working well as it leads to faster upgrades, smaller download sizes and it means fewer issues for end users and IT staff. This release isn’t super major but there are a few things to know about it. Let’s look at the details.
Have you heard of this before? The enablement package?
What is this enablement package anyway? You may not be familiar with it, but the enablement package is Microsoft’s way of making the Windows upgrade process simpler. This is an old development practice of installing feature flags and code throughout a solution, but these are hidden until the developer is ready to turn them on. Then when ready, the flags can be turned on to make the changes and updates go live.
There is a good Reddit discussion that talks about the fact that this makes upgrading to 25H2 almost instantaneous for anyone already running Windows 11 24H2 that has the enablement package. One reboot is usually all it takes. Compared to the days of multi-gigabyte upgrades that could take hours, the enablement model is a welcome improvement. It also means IT departments can roll out the update more quickly across large numbers of machines. This will lead to less disruption for end users.
Why Microsoft prefers enablement packages
Enablement packages have become Microsoft’s standard way of releasing the “second half” of a Windows release cycle. The benefits as we have mentioned are very good for end users. It means smaller downloads, quicker installs, and less downtime.
For Microsoft, this makes it easier for servicing since 24H2 and 25H2 share the same underlying codebase. This still helps with delivering new features through monthly cumulative updates. This is true even before they are formally switched on in the next release.
This will also help with compatibility. Drivers, applications, and hardware that worked on 24H2 should still continue to work on 25H2. This will be extremely beneficial from a support standpoint.
Availability and early access
Microsoft has not officially announced the release. However, there are signs that it is getting close to that official announcement. Neowin reported that ISO files for version 25H2 are already available on Microsoft’s servers, even before the formal release. The ISOs being available allow for clean installations. Also, you can do in-place upgrades and this is useful for administrators or home labbers who want to start testing the install early.
At the same time, Thurrott confirmed that the ISOs and enablement packages are live in the Insider channels. That means members of the Windows Insider Program can already access the update by opting into the Release Preview ring.
In the past, the gap between Release Preview availability and general rollout has been a short one. Often this is just a matter of weeks with previous releases. I would expect the public release of Windows 11 25H2 to be sometime in the early fall of 2025.
New features and removals
TLDR; For everyday users, most of the changes will be minor. The update packages improvements and fixes that were installed as incremental updates during the 24H2 lifecycle,. These are now rolled into a single official release.
Deprecated components
This section of the note isn’t as dramatic as 25H2 shares the same codebase as 24H2. This update is really just a collection of updates and enhancements that improve management and security for the OS. In this release, Microsoft is removing legacy components from the OS. This includes:
- PowerShell 2.0, which has been officially deprecated for years, will finally disappear with 25H2
- WMIC, the Windows Management Instrumentation Command-line tool, is also being removed
Most modern versions of scripts and other automation tools have moved away from PowerShell 2.0 and WMIC, it will still be worth looking to make sure old scripts don’t use WMIC or old versions of PowerShell cmdlets.
Enterprise updates
On this side of things, there are new policy controls that allow organizations to automatically remove certain pre-installed Microsoft Store apps. This type of tooling is something that IT admins have been asking for, for quite some time. It gives them a much more automated approach to manually strip out apps or rely on custom provisioning scripts. It will also lead to better baseline installations through group policy or mobile device management (MDM).
Download the files
- Windows 11 version 25H2 ISO (Arm64)
- KB5054156 – 24H2 to 25H2 eKB (Arm64)
- Windows 11 version 25H2 ISO (x64)
- KB5054156 – 24H2 to 25H2 eKB (x64)
Upgrade paths and options for upgrading
If you are already running 24H2, you will see it appear in the Windows Update notifications as a feature enablement update. Installation will not take long due to the way the feature enablement update works and likely will simply require a reboot.
If you are still on 23H2 or an earlier version, the process will be more involved. You will either need to perform a larger feature update using Windows Update or download the full ISO and perform a clean install.
You can also join the Windows Insider Program and selecting the Release Preview channel if you like to live on the “bleeding edge” of updates and this is an easy way to try 25H2 ahead of everyone else. Just keep in mind that preview builds may still have minor bugs or quirks.
Any gotchas with upgrading?
If you are on 24H2 today, upgrading to 25H2 should be fairly low risk. As we mentioned compatibility is not expected to change, and the process itself is fast due to the way the enablement package works. The main caution is for anyone still relying on older admin tools that are being removed. If you know your automation scripts or other tools you are using depend on WMIC or PowerShell 2.0, take steps now to migrate your scripts and workflows as starting with 25H2 these are going way.
If you are on 23H2 or Windows 10, the jump will be much bigger. In that case, you’ll probably want to double-check hardware compatibility requirements like TPM 2.0, Secure Boot, and supported processors. A clean install may also be the better choice if you are dealing with older hardware.
Always, always, always back up your important data before performing any upgrade. Throw a virtual snapshot on virtual machines before performing the update. Even though enablement packages are low-risk, no update is completely free from the possibility of something going wrong.
Wrapping up
The new Windows 11 version 25H2 is not a dramatic or flashy new release with tons of new features. But if you are already running 24H2 the upgrade is going to be hopefully quick and painless. The new enablement package model that Microsoft is using now helps to minimize the disruption and pain of upgrading to new feature releases.
However, with this update, the more disruptive aspect will come from the outdated tools that are being completely removed. Tools like VMIC and PowerShell 2.0 are officially going away and totally removed with Windows 11 25H2. By now though, most scripts and tools don’t use these legacy components but do be aware of that. Are you planning on upgrading to 25H2? Let me know in the comments.
About The Author
