On September 29 (US time), Microsoft began general availability of version 26H2, called the "Windows 11 2026 Update." Eligible PCs running 24H2 or 25H2 can move to it by applying a small enablement package and restarting once.
Even though the update itself is small, support deadlines and the default settings of some enterprise features are changing. Support for 24H2 Home/Pro ends on October 13, while 25H2 still has some time left. PCs running 26H1 follow a different update path from 24H2 and 25H2.
Whether you should hurry to update depends on which version of Windows 11 you use now and which features you rely on.
A small update with real significance
26H2 is an annual update built on the same codebase as 24H2 and 25H2. According to Microsoft's rollout announcement, most of the necessary components have already been delivered to PCs through earlier monthly updates.
The enablement package used this time works by turning on features that were installed in advance. Compared with traditional large updates that replace the entire OS, it reduces download size and the burden of installation.
However, download size and update time will not be the same on every PC. The approach assumes the target device has already received the required updates. What Microsoft has described is a design that allows a move with a small package and a short restart, not a guarantee of how long the update will take on any individual PC.
Nor are available features determined by version number alone.
In Windows 11, new features are added gradually through monthly updates rather than waiting for the annual update. As a result, some of the improvements presented for 26H2 may already be available to you on 25H2 or 24H2.
26H2 bundles those changes into an annual version, and it is also a milestone that renews the support period. It is not the case that "if you don't update to 26H2, you can't use any of the new features."
What changes in daily use and security
Microsoft's list of changes includes the ability to place the taskbar at the top, bottom, left, or right of the screen, and a setting to reduce the height of the taskbar itself, not just its icons.
The Start menu can now be resized, and the "Pinned," "Recent," and "All apps" sections can each be shown or hidden individually. The app list also gains category and grid views. For users who want more working space, being able to change the taskbar's position and height is a practical improvement.
Windows Search gains a preview feature before you open a result, along with better handling of misspelled app names and partial matches. A setting that automatically adds frequently used folders to the search scope is also available.
File Explorer supports new compression formats, and it now keeps your view and sort settings even when an app opens the Downloads or Documents folder. Microsoft says it also improved the launch speed and responsiveness of the Home page, but it has not given specific improvement figures.
Some security features must be explicitly enabled by users or administrators.
Administrator protection, which lets you use administrator privileges only when needed, and Sysmon, which records system events useful for detecting and investigating threats, are both disabled by default.
Meanwhile, Smart App Control, which blocks the execution of suspicious apps, can now be turned on or off without a clean install of Windows.
In other words, simply updating to 26H2 does not automatically enable every added security feature.
For enterprises, features such as Windows settings backup, per-app taskbar actions, and some File Explorer improvements move from a state that could previously be controlled temporarily to features that are enabled by default.
The guide for IT administrators also explains that existing management policies continue to take precedence and that usage conditions differ by feature. Even with an update built on the same codebase, there may be changes to how enterprise PCs are operated and managed.
Some AI-related features also come with licensing or supported-device requirements.
For example, using Copilot to summarize documents in OneDrive or SharePoint from File Explorer requires a compatible Microsoft 365 subscription and a Copilot license. The feature that lets voice access use natural-language commands is available only on supported Copilot+ PCs.
Being able to update Windows 11 to 26H2 is a separate matter from being able to use features that require paid services or compatible hardware.
Why the urgency depends on your current version
For 24H2 Home/Pro users, the October 13 end of support is imminent.
Even if the feature differences seem small, you need to move to a supported version to keep receiving security updates.
Organizing Microsoft's published lifecycle information by version, support ends on October 13, 2026 for 24H2 Home/Pro, October 12, 2027 for 25H2, and October 10, 2028 for 26H2.
Because 26H1 uses a different codebase, it is not among the devices eligible for the move to 26H2 via the same enablement package as 24H2 and 25H2.
| Current version | Update path to 26H2 | Home/Pro end of support | Enterprise/Education end of support |
|---|---|---|---|
| 24H2 | Delivered to eligible devices via enablement package | October 13, 2026 | October 12, 2027 |
| 25H2 | Delivered to eligible devices via enablement package | October 12, 2027 | October 10, 2028 |
| 26H1 | Uses a different codebase | March 14, 2028 | March 13, 2029 |
| 26H2 | This year's annual version | October 10, 2028 | October 9, 2029 |
The table is based on the end dates for standard editions listed in Microsoft's release information as of October 2, 2026, combined with the 26H1 update policy and this rollout's targets. LTSC is not included.
26H1 is a version offered in the first half of 2026 for some new PCs, and monthly updates will continue to be provided for it. There is no need to confuse the fact that it is not a regular update target for 26H2 with end of support.
If you are on 25H2, you have time to check known issues and peripheral compatibility before updating.
If you are on 24H2 Home/Pro and postpone the update, you should plan to move to a supported version before support ends on October 13. Enterprise/Education editions of 24H2 have different support deadlines, so there is no need to rush based on the same date as consumer editions.
To get 26H2 early, open "Windows Update" in "Settings" and turn on "Get the latest updates as soon as they're available."
26H2 will appear once your device is eligible, but Microsoft will expand delivery gradually over the coming months. If it does not appear, it may simply not be your device's turn yet, or delivery may be temporarily blocked due to a compatibility issue.
Just because 26H2 shares a codebase with 24H2 and 25H2 does not mean it is safe to bypass a compatibility hold by updating manually.
Which environments the 3 known issues affect
The official release health information lists three known issues as of October 2.
All three are listed as "Mitigated," which should be distinguished from "Resolved," meaning completely fixed.
| Issue | Main conditions affected | Key points of the response |
|---|---|---|
| USB audio devices fail to start or produce no sound | Some USB Audio Class 1.0 devices | Code 10 and similar errors occur. Remaining problems are to be fixed in a future update |
| Loss of trust relationship with the domain | Credential Guard-protected machine accounts where enforced Machine Identity Isolation settings do not match environment conditions | Administrators disable the feature using the legacy configuration method and repair the trust relationship after a restart |
| Black screen after sign-in, desktop not displayed | Mainly Azure Virtual Desktop hosts using FSLogix and some existing profiles | Temporary workaround by manually launching explorer.exe. Apply the Known Issue Rollback policy on managed devices |
It would not be appropriate to assume the USB audio issue affects all USB audio devices. Likewise, the black screen problem does not occur on every ordinary home PC.
The domain-related issue also does not mean the update forcibly enables Machine Identity Isolation on every device. The problem arises in environments where the existing configuration method does not match requirements such as a Windows Server 2025 domain functional level or higher.
The Known Issue Rollback for the black screen problem is also not completed simply by installing a group policy. Administrators must configure the policy and restart the devices.
Microsoft also lists Windows versions other than 26H2 as affected by this issue. Just because it appears on the 26H2 release health page does not mean it first occurred because of this update.
For enterprises, the practical approach is to deploy first to representative devices in stages, confirm that business apps and authentication systems work correctly, and then widen the rollout.
Old management scripts should also be checked. The WMIC command was removed in 24H2 and later, and there is no longer a way to reinstall it as an optional feature.
This does not mean WMI itself was removed, but it affects scripts and operations that call WMIC directly.
8GB PCs are not excluded
Windows 11's minimum memory requirement is 4GB. A PC with 8GB of memory is therefore not excluded from 26H2 for that reason alone.
Copilot+ PCs, on the other hand, require 16GB of RAM plus a compatible NPU capable of 40 TOPS or more, among other things.
The conditions for being able to update Windows 11 to 26H2, for being able to use AI features, and for comfortably handling everyday tasks are each separate matters.
There are also user reports that memory usage dropped after updating to 26H2.
In a post, Reddit user shutter_singh reported that memory usage at startup fell from about 6.9GB before the update to about 4.8–5GB afterward.
However, this is only a result from one user's environment. It was not a controlled comparison with consistent conditions such as resident apps and measurement timing, so it is unclear whether the improvement comes from 26H2 itself or whether an 8GB PC would see a similar effect.
Meeting the minimum requirements also does not guarantee a comfortable experience.
To see what 26H2 changes on an 8GB PC, you would need to launch your usual browser and apps under the same conditions and compare not just memory usage but also wait times and responsiveness during use.
A drop in memory usage right after startup and more headroom when using several apps at once should be evaluated separately.
When considering a move to 26H2, first check which version of Windows 11 you are currently using and which peripherals and business functions you want to keep using.
24H2 Home/Pro users in particular should confirm the October 13 end-of-support date and whether 26H2 is being offered on their PC.
If you can confirm before updating that your environment is not affected by the known issues, 26H2, which uses the shared codebase, offers a chance to extend Windows 11's support period without greatly changing your environment.