Windows 11 26H2: what changed, what to check, and whether to upgrade
Windows 11 26H2 is build 26300 and the 2026 annual feature update. Here is the support clock, the upgrade checklist, and what the release does not promise.
- Build
- 26300.9457
- Edition
- Pro (26H2)
- Architecture
- x64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-28
- Page type
- Concept
The short answer
Section titled “The short answer”Windows 11 26H2 is the 2026 annual feature update, build 26300. It became generally available on 2026-09-29. Home and Pro get updates until 2028-10-10; Enterprise and Education until 2029-10-09.
That is the durable part. “26H2” is not a promise of more FPS, lower latency or better drivers. Treat it as a new support clock and a new driver/known-issue baseline, then decide with your own hardware list.
What actually changes for a reader
Section titled “What actually changes for a reader”| Area | 26H2 | What it means |
|---|---|---|
| Build | 26300.x | A new build line, not a monthly patch on 26200 |
| Support | Home/Pro to 2028-10-10; Enterprise/Education to 2029-10-09 | You gain runway over 25H2, but not forever |
| Driver baseline | Vendors publish 26H2 packages after launch | A 25H2 driver may install; it is not the tested combination |
| Known issues | A 26H2-specific list | Check it before blaming the PC |
| Update model | Annual feature update + monthly security updates | Plan a maintenance window, not a random reboot |
The release-health page is the source of truth for build numbers, dates and known issues. A forum post that says “26H2 broke X” is a lead, not a universal bug. We only turn it into a page when we can reproduce it or cite the vendor.
Hotpatch is not a consumer magic trick
Section titled “Hotpatch is not a consumer magic trick”Microsoft lists a hotpatch calendar for 26H2. Hotpatching lets a managed device receive some security updates without a restart in the months between baselines. Availability depends on edition, management and the update channel. If you are on Home and updating manually, assume the normal restart model.
Upgrade decision table
Section titled “Upgrade decision table”| Your situation | Recommendation | Why |
|---|---|---|
| New PC, clean install | 26H2 | Current GA, longest consumer runway |
| 25H2 working, all drivers listed | Wait for the first 26H2 driver wave, then upgrade | A working machine is not a test machine |
| Game with anti-cheat or a kernel driver | Check the game/vendor statement first | Kernel components cannot be emulated or guessed |
| Managed fleet | Follow your ring plan | Pilot, then broad deploy |
| Kiosk/appliance that must not change | LTSC 2024, not 26H2 | LTSC is a fixed-purpose branch, not a faster 26H2 |
| Old PC below TPM 2.0/Secure Boot | Stay supported or replace | 26H2 keeps the same hardware floor |
A safe upgrade sequence
Section titled “A safe upgrade sequence”- Record the current state.
winver, edition, build, GPU driver version and any BitLocker recovery key location. - Check the three blockers. GPU/audio driver for 26H2, anti-cheat or VPN kernel driver, and any printer/scanner that only has a 25H2 package.
- Make a way back. A VM snapshot if virtualised; a full image or at least a restore point and a file backup if physical. The built-in rollback window is short, typically ten days.
- Upgrade, then verify. Read
winver, Device Manager, Event Viewer and one real workload. “It booted” is not verification. - Do not stack changes. Do not upgrade Windows, the GPU driver and a tuning tool on the same day. If something breaks, you will not know which change did it.
Verify build and patch
Section titled “Verify build and patch”winverGet-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber, OsHardwareAbstractionLayerGet-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5Record the build (26300.x), not just “26H2”. A machine can be on 26H2 and still be several patches behind. For a support question, the build and patch matter more than the marketing name.
What to check on day one
Section titled “What to check on day one”| Check | Pass condition |
|---|---|
winver |
26H2, build 26300.x |
| Device Manager | No unknown devices; GPU/audio/NIC healthy |
| Windows Update | No repeated failure/rollback |
| BitLocker | Protection state and recovery key location known |
| One real workload | Game/app launches, no new crash |
| Event Viewer | No new critical storage/driver errors |
Lab note
Section titled “Lab note”Our 26H2 lab VM 361 runs 26300.9457, the GA build. Microsoft’s latest 26H2 patch at the time of writing is 26300.9725 (2026-10-26 OOB), so the lab is deliberately one patch behind. We record the build on every page instead of writing “latest”.
Not verified on this page: 25H2 upgrade path, ARM64, anti-cheat behaviour, and any performance claim. This is an E1 release/decision page, not a benchmark.
What this page does not decide
Section titled “What this page does not decide”- Whether your specific laptop is supported: check the OEM page and the Windows 11 requirements.
- Whether a game runs after the update: check the game’s anti-cheat vendor.
- Whether 26H2 is faster: measure your own workload before and after; do not use a version number as a benchmark.