Windows 11 IPv6 CLAT on Wi-Fi and Ethernet: what KB5127936 adds

This News article explains what the KB documents for builds 26200.9818 (25H2) and 26300.9818 (26H2), how that wording relates to the Tech Community generally available note for Windows 11 Client 25H2 from build 26200.9550, and which requirements and limits Microsoft states (SLAAC; no DHCPv6 Prefix Delegation; no WSL). It does not rehash other TricknFix pieces from the same preview package (USB Audio Class 1.0 Code 10, BitLocker PIN retry handling, Edge Accelerated App Launch, Always On VPN, Smart App Control grayed out, File Explorer customizable context menu) or treat Modernized AutoPlay as the main angle.

No hands-on CLAT lab test is claimed here. Facts follow KB5127936 and the Tech Community networking post consulted on 6 November 2026 (Europe/Paris). On a managed PC, ask your IT team before enabling CLAT, changing Group Policy, or installing an optional preview.

CLAT means Customer-side Translator. In the 464XLAT architecture, the client translates IPv4 traffic into IPv6 toward a provider-side translator (PLAT / NAT64). The Tech Community post describes that translation as stateless on the client side: IPv4-only apps can keep talking to IPv4 destinations while the wire path is IPv6-only.

That matters for IT because many line-of-business tools still assume IPv4 sockets even when the campus or branch has already dropped dual-stack. CLAT is a compatibility bridge, not a claim that every IPv4 app becomes “native IPv6.”

KB5127936 is dated 28 October 2026 and applies to Windows 11 version 26H2 and Windows 11 version 25H2 (builds 26300.9818 and 26200.9818).

Under gradual rollout, the item [Windows IPv6 networking support] states:

The same KB notes that Windows 11 version 24H2 no longer receives non-security preview updates starting with the October 2026 release — so this preview track is about 25H2 / 26H2, not a 24H2 optional package.

Gradual rollout means the documented feature does not arrive on every device at once even after the package is installed.

On 27 October 2026, Jim Alumbaugh published Windows CLAT is Now Generally Available on the Microsoft Tech Community networking blog. That post states CLAT is generally available on Windows 11 Client 25H2 starting with build 26200.9550.

The post’s feature summary includes:

In a 2 November 2026 comment reply on the same thread, JimAlumbaugh stated that with build 26200.9550 or later, no additional patches are required beyond what is documented — without claiming “zero configuration” beyond the documented enablement path.

Read both sources together without inventing a false gap: Tech Community marks GA from 26200.9550 on 25H2; KB5127936’s preview notes (builds 26200.9818 / 26300.9818) are the first KB page that documents Wi-Fi/Ethernet CLAT for 25H2/26H2 with the netsh / GPO wording under gradual rollout. This article does not claim CLAT was absent before build 9818. Cellular details beyond what each source states are not invented here; the KB bullet quoted above focuses on Wi-Fi and Ethernet.

Microsoft’s KB wording is explicit:

If your design still depends on DHCPv6 PD for client addressing, or you expected WSL guests to inherit CLAT automatically, the documented limits say otherwise as of these sources.

This article does not invent a recommended production GPO baseline, a performance benchmark, or a claim that every IPv4 app works through CLAT.

Separate articles already cover other features or known issues from the same preview package; they are different intents:

Modernized AutoPlay from the same KB is covered as a community discussion in this cycle, not as this article’s main angle.