If you've been updating your Windows PC for a while, you've probably seen a new update appear more than once. version type 20H2, 22H2, 24H2 or 25H2 without the system being completely reinstalled. Behind these large versions, in many cases, there isn't a new ISO or a clean installation, but a small component called Enablement Package.
This enablement package has become Microsoft's preferred way to deliver certain feature updates quickly, almost silently, and with a single restart. Even so, it's not uncommon for it to raise questions: What really changes, what risks are involved, what happens to security or to versions that are already at the end of support?Let's break all this down calmly, relying on what is already officially known and on the practical experience of those who use it on a daily basis.
What exactly is the Windows Enablement Package?
The Enablement Package is, in essence, a small patch that acts as a master switchWindows 10 and Windows 11 continuously receive cumulative updates that include, in addition to security fixes, New features that are disabled by defaultThese features are installed in the background, but remain dormant until the system applies the enablement package corresponding to a specific version.
Instead of downloading several gigabytes and reinstalling the operating system, the Enablement Package simply... Change a number of internal flags, activate existing code, and update the version number.That's why its installation is so quick and its size so small compared to a traditional feature upgrade.
This approach has an important consequence: different versions of Windows can share exactly the same kernel and the same system filesdiffering only in what is active or inactive. This explains why, in many cases, switching from one H2 version to another simply requires a restart.
How the Enablement Package works in Windows 10 (20H2, 21H1, 21H2 and 22H2)
In Windows 10, Microsoft clearly introduced this concept with the versions 2004, 20H2, 21H1, 21H2 and 22H2All these editions share a common core operating system, with an identical set of critical files; in fact, the features of 20H2, 21H1, 21H2, and 22H2 were already included in the monthly quality updates for version 2004 and laterbut they remained inactive.
When the appropriate enablement package is installed, what happens is activate those new features and update the version identifierThus, for example, upgrading from Windows 10 2004 to Windows 10 20H2 or 22H2 becomes a very quick operation, with only one interruption to restart the computer.
For compatible versions (2004, 20H2, 21H1 and 21H2), the enablement package is automatically distributed by Windows Update or WSUSIn the list of updates it appears as "Feature update for Windows 10, version XXH2", but internally it is an eKB (Enablement Package) that only activates what is already present in the system.
If the equipment comes from an older edition, such as Windows 10 1909 or earlierHowever, the situation changes: the enablement package cannot be installed separately. In that case, the upgrade to 22H2 is performed with a full feature updatewhich includes both the base files and the integrated enablement package itself, and there the installation time is indeed longer.
Requirements, distribution channels, and restarts in Windows 10
To apply a Windows 10 enablement package, it is essential to meet a series of requirements. version and patch prerequisitesIn the case of 22H2, Microsoft requires that you be on Windows 10 2004, 20H2 or 21H1 (and, in practice, also 21H2) with the latest cumulative updates installed.
Regarding distribution channels, the behavior is quite homogeneous: Windows Update and Microsoft Update They automatically download and install the enablement package when the device is eligible. From the user's perspective, this is simply seen as a "Feature Update" that requires a restart and usually completes very quickly.
In corporate environments, the package is also distributed by Windows Server Update Services (WSUS)Provided that Windows 10 is selected in Products and Classifications and the Updates or Upgrades category is chosen, as applicable. WSUS synchronization itself will then retrieve the appropriate eKB file for each supported version.
There is one important detail: these packages are not usually available for direct download on the Microsoft Update Catalog as standalone updates. They usually arrive via Windows Update, WSUS, or other management services (MDT, ConfigMgr, etc.), which reinforces the idea that they are an integrated part of the maintenance strategy and not a general-purpose manual download.
After applying the enablement package, a device resetThey do not replace previous updates, and Microsoft specifies that this type of eKB does not replace any previous patch, but rather relies on the installed base up to that point.
Enablement Package and Windows 10 Enterprise LTSC/IoT: The Hybrid Scenario
One of the most peculiar situations that has arisen around these packages is the one that affects Windows 10 Enterprise LTSC 2021 / IoT Enterprise LTSC 21H2Some forums and unofficial guides have explained how to force a 22H2 package onto these systems, causing the system to identify itself as a traditional 22H2 build.
The move seems tempting: once the system is announced as 22H2, Many apps and games that require that version no longer crash.Because they only check the build number and not whether it's LTSC or not. From a software compatibility standpoint, this can be a useful shortcut.
The problem lies with support. Standard Windows 10 22H2 has a end-of-life date (EOL) clear (October 2025 for Home and Pro editions), and when the system starts to look like a conventional 22H2, Windows Update stops automatically offering patches at that time, because it believes it is dealing with a version that is already out of support.
Even so, some users have found that they can still download and install manually. Windows 10 Enterprise/IoT Enterprise LTSC 21H2 updates from the Microsoft Update Catalog, and that these updates are applied and appear listed in the Windows Update history. This raises a reasonable question: are they actually being applied to the entire system or only to the code shared with 21H2?
The technical concern is that mixing a base identified as 22H2 with patches designed for 21H2 could end up generating a hybrid scenarioPart of the operating system would continue to receive security fixes, while other components, belonging to the 22H2 branch, could remain with outdated or uncovered patches.
Enablement Package in Windows 11: 24H2, 25H2 and the path to 26H2
In Windows 11, Microsoft has further refined this model. The versions 24H2 and 25H2 share a common core and the same service branch; to learn about the 25H2 newsMany of these features are integrated into cumulative updates and enabled via eKB. The update between these features comes precisely in the form of a lightweight enablement package (eKB). The new features in 25H2 are incorporated into the 24H2 cumulative updates and remain disabled until the system installs the enablement package.
By applying that eKB, the equipment switches from 24H2 to 25H2 with a single restart and minimal downtimeThe user doesn't see a complete reinstallation or a lengthy update wizard, but rather a nearly seamless upgrade that activates features already present on the computer. This allows Microsoft to deliver a major annual release with the same level of efficiency as its monthly patches.
Microsoft is applying a similar strategy with Windows 11 26H2The preliminary builds being tested in the Dev channel, identified by the 26300 branch, point to another enablement package update on the same codebase as 24H2 and 25H2, known internally as Germanium. In practice, 26H2 will be very similar in features to 25H2, but will serve as a transitional version and for internal fine-tuning.
Meanwhile, Microsoft is also preparing a parallel branch called BromineThis is associated with Windows 11 26H1 and intended for new PCs with next-generation Arm chips. This outlines a dual strategy: Germanium for the installed x86 base and certain existing systems, and Bromine for new hardware, maintaining the enablement package model for H2 versions built on top of Germanium.
New features, security, and internal changes in Windows 11 25H2
Although 25H2 doesn't arrive with a flood of visual new features, the update brings significant changes in the safety and cleanliness of legacy componentsThe focus is more on strengthening the platform than on introducing large layers of interface.
Among the key measures is the elimination of PowerShell 2.0 and from the command line of Windows Management Instrumentation (WMIC) during installation, due to the potential vulnerabilities they represent. These are very old tools that, although still present in many scripts and environments, pose a high risk if left enabled by default.
In addition, IT administrators gain more control over bloatware thanks to new options in Group Directive and MDM CSP To remove pre-installed Microsoft default applications on Enterprise and Education devices. This makes it easier to deploy clean Windows 11 25H2 images, without unnecessary apps for the business user.
As part of that commitment to stability, Microsoft is avoiding introducing aggressive design changes or exclusive functionality in 25H2. The idea is to maintain a continuity experience for the end user, while underneath the platform is reinforced and the groundwork is laid for what will come in later versions.
All of this fits with the philosophy of the enablement package: update the version, extend the support cycle and enable certain capabilities, but without turning each H2 into a complete operating system revolution.
Deployment schedule and how to obtain the Enablement Package in Windows 11
For computers already running Windows 11 24H2, there are several ways to receive the 25H2 update via an enablement package. The simplest involves enabling the option in Windows Update. "Receive the latest updates as soon as they are available"This allows the system to receive the eKB earlier when Microsoft releases it for that device.
Even so, the company usually applies a gradual and controlled deploymentThis temporarily blocks the update on computers with potential compatibility issues (drivers, specific software, conflicting hardware, etc.). This means that even if a computer meets the requirements, it may take longer to see the 25H2 update appear in Windows Update if Microsoft detects any risks.
For those who need to update as soon as possible and know what they're doing, there's the option to download the Enablement Package specific to your architecture (x64 for AMD and Intel, or ARM64) directly from the Microsoft repositories. One example is the package identified as KB5054156 for Windows 11 25H2, which is presented as “Feature update to Windows 11, version 25H2 by using an enablement package”.
Once you've downloaded the appropriate eKB file, installation is quick: simply run it, let it apply the changes, and restart. In many cases, after just a few minutes, the system will boot into Windows 11 version 25H2, keeping your applications, settings, and data intact.
It's worth remembering that, just like in Windows 10, Not all version combinations are supported.The system must be on the correct release (for example, 24H2) and have the latest quality updates before applying the enablement package. Skipping this step may result in installation errors or unstable behavior.
Real advantages and risks of using Enablement Package
The main appeal of the Enablement Package is that it allows to update quickly, with very little disruption and with relatively low risk When the official route is followed. It does not require downloading a full ISO, does not force a system reinstallation, and minimizes the impact on the end user.
For businesses, this translates into much shorter maintenance windows, less downtime on production equipment and simpler deployment planning.
However, it's not all perfect. The fact that different versions share the same kernel means that If the base has a problem, it can easily spread. among several H2 releases that are built on that same foundation.
Another risk comes from the unsupported or “creative” scenariosSuch experiments can include forcing an eKB into an LTSC edition or manually installing patches from one branch while the system identifies as another. These experiments can generate hybrid configurations with clear implications for security and stability.
And finally, there's a perception factor: many people assume that an H2 version brings significant visible changes, when in reality, thanks to the enablement package, Much of the new stuff was already in the system weeks or months beforeIt's simply hidden. The version jump becomes more of a change in labeling and support than an immediate functional revolution.
This entire network of updates, enablement packages, and internal branches like Germanium and Bromine creates a much more incremental and quiet way for Windows to evolve than in the past. Understanding what an Enablement Package is and how it fits into this puzzle helps you make more informed decisions when updating, avoid strange combinations, and take full advantage of these H2 versions without unnecessary surprises.
