---
title: WARP client for Windows (version 2024.11.309.0) · Changelog
description: WARP client for Windows (version 2024.11.309.0)
chatbotDeprioritize: true
source_url:
  html: https://developers.cloudflare.com/changelog/2024-11-18-warp-windows-ga/
  md: https://developers.cloudflare.com/changelog/2024-11-18-warp-windows-ga/index.md
---

# Changelog

New updates and improvements at Cloudflare.

[Subscribe to RSS](https://developers.cloudflare.com/changelog/rss/index.xml)\
[View all RSS feeds](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/)

![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_ZEA2nF.svg)

[← Back to all posts](https://developers.cloudflare.com/changelog/)

## WARP client for Windows (version 2024.11.309.0)

Nov 18, 2024

[Zero Trust WARP Client](https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/)

A new GA release for the Windows WARP client is now available on the [stable releases downloads page](https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/download-warp/).

This release contains minor fixes and improvements.

**Changes and improvements:**

* Fixed an issue where SSH sessions and other application connections over TCP or UDP could drop when a device that is using MASQUE changes its primary network interface.
* Fixed an issue to ensure the Cloudflare root certificate (or custom certificate) is installed in the trust store if not already there.
* Fixed an issue with the WARP client becoming unresponsive during startup.
* Extended diagnostics collection time in `warp-diag` to ensure logs are captured reliably.
* Fixed an issue that was preventing proper operation of DNS-over-TLS (DoT) for consumer users.

**Known issues:**

* DNS resolution may be broken when the following conditions are all true:

  * WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
  * A custom DNS server address is configured on the primary network adapter.
  * The custom DNS server address on the primary network adapter is changed while WARP is connected.

  To work around this issue, reconnect the WARP client by toggling off and back on.
