# Which Windows 11? 26H2, 25H2, LTSC 2024 and ARM64

> Compare Windows 11 26H2, 25H2, LTSC 2024 and ARM64 by support window, hardware, licensing and use case, then pick one.

**Tested on**

- Build: 26300.9457
- Edition: Pro (26H2) / LTSC 2024
- Architecture: x64
- Evidence: E2
- Verified: 2026-10-28
- Test machine: PVE 9.2.2 VM 361 (26H2 Pro) + VM 360 (LTSC 2024); 8GB/4 vCPU each; vTPM 2.0 + Secure Boot

## The short answer

- **Most people installing a current PC:** Windows 11 **26H2**. It is the current GA release (build 26300), supported to 2028-10-10 on Home/Pro and 2029-10-09 on Enterprise/Education.
- **A PC that must not change for years:** Windows 11 **LTSC 2024** (build 26100, support to 2029-10-09). It is not a “faster Windows”; it is a fixed-purpose release with a different licensing channel.
- **Still on 25H2:** supported until 2027-10-12 (Home/Pro) and 2028-10-10 (Enterprise). Move when your drivers and games are known-good on 26H2, not on day one.
- **Snapdragon X / ARM laptop:** Windows 11 **ARM64**. Same release cadence, different driver model, and x64 apps run through Prism.

## Decision table

| You have | Pick | Why | Watch out |
|---|---|---|---|
| Current x86 laptop or desktop | 26H2 Home/Pro | Current GA, longest consumer support | Fresh release: check GPU/audio drivers and anti-cheat |
| Managed or mission-critical workstation | 26H2 Enterprise, or LTSC 2024 | Enterprise support to 2029; LTSC stays fixed | LTSC needs the right volume licensing channel |
| Snapdragon X device | 26H2 ARM64 | Native ARM64 build, Prism for x64 apps | Kernel drivers and some anti-cheat titles are still x64-only |
| Old PC below TPM 2.0 / Secure Boot | Stay on a supported build or replace | 26H2 keeps the same hardware floor | Do not follow “bypass” scripts; you lose the support path |
| Windows 10 today | Plan a move | Windows 10 support ended 2025-10-14; consumer ESU now runs to 2027-10-12 | Check CPU/TPM before buying a licence |

## 26H2 vs 25H2: what actually changes for a reader

- **Build number:** 26300.x vs 26200.x. Every page on this site records the build it was verified on.
- **Support window:** 26H2 adds roughly one year over 25H2 on the same edition.
- **Driver baseline:** vendors ship 26H2 packages after launch; a 25H2 driver may install but is not the tested combination.
- **Known issues:** 26H2 has its own list (black screen after sign-in, RDP `0xC000000D` for non-admin users, AC-3 audio apps, domain trust). Check it before blaming your hardware.

## LTSC 2024 is not “Windows without bloat”

LTSC removes features on a fixed cadence and is licensed through volume channels. It is a good fit for kiosks, lab machines and appliances; it is a poor fit for a gaming laptop that needs the latest GPU stack and Store apps. We explain the boundary; we do not distribute images or keys.

## ARM64: the compatibility layer is good, not universal

Prism runs x64 applications, including AVX/AVX2 paths, on Snapdragon X. That covers most browsers, Office and many games. It does **not** make x64 kernel drivers work: anti-cheat, some VPN clients and specialized hardware tools can still refuse to run. Check the vendor page before buying an ARM laptop for a specific game or device.

## Lab check: 26H2 and LTSC 2024 (E2)

> **Note: Scope**
>
> This run covers **26H2 Pro** and **LTSC 2024**. 25H2 and ARM64 remain E1 on this page. For the full platform guide, including 26H1 vs 26H2 and the OnArm.net compatibility database, see [Windows on Arm in 2026](https://winbook.fyi/en/windows/platform/arm64/).

> **Tip: Next step**
>
> Picked 26H2? The [clean install procedure](https://winbook.fyi/en/windows/install/clean/) covers UEFI, TPM 2.0, partitions and the post-install checks.

### 26H2 Pro (VM 361)

| Item | Observed |
|---|---|
| Edition | Windows 11 Pro (`Professional`) |
| Display version | 26H2 |
| Build | 26300.9457 (`UBR` 0x24f1) |
| Architecture | x64 |
| Firmware | UEFI, Secure Boot On |
| TPM | 2.0, “ready for use” (IBM vTPM) |
| Install date | 2026-10-28 |
| Processor | QEMU Virtual CPU, 4 vCPU |
| Locale | en-US |

`msinfo32` reports “Microsoft Windows 11 Pro”, version `10.0.26300 Build 26300`. The registry `ProductName` still reads “Windows 10 Pro” — a branding string in the 26H2 image, not a Windows 10 build. The ISO was `Windows11_Client_x64_en-us_26300_9457.iso`, SHA-256 `BD4307…A650`.

### LTSC 2024 (VM 360)

| Item | Observed |
|---|---|
| Edition | Enterprise LTSC 2024 (`EnterpriseS`) |
| Display version | 24H2 |
| Build | 26100.1742 |
| Architecture | x64 |
| Firmware | OVMF, Secure Boot on |
| TPM | 2.0, ready |
| Install date | 2026-09-01 |
| Hotfixes | KB5043113, KB5043080, KB5042098 (2024-09-06) |
| Activation | LicenseStatus 5, grace 0 — the lab ISO is **not activated** |

The registry `ProductName` still reads “Windows 10 Enterprise LTSC 2024”; that is the branding string in the LTSC 2024 image, not a Windows 10 build.

**Not verified:** 25H2, ARM64, activation, and upgrade paths. Do not read this table as “LTSC is activated” or “26H2 is licensed”.

## What this page does not decide

- Whether your specific laptop is supported: check the OEM page and the [Windows 11 requirements](https://learn.microsoft.com/en-us/windows/whats-new/windows-11-requirements).
- Whether a game runs on ARM: check the game’s anti-cheat and the vendor’s ARM statement.
- Whether you should upgrade today: if 25H2 is working and 26H2 drivers are not listed for your GPU, wait.

## Sources

- [Microsoft — Windows 11 release information](https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information)
- [Microsoft — Supported versions of Windows client](https://learn.microsoft.com/en-us/windows/release-health/supported-versions-windows-client)
- [Microsoft — Windows 11 requirements](https://learn.microsoft.com/en-us/windows/whats-new/windows-11-requirements)
- [Microsoft Q&A — Windows 11 ARM64 ISO](https://learn.microsoft.com/en-us/answers/questions/5619305/windows-11-enterprise-for-arm-based-pc)

---

Source: https://winbook.fyi/en/windows/start/versions/