You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- The MASQUE protocol is now the default protocol for all new WARP device
12
-
profiles.
11
+
- MASQUE is now the default [tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol) for all new WARP device profiles.
13
12
14
-
- Improvement to limit idle connections in DoH mode to avoid unnecessary
15
-
resource usage that can lead to DoH requests not resolving.
13
+
- Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/#gateway-with-doh) to avoid unnecessary resource usage that can lead to DoH requests not resolving.
16
14
17
-
- Improvements to maintain Global WARP Override settings when switching
18
-
between organization configurations.
15
+
- Improvements to maintain [Global WARP override](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#global-warp-override) settings when [switching between organizations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-warp).
19
16
20
17
- Improvements to maintain client connectivity during network changes.
Copy file name to clipboardExpand all lines: src/content/warp-releases/macos/ga/2025.7.176.0.yaml
+7-6Lines changed: 7 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,17 @@ releaseNotes: |-
2
2
This release contains minor fixes and improvements.
3
3
4
4
**Changes and improvements**
5
-
- Fixed a bug preventing the warp-diag captive-portal command from running successfully due to the client not parsing SSID on macOS.
6
-
- Improvements to maintain Global WARP Override settings when switching between organization configurations.
7
-
- The MASQUE protocol is now the default protocol for all new WARP device profiles.
8
-
- Improvement to limit idle connections in DoH mode to avoid unnecessary resource usage that can lead to DoH requests not resolving.
5
+
- Fixed a bug preventing the `warp-diag captive-portal` command from running successfully due to the client not parsing SSID on macOS.
6
+
- Improvements to maintain [Global WARP override](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#global-warp-override) settings when [switching between organizations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-warp).
7
+
- MASQUE is now the default [tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol) for all new WARP device profiles.
8
+
- Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/#gateway-with-doh) to avoid unnecessary resource usage that can lead to DoH requests not resolving.
9
9
- Improvements to maintain client connectivity during network changes.
10
-
- The WARP client now supports macOS Tahoe (Version 26.0)
10
+
- The WARP client now supports macOS Tahoe (version 26.0).
11
11
12
12
**Known issues**
13
13
- macOS Sequoia: Due to changes Apple introduced in macOS 15.0.x, the WARP client may not behave as expected. Cloudflare recommends the use of macOS 15.4 or later.
14
-
- Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To learn more about configuring a fallback server, please reference the [Zero Trust documentation](https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/#route-traffic-to-fallback-server).
14
+
15
+
- Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to [Route traffic to fallback server](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/#route-traffic-to-fallback-server).
Copy file name to clipboardExpand all lines: src/content/warp-releases/windows/ga/2025.7.176.0.yaml
+7-6Lines changed: 7 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -2,25 +2,26 @@ releaseNotes: |-
2
2
This release contains minor fixes and improvements.
3
3
4
4
**Changes and improvements**
5
-
- The MASQUE protocol is now the default protocol for all new WARP device profiles.
6
-
- Improvement to limit idle connections in DoH mode to avoid unnecessary resource usage that can lead to DoH requests not resolving.
5
+
- MASQUE is now the default [tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol) for all new WARP device profiles.
6
+
- Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/#gateway-with-doh) to avoid unnecessary resource usage that can lead to DoH requests not resolving.
7
7
- Improvement to maintain TCP connections to reduce interruptions in long-lived connections such as RDP or SSH.
8
-
- Improvements to maintain Global WARP Override settings when switching between organization configurations.
8
+
- Improvements to maintain [Global WARP override](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#global-warp-override) settings when [switching between organizations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-warp).
9
9
- Improvements to maintain client connectivity during network changes.
10
10
11
11
**Known issues**
12
12
- For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum [Windows 11 24H2 KB5062553](https://support.microsoft.com/en-us/topic/july-8-2025-kb5062553-os-build-26100-4652-523e69cb-051b-43c6-8376-6a76d6caeefd) or higher for resolution.
13
13
14
-
- Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to [Route traffic to fallback server](https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/#route-traffic-to-fallback-server).
15
14
16
-
- Devices with KB5055523 installed may receive a warning about Win32/ClickFix.ABA being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to [version 1.429.19.0](https://www.microsoft.com/en-us/wdsi/definitions/antimalware-definition-release-notes?requestVersion=1.429.19.0) or later.
15
+
- Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to [Route traffic to fallback server](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/#route-traffic-to-fallback-server).
16
+
17
+
- Devices with KB5055523 installed may receive a warning about `Win32/ClickFix.ABA` being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to [version 1.429.19.0](https://www.microsoft.com/en-us/wdsi/definitions/antimalware-definition-release-notes?requestVersion=1.429.19.0) or later.
17
18
18
19
- DNS resolution may be broken when the following conditions are all true:
19
20
- WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
20
21
- A custom DNS server address is configured on the primary network adapter.
21
22
- The custom DNS server address on the primary network adapter is changed while WARP is connected.
22
23
23
-
To work around this issue, please reconnect the WARP client by toggling off and back on.
24
+
To work around this issue, reconnect the WARP client by toggling off and back on.
0 commit comments