
Windows CLAT (WinCLAT) is Microsoft’s implementation of the customer-side translator (CLAT) for Windows 11. It allows IPv4-dependent applications to communicate over IPv6-mostly and IPv6-only networks, helping organizations move forward with IPv6 adoption while maintaining access to IPv4 resources. WinCLAT is now generally available. This page collects deployment guidance, configuration details, and troubleshooting resources for WinCLAT in the enterprise.
Last updated: November 12, 2026
WinCLAT Resources
The following articles cover WinCLAT planning, network configuration, management, and troubleshooting, organized by deployment stage.
Getting Started
- What is 464XLAT? CLAT and PLAT Explained – How the CLAT and PLAT work together to support IPv4 applications on IPv6-only networks.
- What is an IPv6-Mostly Network? – How IPv6-only, dual-stack, and IPv4-only devices share the same network using DHCP option 108.
- Windows CLAT Frequently Asked Questions (FAQ) – Commonly asked questions and answers about Windows CLAT.
- Windows CLAT Overview and Configuration – Background, operating requirements, and commands for enabling and configuring WinCLAT.
- When Windows CLAT Is Used on IPv6-Mostly and IPv6-Only Networks – Operating conditions, traffic handling, and practical deployment examples.
- WinCLAT on the IPv6 Buzz Podcast – A deep-dive discussion with Ed Horley and Tom Coffeen covering WinCLAT configuration, troubleshooting, and telemetry.
Network Prerequisites
- How Windows CLAT Discovers the NAT64 Prefix – NAT64 prefix discovery using IPv6 router advertisements and DNS.
- Configure Windows Server DNS64 for IPv6-Mostly and IPv6-Only – DNS64 configuration on Windows Server DNS to support NAT64 and WinCLAT.
- Configure DHCP Option 108 on Windows DHCP Server – Configuration guidance for supporting IPv6-mostly deployments with Windows DHCP Server.
Management and Troubleshooting
- WinCLAT PowerShell Module – A free, open-source PowerShell module to configure, manage, report, and troubleshoot WinCLAT in the enterprise. Available on GitHub and the PowerShell Gallery.
- Managing Windows CLAT with Intune Remediations – Deploy the setting that permits WinCLAT on Wi-Fi and Ethernet using Intune Remediations, then verify that WinCLAT is translating.
- Troubleshooting WinCLAT – Guide for troubleshooting WinCLAT configuration and operational issues using the WinCLAT PowerShell module.
- Understanding WinCLAT Event Logging – Event ID reference for key WinCLAT events and how to use them when troubleshooting.
- How to Identify Applications That Use Windows CLAT with Sysmon – Identify applications that are sending IPv4 traffic through WinCLAT.
Microsoft and Standards References
- Windows CLAT Is Now Generally Available – Microsoft’s general availability announcement.
- 464XLAT: Combination of Stateful and Stateless Translation (RFC 6877)
Browse all articles in the Windows CLAT category. I will update this page with additional WinCLAT deployment, management, and troubleshooting articles as they become available.
WinCLAT Requirements at a Glance
- Operating system: Windows 11 version 25H2 build 26200.9550 or later. WinCLAT is not available on Windows Server.
- Interfaces: Wi-Fi and Ethernet, in addition to cellular. CLAT must be permitted on non-cellular interfaces, which is disabled by default.
- NAT64: The network must provide a NAT64 gateway to act as the provider-side translator (PLAT).
- NAT64 prefix discovery: The NAT64 prefix must be discoverable through IPv6 router advertisements (PREF64) or DNS (DNS64).
- IPv6-mostly networks: DHCP option 108 signals capable clients to operate without native IPv4.
WinCLAT Fundamentals
The following sections explain the problem WinCLAT solves, how CLAT and 464XLAT work, and where WinCLAT fits on IPv6-mostly and IPv6-only networks.
Why WinCLAT?
Although Windows supports IPv6 natively, some applications still depend on IPv4. For example, an application might use IPv4-only networking APIs or connect directly to an IPv4 address. These applications present a compatibility challenge when the device connects to a network without native IPv4 connectivity. DNS64 and NAT64 allow IPv6-capable applications to reach IPv4-only destinations. However, applications that generate IPv4 traffic need additional support. WinCLAT addresses this requirement by translating their traffic for transport across the IPv6 network.
What is CLAT?
CLAT stands for customer-side translator. It translates IPv4 packets generated by an application into IPv6 packets. These packets travel across the IPv6 network to a NAT64 gateway, which translates them back to IPv4 for delivery to the destination. Return traffic follows the reverse process. Windows CLAT, commonly called WinCLAT, is Microsoft’s implementation of this technology. Windows 11 supports WinCLAT on Wi-Fi and Ethernet connections, extending functionality previously available only on cellular interfaces.
What is 464XLAT?
464XLAT, defined in RFC 6877, combines a customer-side translator (CLAT) on the device with a provider-side translator (PLAT), typically a NAT64 gateway, in the network. WinCLAT provides the CLAT component on Windows, and applications that communicate natively over IPv6 do not require WinCLAT translation. For a complete explanation, see What is 464XLAT? CLAT and PLAT Explained.
IPv6-Mostly and IPv6-Only Networks
WinCLAT is useful for organizations that want to reduce their reliance on IPv4 without waiting for every application and service to support IPv6. On an IPv6-only network, Windows uses IPv6 connectivity while WinCLAT supports applications that still require IPv4. On an IPv6-mostly network, capable devices can forgo native IPv4 configuration while other devices continue using IPv4 as needed. DHCP option 108 provides the signal that allows compatible clients to operate this way.
Additional Information
IPv6: Benefits, Adoption, and Enterprise Deployment
What is 464XLAT? CLAT and PLAT Explained
What is an IPv6-Mostly Network?
Windows CLAT (WinCLAT) Frequently Asked Questions (FAQ)
Need Help with WinCLAT?
Planning an IPv6-only or IPv6-mostly deployment? Have questions about WinCLAT configuration, network requirements, or application compatibility testing? Fill out the form below to get in touch.








