|
| 1 | +--- |
| 2 | +title: WARP client for Windows (version 2025.2.460.1) |
| 3 | +description: WARP client for Windows (version 2025.2.460.1) |
| 4 | +date: 2025-02-03T11:00:00Z |
| 5 | +--- |
| 6 | + |
| 7 | +A new beta release for the Windows WARP client is now available on the [Downloads page](/cloudflare-one/connections/connect-devices/warp/download-warp/beta-releases/). This release contains significant improvements to our captive portal / public Wi-Fi detection logic. If you have experienced captive portal issues in the past, re-test and give this version a try. |
| 8 | + |
| 9 | +**Changes and improvements** |
| 10 | + |
| 11 | +- Improved [captive portal detection](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals/) to make more public networks compatible |
| 12 | + and have faster detection. |
| 13 | +- Improved error messages shown in the app. |
| 14 | +- Added the ability to control if the WARP interface IPs are [registered with |
| 15 | + DNS servers](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#warp-interface-ip-dns-registration) or not. |
| 16 | +- Removed DNS logs view from the Windows client GUI. DNS logs can be viewed as |
| 17 | + part of `warp-diag` or by viewing the log file on the user's local directory. |
| 18 | +- Fixed issue that would result in a user receiving multiple re-authentication |
| 19 | + requests when waking their device from sleep. |
| 20 | +- WARP tunnel protocol details can now be viewed using the `warp-cli tunnel stats` |
| 21 | + command. |
| 22 | +- Improvements to [Windows multi-user](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/windows-multiuser/) including support for fast user |
| 23 | + switching. If you are interested in testing this feature, reach out to |
| 24 | + your Cloudflare account team. |
| 25 | +- Fixed issue with device revocation and re-registration when switching |
| 26 | + configurations. |
| 27 | +- Fixed issue where DEX tests would run during certain sleep states where the |
| 28 | + networking stack was not fully up. This would result in failures that would be |
| 29 | + ignored. |
| 30 | + |
| 31 | +**Known issues** |
| 32 | + |
| 33 | +- DNS resolution may be broken when the following conditions are all true: |
| 34 | + |
| 35 | + - WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode. |
| 36 | + - A custom DNS server address is configured on the primary network adapter. |
| 37 | + - The custom DNS server address on the primary network adapter is changed while WARP is connected. |
| 38 | + |
| 39 | + To work around this issue, reconnect the WARP client by toggling off and back on. |
0 commit comments