Windows Client v5.14$$$During the week of March 17; 2025; we are starting the rollout of Windows Client version 5.14. This version contains bug fixes and enhancements.$$$In addition; Windows Client 5.14 installs a driver to support Anti-Tampering. This driver is not loaded unless you enable Anti-Tampering. For more information; see Working with Anti-Tampering for the Cato Client (EA).

Windows Client v5.13$$$From January 5; 2025 we started the rollout of Windows Client version 5.13. This version contains:$$$$$$The following DEM enhancements are now supported with this version:$$$$$$Underlay Performance Monitoring in Socket Last Mile: Identify and diagnose out-of-tunnel issues that could impact last-mile performance$$$$$$Use Multiple Devices: DEM hardware metrics are now grouped by device name; helping you easily understand the performance of each device when there are multiple devices for the same user$$$$$$Support for Different LAN Gateways: LAN gateway probes are now grouped by LAN gateway IP; letting you easily understand the performance of each LAN gateway when different gateways are present at different timeframes$$$$$$Bug fixes and enhancements

Windows Client v5.12$$$From November 3; 2024; we started the rollout of Windows Client version 5.12. This version contains:$$$Bug fixes and enhancements; including:$$$Enabling the Always-On policy with the registry key blocked access to Microsoft Self-Service Password Reset from the lock screen

Windows Client v5.11.9$$$From August 16; 2024; we are starting the rollout of Windows Client version 5.11.9. This version contains:$$$$$$Bug Fix:$$$$$$Resolved a connectivity issue impacting topologies that include a misconfigured DNS setting on the device network adapter set with an IPv6 address that does not respond

Windows Client v5.11$$$From July 14; 2024; we are starting the rollout of Windows Client version 5.11. This version contains:$$$$$$IPv6 Support for Last Mile Connection: Users can connect remotely over ISPs that provide last-mile IPv6-only connections. Both IPv6 and IPv4 connections are now supported.$$$$$$Authenticating with Windows Credentials Supported on Azure Hybrid AD Joined Devices: Users on Azure Hybrid AD Joined Devices can authenticate with their Windows credentials for an improved user experience. You can configure the Client to launch; add a user; authenticate; and connect without any user action. Azure AD with MFA is now also supported.$$$$$$Bug Fix:$$$$$$If a login attempt failed; in some cases users were unable to connect to the network

Windows Client v5.10.34$$$From June 6th; 2024; we are starting the rollout of Windows Client version 5.10.34. This version contains an important security update and bug fixes.

Windows Client v5.10$$$Windows Client v5.10: Over the next few weeks; we will start the rollout of Windows Client v5.10. This version contains:$$$$$$User Notifications for CASB and DLP: The device displays a notification to the user when their activity is blocked by App Control or Data Control rules. This educates the user about which app was blocked and why.$$$Improved Client messages for failed upgrades and token expiration$$$Stability enhancements; including Pre-login mode$$$Bug fixes

Windows Client v5.9$$$From November 20th; 2023; we started the roll out of Windows Client version 5.9. This version contains:$$$$$$New Experience for Secured Remote Internet Access (Early Availability): We are introducing new features that transform the user experience for secured Internet access. Users can benefit from Internet security based on a one time authentication and Always-On can be used while ensuring business continuity:$$$$$$Remote Internet Security with One Time Authentication: For secured Internet access; remote users only need to authenticate once.$$$$$$Cato Security policies are always enforced for Internet traffic with this mode; users continuous access without needing to re-authenticate.$$$$$$New Bypass Mode for Always-On: Users can temporarily access the Internet without waiting for admin approval. Users provide a reason in the Client and they can temporarily bypass Always-On and disconnect the Client.$$$$$$The duration of the bypass can be configured by administrators$$$$$$Always-On Recovery Mode: Users can access the Internet if a connection to the Cato Cloud is unavailable. For example; if a Captive Portal prevents the Client connecting to the Cato Cloud; users can still access the Internet. However; Cato security is bypassed.$$$$$$Device Posture Check Improves Security Posture: You can now include a check for DLP within your Device Posture Profiles. The Device Posture Profile can be included in your Client Connectivity and security policies.$$$$$$Client UI Improvements: We have updated the Client UI; to display:$$$$$$A message if the Client experiences issues establishing a connection to the Cato Cloud$$$$$$The indication if Always-On is enforced is moved to the Statistics page$$$$$$Updated Vendors and Versions for Device Posture Checks: We updated the OPSWAT framework used by the Client to version 4.4.3.3714