---
title: WARP client for Windows (version 2024.10.537.1) · Changelog
description: WARP client for Windows (version 2024.10.537.1)
chatbotDeprioritize: true
source_url:
  html: https://developers.cloudflare.com/changelog/2024-11-05-warp-windows-beta/
  md: https://developers.cloudflare.com/changelog/2024-11-05-warp-windows-beta/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.10.537.1)

Nov 05, 2024

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

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

This release contains an exciting new feature along with reliability improvements and general bug fixes. Please take time over the next few weeks to play with the new functionality and let us know what you think on both the community forum and through your account teams.

**New features:**

* Added the ability for administrators to initiate remote packet capture (PCAP) and warp-diag collection

**Changes and improvements:**

* Improved reliability of connection establishment logic under degraded network conditions
* Improved captive portal detection behavior by forcing captive portal checks outside the tunnel
* Allow the ability to configure tunnel protocol for consumer registrations
* Fixed an issue with the WARP client becoming unresponsive during startup
* Extended diagnostics collection time in warp-diag to ensure logs are captured reliably

**Known issues:**

* DNS resolution may be broken when the following condition 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, please reconnect the WARP client by toggling off and back on.
