Windows Update's "Get the latest updates as soon as they're available" toggle does not guarantee that a new feature update appears immediately. Version 26H2 is distributed as a small enablement package on top of 25H2, but Microsoft releases it in phases and can suppress it for specific devices through compatibility holds. If your machine reports "you're up to date," the most likely explanations are a staged rollout that has not reached you yet, a safeguard hold on your hardware or driver configuration, or a servicing prerequisite that is not yet satisfied.
How 26H2 is actually delivered
Windows 11 26H2 shares the same servicing branch as 25H2 (and 24H2 before it). The new features already exist in the operating system binaries you have installed; they are simply switched off. Turning them on requires a small enablement package, referenced as KB5121794, which flips the switch and bumps the reported version from 25H2 to 26H2. Because the payload is tiny, the installation is quick and only needs a single restart.
This design has two practical consequences. First, if your device is not yet on a sufficiently recent cumulative update, the enablement package will not be offered. Second, because the package is a feature update in Windows Update's eyes, it is still subject to phased rollout and safeguard holds, just like a full feature update would be.
Diagnosing why the offer is missing
Work through these checks in order:
- Confirm your current version. Run
winverand verify you are on 25H2 with the latest cumulative update installed. The enablement package requires the September 2026 preview cumulative update (KB5124010, build 26100.9546) or anything later. - Check for safeguard holds. Open Settings → Windows Update and look for any message about compatibility issues. Microsoft also publishes known issues on the Windows release health dashboard; if your processor, driver, or installed software matches a documented problem, the update is deliberately withheld until a fix ships.
- Verify hardware eligibility. 26H2 only targets devices that meet Windows 11 hardware requirements. Older unsupported hardware will never see the offer.
- Check update policies. If the machine is managed by an organization, or if you have used tools to defer feature updates, a policy may be blocking the offer. The Group Policy setting "Select the target Feature Update version" or a registry value under
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdatecan pin the device to 25H2 indefinitely.
The simplest fix: wait for the rollout
If nothing is wrong with your device, the answer is patience. Microsoft staggers feature update availability over weeks so that problems can be caught on a small population first. Clicking Check for updates repeatedly does not move you up the queue. Once your device's rollout phase begins, the enablement package will appear as a normal feature update, typically labeled "Windows 11 26H2" with a small download size.
Forcing the upgrade manually
If you need 26H2 now and no hold applies, you have several options:
- Install the enablement package directly. Unlike most cumulative updates, the 26H2 enablement package is not published in the Microsoft Update Catalog. However, standalone
.msuinstallers for both x64 (Intel/AMD) and ARM64 devices are available through Microsoft's official download channels. Download the file matching your architecture and run it; the update installs and requires a restart. Make sure the prerequisite cumulative update is already in place first. - Use the Installation Assistant from Microsoft's Windows 11 download page. It performs an in-place upgrade while keeping your files and applications.
- Mount a 26H2 ISO and run
setup.exe, choosing the option to keep personal files and apps. This is the most reliable route when Windows Update is misbehaving.
Before any manual upgrade, back up important data and confirm you have at least 20 GB of free space on the system drive.
Preventing future rollout delays
Keep your device on current cumulative updates, since feature enablement packages frequently depend on a recent servicing baseline. Avoid pinning a target feature update version in policy unless you are deliberately managing an enterprise fleet. And remember that the "latest updates" toggle accelerates delivery of optional and preview updates; it does not override phased feature update deployment or safeguard holds.
Frequently Asked Questions
Does "Get the latest updates as soon as they're available" force feature updates?
No. It opts you into preview and optional updates as early as possible, but feature updates like 26H2 are still gated by phased rollout and compatibility holds. Being opted in only means you are considered early in the rollout, not that you get it on day one.
Why is the enablement package so small compared to a normal feature update?
Because 25H2 and 26H2 share the same servicing branch, the new features are already present but disabled on your device. The enablement package only activates them, so the download is a few megabytes rather than several gigabytes.
Can I install 26H2 if I am still on 24H2?
Yes, but the path differs. Devices on 24H2 receive the enablement package for 25H2 first, then the 26H2 enablement package. Alternatively, a full upgrade via the Installation Assistant or ISO takes you straight to 26H2.
Is the 26H2 enablement package available in the Microsoft Update Catalog?
No. It is distributed as standalone .msu files through Microsoft's download channels instead, with separate packages for x64 and ARM64 systems.
How do I know whether a compatibility hold is blocking my device?
Check Windows Update in Settings for a notice about known compatibility issues, and review Microsoft's release health page for documented problems affecting your hardware, drivers, or applications. Holds are lifted automatically once a fix is available.
Will installing the enablement package manually cause problems later?
No. Once installed, your device is on 26H2 and receives normal monthly cumulative updates. The installation method does not affect future servicing.