• Fixes an issue where Zscaler Client Connector did not always clear the DNS suffixes when moving from a machine tunnel to a user tunnel.
• Fixes an issue where the ZSATray process could block another application, such as PowerBuilder, from starting.
• Fixes a driver error that occurred when upgrading Zscaler Client Connector for customers with anti-tampering already or previously enabled.
• Fixes an issue where Zscaler Client Connector did not switch to the correct Network Type on a device using a USB Ethernet adapter.
• Fixes an issue where a Detect Antivirus device posture check did not pass, even though the antivirus specified in the antivirus name (AV Name) was running on the system.
• Fixes an issue where Zscaler Client Connector prevented removing a device from isolation through the Microsoft Defender portal with Microsoft Intune.
• Fixes an issue where network transfer data could be duplicated (e.g., print jobs, file transfers) after upgrading to Zscaler Client Connector version 4.5.0.337 for Windows.
• Fixes an issue where Zscaler Client Connector did not fall back to the redirect broker (any.broker) when switching from an Off Trusted Network to a Trusted Network.
• Fixes an issue where Zscaler Client Connector did not correctly close an existing Zscaler Private Access (ZPA) app session when in the ZPA forced reauthentication state.

• Fixes an issue where Zscaler Client Connector did not always clear the DNS suffixes when moving from a machine tunnel to a user tunnel.
• Fixes an issue where the ZSATray process could block another application, such as PowerBuilder, from starting.
• Fixes a driver error that occurred when upgrading Zscaler Client Connector for customers with anti-tampering already or previously enabled.
• Fixes an issue where Zscaler Client Connector did not switch to the correct Network Type on a device using a USB Ethernet adapter.
• Fixes an issue where Zscaler Client Connector prevented removing a device from isolation through the Microsoft Defender portal with Microsoft Intune.
• Fixes an issue where Zscaler Client Connector did not fall back to the redirect broker (any.broker) when switching from an Off Trusted Network to a Trusted Network.
• Fixes an issue where Zscaler Client Connector did not correctly close an existing Zscaler Private Access (ZPA) app session when in the ZPA forced reauthentication state.

• Fixes a driver error that occurred when upgrading Zscaler Client Connector for customers with anti-tampering already or previously enabled.
• Fixes an issue where Zscaler Client Connector prevented removing a device from isolation through the Microsoft Defender portal with Microsoft Intune.
• Fixes an issue where Zscaler Client Connector did not fall back to the redirect broker (any.broker) when switching from an Off Trusted Network to a Trusted Network.

Zscaler Client Connector version 4.6.0.123 has a known issue where users in a dual stack network or an IPv6-only network intermittently might be unable to access Zscaler Private Access (ZPA) applications after the device wakes up from sleep mode. Users can resolve the issue by clicking Restart Service on the More window. The issue will be corrected in an upcoming refresh release.

• Supports Business Continuity in Zscaler Private Access (ZPA) which ensures continued access to applications for users in events where the reachability or availability of the ZPA cloud is affected.
• Adds fail-open settings to the app profile that can override the global fail-open settings.
• Supports using a fail-close policy when Zscaler Client Connector is in Strict Enforcement mode and is in a fail-close state.
• Supports partner login settings on the app profile that can override the global ZPA Partner Logins settings (including entering specific partner domains that you can select on the app) and apply a device posture to partner tenants.
• Adds support for the collection of Health Metrics on devices to allow for diagnostics and proactively identify issues.
• Adds the ability to automatically resize the Zscaler Client Connector window during authentication to fit the IdP page.
• Adds the ability to display a custom notification to users who attempt to access the internet when in Strict Enforcement mode.
• Enhances the CrowdStrike ZTA posture by introducing two new device posture checks: CrowdStrike ZTA Device OS Score and CrowdStrike ZTA Sensor Setting Score.
• Adds the ability to create a custom banner with information about your organization and display it on the app.
• Adds enhancements to the stored configuration files used when reverting Zscaler Client Connector to a previous version.
• Supports the ability to notify end users of cloud DLP notifications on the endpoint if Endpoint Data Loss Prevention (DLP) notifications are enabled.
• Supports Egress IP as a condition for trusted network criteria.
• Adds enhancements to the Report an Issue form by supporting specific file types (image, document, and text files) and increasing the attachment size cap from 1 MB to 5 MB.
• Supports step-up authentication for conditional access to ZPA based on dynamic requests for stronger authentication for ZIdentity-enabled tenants.
• Updates the forwarding profile settings to drop IPv6 packets from IPv6-only networks, and renames the Drop IPv6 Packets option that drops IPv6 packets in dual stack networks.
• Improves Zscaler Tunnel (Z-Tunnel) 2.0 session handling and reconnection logic after the device wakes up from sleep mode.
• Supports the Dynamic ZIA Service Edge Assignment feature with ZIA Private Service Edges and ZIA Virtual Service Edges in addition to ZIA Public Service Edges.
• Updates third-party libraries for security fixes: upgrades the V8 engine used for the PAC parser to version 13.0, Npcap to version 1.80, and OpenSSL to version 1.0.2zk.
• Improves DNS request handling to reduce requests, including adding the ability to prioritize domain exclusions over IP inclusions when determining whether a DNS request should bypass Z-Tunnel 2.0.
• Supports forcing ZPA authentication to expire after a Windows user has been locked on a device for a specified number of minutes.
• Improves the startup sequence to reduce the time before Zscaler Client Connector begins traffic interception.
• Adds the ability to specify a registry key to locate the PAC URL on forwarding profiles using the Enforce and None modes.
• Supports using additional IdP domains if you use WebView2 authentication with an Imprivata integration and the user login domain is different from the IdP domain.
• Updates the Show all notifications toggle on the More window in the app to be Show notification pop-ups.
• Fixes an issue where Zscaler Client Connector failed to launch when the user skipped completion of Autopilot setup during Microsoft Autopilot deployment.
• Fixes an issue where Zscaler Client Connector pushed a proxy PAC file even though proxy settings were set to Never.
• Fixes an issue where users could not connect to a remote desktop protocol (RDP) related to the Windows domain network profile detection.
• Fixes an issue where Zscaler Client Connector intermittently did not follow IP-based Z-Tunnel 2.0 inclusion and exclusion rules.
• Fixes an issue where connections made while Zscaler Client Connector was in a fail-open state due to captive portal detection were still available even after the Zscaler Client Connector reenabled its services.
• Fixes an issue where a persistent pop-up notification lost focus when a new window was opened, resulting in new notifications not displaying.
• Fixes an issue where an update to the Show ZPA Reauthentication Notification in Every (In Minutes) value in the Zscaler Client Connector Portal did not immediately take effect after updating the policy manually in the app.
• Fixes a decryption issue with machine tunnels when Zscaler Client Connector was installed using Microsoft AutoPilot.
• Fixes an issue where ZPA did not reauthenticate automatically due to a WebView2 initialization issue resulting from resuming a Windows device from Modern Standby.
• Fixes an issue where Zscaler Client Connector did not bypass mobilesupport.zscaler.com when fetching logs from the Zscaler Client Connector Portal even though support access was not enabled for users.
• Fixes an issue where the internet usage policy page for a captive portal did not load properly after clicking Open Browser in Zscaler Client Connector.
• Fixes an issue where Zscaler Client Connector did not detect a Trusted Network when sending the DNS request through the default adapter.
• Fixes an issue where Zscaler Client Connector did not always clear the DNS suffixes when moving from a machine tunnel to a user tunnel.
• Fixes an issue where service status pop-up notifications indicating that Internet Security or Private Access is enabled or disabled displayed even though service status notifications were disabled.
• Fixes an issue where Zscaler Client Connector resolved a valid fully qualified domain name (FQDN) DNS search domain in a ZPA application segment as a non-existent domain (NXDOMAIN).
• Fixes an issue where Zscaler Client Connector did not recognize the Windows proxy settings during authentication.
• Fixes an issue where customers experienced DNS resolution errors on applications after Multimatch and App Scaling were enabled.
• Fixes an issue where users could not log in to Zscaler Client Connector if they were subscribed to a ZIdentity-enabled tenant and Posture Based App Profile was enabled but there were no device postures configured.
• Fixes an issue where Strict Enforcement was not enabled after installing Zscaler Client Connector for a ZIdentity-enabled tenant.
• Fixes an issue where the ZSATray process could block another application, such as PowerBuilder, from starting.
• Fixes an authentication issue in Zscaler Client Connector caused by a hardware fingerprint change after a reboot of the client machine.
• Fixes an issue where the Ethernet adapter was disabled after a device was rebooted or powered up if Zscaler Client Connector was configured to block domain profile detection.
• Fixes an issue where Zscaler Client Connector did not clear the Windows Firewall Protection filter after Trigger Domain Profile Detection was disabled.
• Fixes an issue where Zscaler Client Connector did not switch to a Split VPN Trusted Network after a VPN connection was established.
• Fixes an internal socket problem error that occurred with certain malformed UDP datagrams after starting applications such as Microsoft PowerPoint using the empower add-in.
• Fixes an issue where Zscaler Client Connector did not switch to the correct Network Type on a device using a USB Ethernet adapter.
• Fixes an issue where users with non-English OS devices were prompted to log in to Zscaler Client Connector after a device restart.
• Fixes an issue where Zscaler Client Connector connected to the default proxy port instead of the custom port specified in the PAC file.
• Fixes an issue where a Detect Antivirus device posture check did not pass, even though the antivirus specified in the antivirus name (AV Name) was running on the system.
• Fixes an issue where printing resulted in duplicate print jobs.
• Fixes an issue where Zscaler Client Connector did not fall back to the redirect broker (any.broker) when switching from an Off Trusted Network to a Trusted Network.
• Fixes an issue where Windows did not set the domain profile correctly after switching from a domain-joined network to a VPN Trusted Network when using a ZPA forwarding profile for VPN Trusted Network set to None.
• Fixes an issue where Zscaler Client Connector prevented removing a device from isolation through the Microsoft Defender portal with Microsoft Intune.
• Fixes a driver error that occurred when upgrading Zscaler Client Connector for customers with anti-tampering already or previously enabled.

Fixes an issue where Zscaler Client Connector used the default IP range for the machine tunnel even though the Zscaler Client Connector Synthetic IP Range was set.

• Fixes an issue where Zscaler Client Connector used the default IP range for the machine tunnel even though the Zscaler Client Connector Synthetic IP Range was set.
• Fixes an issue where Zscaler Client Connector did not switch to a Split VPN Trusted Network after a VPN connection was established.
• Fixes an issue where users with non-English OS devices were prompted to log in to Zscaler Client Connector after a device restart.

• Corrected errors in the translated text included with French localization.
• Fixes an issue where Zscaler Client Connector did not recognize the Windows proxy settings during authentication.
• Fixes an issue where Zscaler Client Connector used the default IP range for the machine tunnel even though the Zscaler Client Connector Synthetic IP Range was set.
• Fixes an issue where the Ethernet adapter was disabled after a device was rebooted or powered up if Zscaler Client Connector was configured to block domain profile detection.
• Fixes an issue where Zscaler Client Connector did not switch to a Split VPN Trusted Network after a VPN connection was established.
• Fixes an internal socket problem error that occurred with certain malformed UDP datagrams after starting applications such as Microsoft PowerPoint using the Empower add-in.
• Fixes an issue where users with non-English OS devices were prompted to log in to Zscaler Client Connector after a device restart.

• Fixes an issue where anti-tampering protection could be bypassed by tampering with a specific action performed by a trusted Windows process.
• Fixes an issue where Zscaler Client Connector did not load in a non-persistent VDI (virtual desktop infrastructure) where the user's roaming profile was mapped to an internal network share, causing network delays in certain file operations.
• Fixes an FW/AV error that could occur when using Microsoft eDiscovery.
• Fixes an issue where Zscaler Client Connector did not detect a Trusted Network when sending the DNS request through the default adapter.
• Fixes an issue where service status pop-up notifications indicating that Internet Security or Private Access is enabled or disabled displayed even though service status notifications were disabled.
• Fixes an internal error (302) that occurred if a Zscaler Private Access (ZPA) reauthentication session was interrupted by another reauthentication session initiated by the user through the Authenticate button from the system tray icon.
• Fixes an issue where customers experienced DNS resolution errors on applications after Multimatch and App Scaling were enabled.
• Fixes an issue where the ZSATunnel crashed and did not recover after switching from an Off Trusted Network to a VPN Trusted Network with a forwarding profile of None.
• Fixes a Machine Tunnel authentication error that occurred after the signing certificate expired for devices that were cloned with Zscaler Client Connector already installed.
• Fixes an issue where strict enforcement was not enabled after installing Zscaler Client Connector for a ZIdentity-enabled tenant.
• Fixes an issue where ZSATrayManager crashed after updating Zscaler Client Connector when there were a large number of environment variables.

• Fixes an issue where anti-tampering protection could be bypassed by tampering with a specific action performed by a trusted Windows process.
• Fixes an issue where Zscaler Client Connector did not load in a non-persistent VDI (virtual desktop infrastructure) where the user's roaming profile was mapped to an internal network share, causing network delays in certain file operations.
• Fixes an FW/AV error that could occur when using Microsoft eDiscovery.
• Fixes an issue where Zscaler Client Connector did not detect a Trusted Network when sending the DNS request through the default adapter.
• Fixes an issue where service status pop-up notifications indicating that Internet Security or Private Access is enabled or disabled displayed even though service status notifications were disabled.
• Fixes an internal error (302) that occurred if a Zscaler Private Access (ZPA) reauthentication session was interrupted by another reauthentication session initiated by the user through the Authenticate button from the system tray icon.
• Fixes an issue where customers experienced DNS resolution errors on applications after Multimatch and App Scaling were enabled.
• Fixes an issue where the ZSATunnel crashed and did not recover after switching from an Off Trusted Network to a VPN Trusted Network with a forwarding profile of None.
• Fixes a Machine Tunnel authentication error that occurred after the signing certificate expired for devices that were cloned with Zscaler Client Connector already installed.
• Fixes an issue where ZSATrayManager crashed after updating Zscaler Client Connector when there were a large number of environment variables.
• Fixes an issue where the posture-based app profile was not correctly applied after upgrading to Zscaler Client Connector version 4.4.0.368 for Windows.

• Fixes an issue where anti-tampering protection could be bypassed by tampering with a specific action performed by a trusted Windows process.
• Fixes an FW/AV error that could occur when using Microsoft eDiscovery.
• Fixes an issue where service status pop-up notifications indicating that Internet Security or Private Access is enabled or disabled displayed even though service status notifications were disabled.
• Fixes an issue where customers experienced DNS resolution errors on applications after Multimatch and App Scaling were enabled.
• Fixes a Machine Tunnel authentication error that occurred after the signing certificate expired for devices that were cloned with Zscaler Client Connector already installed.

• Fixes an issue where ZSATunnel did not exit when it aborted execution or crashed if you have Process-Based Application Bypass configured and enabled.
• Fixes a decryption issue with machine tunnels when Zscaler Client Connector was installed using AutoPilot.
• Fixes an internal server error that occurred when connecting to Zscaler Private Access (ZPA) if an IPv6 IP address was on the DNS priority list and you use the Route Based option for Tunnel Driver Type.
• Fixes an issue where ZPA did not reauthenticate automatically due to a WebView2 initialization issue resulting from resuming a Windows device from Modern Standby.
• Fixes an issue where the internet usage policy page for a captive portal did not load properly after clicking Open Browser in Zscaler Client Connector.
• Fixes high CPU usage by the Anti-Tampering feature (ZEP Service).
• Fixes an issue where a machine tunnel was not established after the initial Zscaler Client Connector deployment on a new device.
• Fixes an issue where Zscaler Client Connector did not display in the system tray after a system reboot.
• Fixes an issue where uploads from a client device to ZPA apps could fail when a client app server sent more than 64k bytes of data directly after a TCP handshake without a server acknowledgement.
• Fixes an issue where users could not log in to Zscaler Client Connector if they were subscribed to a ZIdentity-enabled tenant and Posture Based App Profile was enabled but there were no device postures configured.

• Fixes an issue where ZSATunnel did not exit when it aborted execution or crashed if you have Process-Based Application Bypass configured and enabled.
• Fixes a decryption issue with machine tunnels when Zscaler Client Connector was installed using AutoPilot.
• Fixes an internal server error that occurred when connecting to Zscaler Private Access (ZPA) if an IPv6 IP address was on the DNS priority list and you use the Route Based option for Tunnel Driver Type.
• Fixes an issue where ZPA did not reauthenticate automatically due to a WebView2 initialization issue resulting from resuming a Windows device from Modern Standby.
• Fixes an issue where the internet usage policy page for a captive portal did not load properly after clicking Open Browser in Zscaler Client Connector.
• Fixes high CPU usage by the Anti-Tampering feature (ZEP Service).
• Fixes an issue where a machine tunnel was not established after the initial Zscaler Client Connector deployment on a new device.
• Fixes an issue where Zscaler Client Connector did not display in the system tray after a system reboot.

• Fixes an issue where ZSATunnel did not exit when it aborted execution or crashed if you have Process-Based Application Bypass configured and enabled.
• Fixes an issue where a blank web page appeared during Zscaler Internet Access (ZIA) authentication or Zscaler Private Access (ZPA) reauthentication when using WebView2 web control.
• Fixes an internal server error that occurred when connecting to ZPA if an IPv6 IP address was on the DNS priority list and you use the Route Based option for Tunnel Driver Type.
• Fixes an issue where ZPA did not reauthenticate automatically due to a WebView2 initialization issue resulting from resuming a Windows device from Modern Standby.
• Fixes high CPU usage by the Anti-Tampering feature (ZEP Service).
• Fixes an issue where a machine tunnel was not established after the initial Zscaler Client Connector deployment on a new device.
• Fixes an issue where the Export Logs option did not display when the Report an issue option was enabled in the Troubleshoot section on the More window of Zscaler Client Connector.

Zscaler Client Connector version 4.5.0 for Windows has a known issue where uploads from a client device to Zscaler Private Access (ZPA) apps can fail when a client app server sends more than 64k bytes of data directly after a TCP handshake without a server acknowledgement. The issue has been corrected on Zscaler Client Connector version 4.5.0.325 for Windows. Prior to upgrading, you can temporarily resolve the issue by using an HTTPS server.

• Fixes an issue where a blank web page appeared during Zscaler Internet Access (ZIA) authentication or Zscaler Private Access (ZPA) reauthentication when using WebView2 web control.
• Fixes an issue where antivirus detection failed after upgrading to Zscaler Client Connector version 4.5.0.286 for Detect Antivirus posture types with a blank AV Name.

Fixes an issue where a blank web page appeared during Zscaler Internet Access (ZIA) authentication or Zscaler Private Access (ZPA) reauthentication when using WebView2 web control.

• Updates Zscaler Client Connector to ignore the "Run this program as an administrator" compatibility setting and always launch the system tray as the standard user.
• Fixes an issue where Zscaler Client Connector disconnected temporarily when deploying a larger number of Zscaler Private Access (ZPA) applications via an API.
• Fixes an issue where flow logs did not display the URL for a custom IP-based application bypass.
• Supports the Ignore Client Cert errors for WebView2 option that continues the authentication workflow if the embedded WebView2 in Zscaler Client Connector encounters client certificate errors. To learn more, see Using WebView2 Authentication.
• Fixes an issue where Zscaler Client Connector did not update the PAC file for the forwarding profile when the IP address remained the same even after a network type change.
• Fixes an issue where Zscaler Client Connector did not bypass mobilesupport.zscaler.com when fetching logs from the Zscaler Client Connector Portal even though support access was not enabled for users.
• Fixes an issue where the User Devices section of the Zscaler Digital Experience (ZDX) Admin Portal did not display the correct tunnel status for Zscaler Client Connector.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Updates Zscaler Client Connector to ignore the "Run this program as an administrator" compatibility setting and always launch the system tray as the standard user.
• Fixes an issue where the Wi-Fi adapter was disabled after rebooting when Zscaler Private Access (ZPA) was enabled and Block Domain Profile Detection was not enabled for any network types.
• Fixes an issue where Zscaler Client Connector disconnected temporarily when deploying a larger number of ZPA applications via an API.
• Fixes an issue where flow logs did not display the URL for a custom IP-based application bypass.
• Supports the Ignore Client Cert errors for WebView2 option that continues the authentication workflow if the embedded WebView2 in Zscaler Client Connector encounters client certificate errors. To learn more, see Using WebView2 Authentication.
• Fixes a false positive FW/AV Error detection.
• Fixes an issue where the initial DNS query timed out for a ZPA bypassed application when App Scaling was enabled.
• Fixes an issue where Zscaler Client Connector did not update the PAC file for the forwarding profile when the IP address remained the same even after a network type change.
• Fixes an issue where Zscaler Client Connector disappeared and did not reappear in the system tray until the system was rebooted.
• Fixes an issue where customers using a process-based application bypass could experience a Blue Screen error.
• Fixes an issue where Zscaler Client Connector did not bypass mobilesupport.zscaler.com when fetching logs from the Zscaler Client Connector Portal even though support access was not enabled for users.
• Fixes an issue where the User Devices section of the Zscaler Digital Experience (ZDX) Admin Portal did not display the correct tunnel status for Zscaler Client Connector.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where Zscaler Client Connector disconnected temporarily when deploying a larger number of Zscaler Private Access (ZPA) applications via an API.
• Fixes a false positive FW/AV Error detection.
• Fixes an issue where the initial DNS query timed out for a Zscaler Private Access (ZPA) bypassed application when App Scaling was enabled.
• Fixes an issue where Zscaler Client Connector did not update the PAC file for the forwarding profile when the IP address remained the same even after a network type change.
• Fixes an issue where Zscaler Client Connector did not bypass mobilesupport.zscaler.com when fetching logs from the Zscaler Client Connector Portal even though support access was not enabled for users.

• Fixes a false positive FW/AV Error detection.
• Fixes an issue where Zscaler Client Connector did not bypass mobilesupport.zscaler.com when fetching logs from the Zscaler Client Connector Portal even though support access was not enabled for users.

• Fixes an error where the ZSATrayManager process became stuck on the Windows Management Instrumentation (WMI) API invocation during reauthentication.
• Fixes an issue where Zscaler Client Connector was preventing the removal of a device from isolation through the Intune Microsoft Defender portal.
• Fixes high memory consumption on Zscaler Client Connector.
• Fixes an issue where users could not connect to an RDP related to the Windows domain network profile detection.
• Fixes an issue where the Wi-Fi adapter was disabled after rebooting when Zscaler Private Access (ZPA) was enabled and Block Domain Profile Detection was not enabled for any network types.
• Fixes an issue where Zscaler Client Connector users displayed in the Endpoint Settings in the Zscaler Deception Admin Portal even though Zscaler Deception was not enabled.
• Fixes an issue where excessive keepalive requests were received from devices with posture-based app profiles.
• Fixes an issue where Zscaler Client Connector did not evaluate trusted network criteria against a non-primary default adapter even though Evaluate Trusted NW against All Default Route Adapters was enabled.
• Fixes an issue where a "The Zscaler Client Connector is not running Tunnel" message displayed in User Devices in the Zscaler Digital Experience (ZDX) Admin Portal even though Zscaler Client Connector was connected to the tunnel.
• Fixes a false positive FW/AV Error detection.
• Fixes an issue where Zscaler Client Connector did not match the wildcard in partner login mode, although it matched without partner login.
• Fixes an issue where the initial DNS query timed out for a ZPA bypassed application when App Scaling was enabled.
• Fixes an issue where Zscaler Client Connector disappeared and did not reappear in the system tray until the system was rebooted.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where users ran into connection delays in some scenarios when a device woke up from sleep.
• Fixes an issue where Zscaler Client Connector was preventing the removal of a device from isolation through the Intune Microsoft Defender portal.
• Fixes high memory consumption on Zscaler Client Connector.
• Fixes an issue where Zscaler Client Connector pushed a proxy PAC file even though proxy settings were set to Never.
• Fixes an issue where users could not connect to a remote Windows desktop (RDP) related to the Windows domain network profile detection.
• Fixes an issue where Zscaler Client Connector users displayed in the Endpoint Settings in the Zscaler Deception Admin Portal even though Zscaler Deception was not enabled.
• Fixes an issue where excessive keepalive requests were received from devices with posture-based app profiles.
• Fixes an issue where Zscaler Client Connector did not evaluate trusted network criteria against a non-primary default adapter even though Evaluate Trusted NW against All Default Route Adapters was enabled.
• Fixes an issue where the Zscaler Internet Access (ZIA) disaster recovery hostname DNS query failed when VPN was enabled.
• Fixes an issue where a "The Zscaler Client Connector is not running Tunnel" message displayed in the User Devices section of the Zscaler Digital Experience (ZDX) Admin Portal even though Zscaler Client Connector was connected to the tunnel.
• Fixes an issue where Zscaler Client Connector did not match the wildcard in partner login mode, although it matched without partner login.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an error where the ZSATrayManager process became stuck on the Windows Management Instrumentation (WMI) API invocation during reauthentication.
• Fixes an issue where Zscaler Client Connector was preventing the removal of a device from isolation through the Intune Microsoft Defender portal.
• Fixes high memory consumption on Zscaler Client Connector.
• Fixes an issue where Zscaler Client Connector pushed a proxy PAC file even though proxy settings were set to Never.
• Fixes an issue where Zscaler Client Connector users displayed in the Endpoint Settings in the Zscaler Deception Admin Portal even though Zscaler Deception was not enabled.
• Fixes an issue where Zscaler Private Access (ZPA) remained in a Connecting state when the WMI service was paused.
• Fixes an issue where excessive keepalive requests were received from devices with posture-based app profiles.
• Fixes an issue where the Zscaler Internet Access (ZIA) disaster recovery hostname DNS query failed when VPN was enabled.
• Fixes an issue where Zscaler Client Connector did not match the wildcard in partner login mode, although it matched without partner login.

• Fixes an issue where Zscaler Client Connector pushed a proxy PAC file even though proxy settings were set to Never.
• Fixes an issue where Zscaler Client Connector users displayed in the Endpoint Settings in the Zscaler Deception Admin Portal even though Zscaler Deception was not enabled.
• Fixes an issue where excessive keepalive requests were received from devices with posture-based app profiles.
• Fixes an issue where Zscaler Client Connector did not match the wildcard in partner login mode, although it matched without partner login.

• Supports ZIdentity integration for the following features: Strict Enforcement mode, Endpoint Data Loss Prevention (DLP), machine tunnel authentication, support for device groups and service entitlement, dynamic service enrollment, and using ZIdentity to authenticate device tokens created in Zscaler Client Connector. To learn more, see What Is ZIdentity?
• Supports Zscaler Digital Experience (ZDX) database security with encryption to sensitive data.
• Updates the DNS TXT record query in Disaster Recovery Mode to send the query to all DNS servers.
• Updates Zscaler Client Connector to disable traffic forwarding when users start Windows in safe mode.
• Adds support to use a PROXY return statement in the PAC file used with Zscaler Internet Access (ZIA) Disaster Recovery Configuration so that internet traffic is sent to a proxy server. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Updates Zscaler Client Connector to allow traffic to the loopback proxy for app containers that are added while the app is running if Disable Loopback Restriction is enabled.
• Supports clearing the list of Kerberos domain controllers in the cache when Zscaler Client Connector connects to and disconnects from Zscaler Private Access (ZPA). To learn more, see Configuring Zscaler Client Connector App Profiles.
• Adds support to automatically start packet captures when Zscaler Client Connector detects a captive portal. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Improves the installation and uninstallation processes for anti-tampering, including adding an option to enable anti-tampering using an MSI installer. To learn more, see Customizing Zscaler Client Connector with Install Options for MSI.
• Supports using the Enable Anti-tampering setting from the app profile regardless of how the anti-tampering option was originally set during installation. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Updates Zscaler Client Connector to require users to reauthenticate ZPA if they log in to Windows with fast startup enabled. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Updates the process used with Firefox integration. Firefox integration no longer supports Mozilla Developer Preview or Firefox downloaded from the Microsoft Store.
• Adds support for captive portal detection that moves captive portal settings from the global settings on the Client Connector Support page to the app profile and adds additional configuration settings, including using an embedded browser when users authenticate to a captive portal. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Acknowledges Zscaler’s use of third-party software and adds a link to view the third-party software notice in the About section of the More window in Zscaler Client Connector. To learn more, see Viewing Information About Zscaler Client Connector.

• Adds localization support to change the language of the app user interface based on the system language. Zscaler Client Connector version 4.5 and later for Windows supports changing the English language to French and vice versa.

  If you use Zscaler Diagnostics, users must copy the Current user settings to the Welcome screen settings in Windows to display the Zscaler Diagnostics user interface in the system language.

• Supports ZDX improvements to remote Packet Capture (PCAP) functionality to incorporate Lightweight Filter (LWF) capture capability.
• Updates the Detect Carbon Black, Detect CrowdStrike, and Detect SentinelOne device posture types so that the posture check passes if the security product is installed and turned on in Windows Security Center even if a matching thumbprint is not detected. To learn more, see Configuring Device Posture Profiles.
• Allows Zscaler Client Connector to block all inbound traffic for various network types with an option to exclude one or more ports. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Supports forcing a location sync between the SCCM client and the management point after connecting to or disconnecting from ZPA. To learn more, see Configuring Zscaler Client Connector App Profiles.
• Fixes an issue where Zscaler Client Connector displayed an Authentication Error for a device that was removed in the Zscaler Client Connector Portal in a No Default Route (NDR) environment with Tunnel Internal Traffic enabled. If the user clicked Retry, Zscaler Client Connector returned a -13 error.
• Adds an option to have WebView 2.0 not follow the system proxy and instead connect directly to the internet. To learn more, see Enabling WebView 2.0 Authentication.
• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version on Windows 10 Long-Term Servicing Branch (LTSB) devices.
• Fixes an issue where users ran into connection delays in some scenarios when a device woke up from sleep.
• Fixes an issue where Zscaler Client Connector incorrectly reported traffic as bypassed when it had been blocked by the Windows firewall in some scenarios.
• Fixes an issue where Zscaler Client Connector failed to launch when the user skipped completion of Autopilot setup during Microsoft Autopilot deployment.
• Fixes an issue where the Zscaler Client Connector Portal displayed the wrong service status if the user was connected to ZPA as a partner tenant.
• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version in some scenarios.
• Fixes an issue where Zscaler Client Connector continued to use the service edge IP address from the previous PAC file after the PAC file was updated in the app profile in the None forwarding mode.
• Fixes an issue where users were required to reauthenticate to ZPA multiple times per day if Zscaler Client Connector incorrectly detected a network adapter change.
• Updates third-party libraries for security fixes: upgrades the V8 engine used for the PAC parser (to version 12.5), Npcap (to version 1.79), NewtonSoft Json Parser (to version 13.0.3), and fixes ZSFFUtil and Mozilla libraries.
• Resolves an issue where Zscaler Client Connector displayed "Partner Already Exists with the same domain" when attempting to log in to a partner tenant after upgrading the app.
• Fixes an issue with ZSATray High CPU usage when the device posture check was set to Detect Windows Defender.
• Fixes an issue where Zscaler Client Connector did not apply the system PAC file after a network type change due to a Remote Procedure Call (RPC) failure.
• Fixes an issue where the ZPA reauthentication failed intermittently during a network change.
• Fixes an issue where a ZPA IP-based application was bypassed in some scenarios when an entry in the VPN gateway bypass section was not resolvable.
• Fixes an issue where Zscaler Client Connector dropped an initial DNS request via TCP in some scenarios.
• Fixes connectivity issues between Zscaler Active Defense (ZAD) service and the Zscaler Deception Admin Portal.
• Fixes an issue where users could not access a private application after force reauthentication was triggered when the timeout policy was set to Never.
• Fixes an issue where a change to a Device Posture profile in the Zscaler Client Connector Portal was not sent to the ZPA Service Edge.
• Fixes an issue where VPN gateway bypass domains were not accessible after upgrading Zscaler Client Connector.
• Fixes an issue where Zscaler Client Connector disconnected intermittently when a large number of smaller chunk downloads were happening simultaneously.
• Fixes an issue where the Zscaler Client Connector login page displayed although the HIDEAPPUIONLAUNCH command line parameter was enabled.
• Fixes an issue where the Windows Explorer and other application windows were refreshed and repainted while Zscaler Client Connector updated the system proxy configuration.
• Fixes an issue where Zscaler Client Connector could not connect to an application using a non-web port when traffic forwarding was set to use Zscaler Tunnel (Z-Tunnel) 1.0 and the Route-based driver type.
• Resolves an issue where domain profile detection was not correctly blocked when the Block Domain Profile Detection feature was enabled while using the Machine Tunnel feature.
• Fixes an issue where Zscaler Client Connector did not bypass all ZPA applications set up for domain- and IP-based application bypass when using App Scaling.
• Fixes an issue where ZPA remained in a Connecting state for over an hour due to an issue with the Disaster Recovery file.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where Zscaler Private Access (ZPA) remained in a Connecting state for over an hour due to an issue with the Disaster Recovery file.
• Fixes an issue where Zscaler Client Connector switched from Zscaler Tunnel (Z-Tunnel) 2.0 to Z-Tunnel 1.0 when connecting to the VPN after an upgrade.
• Fixes an issue where users could not access a private application after force reauthentication was triggered when the timeout policy was set to Never.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where Zscaler Private Access (ZPA) remained in a Connecting state for over an hour due to an issue with the Disaster Recovery file.
• Fixes an issue where Zscaler Client Connector fell back to Zscaler Tunnel (Z-Tunnel) 1.0 after the user upgraded to Zscaler Client Connector version 4.3.0.x and later.
• Fixes an issue where users could not access a private application after force reauthentication was triggered when the timeout policy was set to Never.
• Fixes an issue where Zscaler Client Connector was stuck in a Connecting state in some scenarios.
• Fixes an issue where the Zscaler Client Connector login page displayed although the HIDEAPPUIONLAUNCH command line parameter was enabled.
• Fixes an issue where the ZSATunnel process did not stop in a timely manner during upgrades and other scenarios.
• Fixes an issue where Zscaler Client Connector remained in a Connecting state for a few minutes after the user's computer goes into sleep or hibernation.
• Fixes an issue where users ran into connection delays in some scenarios when a device woke up from sleep.
  

• Fixes an issue where Zscaler Client Connector fell back to Zscaler Tunnel (Z-Tunnel) 1.0 after the user upgraded to Zscaler Client Connector version 4.3.0.x and later.
• Fixes an issue where the Zscaler Client Connector login page displayed although the HIDEAPPUIONLAUNCH command line parameter was enabled.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where Zscaler Client Connector failed to launch when the user skipped completion of Autopilot setup during Microsoft Autopilot deployment.
• Resolves an issue where Zscaler Client Connector displayed "Partner Already Exists with the same domain" when attempting to log in to a partner tenant after upgrading the app.
• Fixes an issue where VPN gateway bypass domains were not accessible after upgrading Zscaler Client Connector.
• Fixes an issue where Zscaler Client Connector disconnected intermittently when a large number of smaller chunk downloads were happening simultaneously.
• Fixes an issue where users were not auto-enrolled in Zscaler Client Connector after a network switch.
• Resolves an issue where domain profile detection was not correctly blocked when the Block Domain Profile Detection feature was enabled while using the Machine Tunnel feature.
• Fixes an issue where users faced intermittent connectivity issues to the ZPA service during network change events.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version on Windows 10 LTSB devices.
• Fixes an issue where Zscaler Client Connector incorrectly reported traffic as bypassed when it had been blocked by the Windows firewall in some scenarios.
• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version in some scenarios.
• Fixes an issue where the Firewall device posture check passed even though Windows Defender Firewall was disabled.
• Fixes an issue where the Firewall device posture check failed even though the firewall was enabled on the user device.
• Fixes an issue where a Zscaler Private Access (ZPA) IP-based application was bypassed in some scenarios when an entry in the VPN gateway bypass section was not resolvable.
• Fixes connectivity issues between the Zscaler Active Defense (ZAD) and the Zscaler Deception Admin Portal.
• Fixes an issue where users could not access a private application after force reauthentication was triggered when the timeout policy was set to Never.
• Fixes an issue where VPN gateway bypass domains were not accessible after upgrading Zscaler Client Connector to version 4.3.0.190.
• Fixes an issue where Zscaler Client Connector disconnected intermittently when a large number of smaller chunk downloads were happening simultaneously.
• Fixes an issue where users were not auto-enrolled in Zscaler Client Connector after a network switch.
• Fixes an issue where Zscaler Client Connector could not connect to an application using a non-web port when traffic forwarding was set to use Zscaler Tunnel (Z-Tunnel) 1.0 and the Route-based driver type.

• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version on Windows 10 LTSB devices.
• Fixes an issue where the Firewall device posture check passed even though Windows Defender Firewall was disabled.
• Fixes an issue where the Firewall device posture check failed even though the firewall was enabled on the user device.
• Fixes an issue where a Zscaler Private Access (ZPA) IP-based application was bypassed in some scenarios when an entry in the VPN gateway bypass section was not resolvable.
• Adds support for downloading the default PAC file using HTTPS.
• Fixes connectivity issues between the Zscaler Active Defense (ZAD) and the Zscaler Deception Admin Portal.
• Fixes an issue where users could not access a private application after force reauthentication was triggered when the timeout policy was set to Never.
• Fixes an issue where VPN gateway bypass domains were not accessible after upgrading Zscaler Client Connector.
• Fixes an issue where users were not auto-enrolled in Zscaler Client Connector after a network switch.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version on Windows 10 LTSB devices.
• Fixes an issue where Zscaler Client Connector incorrectly reported traffic as bypassed when it had been blocked by the Windows firewall in some scenarios.
• Fixes an issue where Zscaler Client Connector did not upgrade correctly to a higher version in some scenarios.
• Fixes an issue where the Firewall device posture check passed even though Windows Defender Firewall was disabled.
• Fixes an issue with ZSATray High CPU usage when the device posture check was set to Detect Windows Defender.
• Fixes an issue where the Firewall device posture check failed even though the firewall was enabled on the user device.
• Fixes an issue where a Zscaler Private Access (ZPA) IP-based application was bypassed in some scenarios when an entry in the VPN gateway bypass section was not resolvable.
• Fixes connectivity issues between the Zscaler Active Defense (ZAD) and the Zscaler Deception Admin Portal.
• Fixes an issue where users could not access a private application after force reauthentication was triggered when the timeout policy was set to Never.
• Fixes an issue where Zscaler Client Connector did not connect to the correct ZIA Public Service Edge after a trusted network switch in some scenarios.
• Fixes an issue where Zscaler Client Connector could not connect to an application using a non-web port when traffic forwarding was set to use Zscaler Tunnel (Z-Tunnel) 1.0 and the Route-based driver type.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where the Detect Antivirus posture check failed intermittently in some scenarios.
• Fixes an issue where users faced intermittent connectivity issues to Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA) services.
• Fixes an issue where Zscaler Client Connector did not switch to a different user when the user logged in on Imprivata.
• Fixes an issue where Firefox and Safari did not enforce the default proxy configuration in TWLP mode.
• Fixes an issue where the PAC file was not set after returning to the trusted network after switching from a trusted network to a captive portal.
• Fixes an issue where the ZPA reauthentication timed out if the system went to sleep during the reauthentication process.
• Fixes a problem where help.zscaler.com traffic did not route through the ZIA tunnel in some scenarios.
• Fixes an issue where users could not connect to the internet because Zscaler Client Connector remained in a Connecting state.
• Fixes an issue where the ZPA reauthentication failed intermittently during a network change.
• Fixes an issue where Zscaler Client Connector did not validate the certificate correctly for a downloaded PAC file (CVSS 6.4).
• Fixes an issue where Zscaler Client Connector dropped an initial DNS request via TCP in some scenarios.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where the username field did not display when logging in to Zscaler Client Connector when the system locale was set to Japanese.
• Fixes an issue where Zscaler Client Connector entered a loop trying to connect to a Zscaler Private Access (ZPA) IP address after detecting a captive portal.
• Fixes an issue where Zscaler Client Connector continued to use the service edge IP address from the previous PAC file after the PAC file was updated in the app profile in the None forwarding mode.
• Fixes an issue where users faced intermittent connectivity issues to Zscaler Internet Access (ZIA) and ZPA services.
• Fixes an issue where the posture-based app profile was not correctly applied in a specific case.
• Fixes an issue where Firefox and Safari did not enforce the default proxy configuration in TWLP mode.
• Fixes an issue where the PAC file was not set after returning to the trusted network after switching from a trusted network to a captive portal.
• Fixes an issue where the ZPA reauthentication timed out if the system went to sleep during the reauthentication process.
• Fixes a problem where help.zscaler.com traffic did not route through the ZIA tunnel in some scenarios.
• Fixes an issue where users could not connect to the internet because Zscaler Client Connector remained in a Connecting state.
• Fixes an issue where Zscaler Client Connector remained in a Connecting state after system hibernation or tunnel restart.
• Fixes an issue where the ZPA reauthentication failed intermittently during a network change.
• Fixes an issue where Zscaler Client Connector did not validate the certificate correctly for a downloaded PAC file (CVSS 6.4).

• Fixes an issue where the username field did not display when logging in to Zscaler Client Connector when the system locale was set to Japanese.
• Fixes an issue where users could not enter the @ symbol in the Password field of Zscaler Client Connector during user login if using a non-English keyboard layout.
• Fixes an issue where Zscaler Client Connector entered a loop trying to connect to a Zscaler Private Access (ZPA) IP address after detecting a captive portal.
• Fixes an issue where Zscaler Client Connector continued to use the service edge IP address from the previous PAC file after the PAC file was updated in the app profile in the None forwarding mode.
• Fixes an issue where Zscaler Client Connector refreshed all VPN hostname bypasses even though no network change was detected.
• Fixes an internal error that occurred when connecting to a partner tenant while ZPA was disabled on a VPN trusted network.
• Fixes an issue where the ZPA reauthentication timed out if the system went to sleep during the reauthentication process.
• Fixes an issue where the ZPA reauthentication failed intermittently during a network change.
• Fixes an issue where Zscaler Client Connector did not validate the certificate correctly for a downloaded PAC file (CVSS 6.4).

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes an issue where users were unable to authenticate with Zscaler Client Connector when browser-based authentication was set up and the application was installed with strict enforcement.
• Fixes an issue with the V8-based PAC parser that caused the ZSATunnel process to encounter an error condition.
• Fixes an issue where Zscaler Client Connector failed to stop the previous version of the tunnel service during an upgrade, causing the upgrade process to fail for certain users.
• Fixes an issue where Zscaler Client Connector did not load the captive portal page even though captive portal detection was enabled.
• Fixes an issue where Zscaler Client Connector users experienced a connection error in Zscaler Private Access (ZPA) when an alternative cloud was activated.
• Fixes an issue where Zscaler Client Connector did not connect via a captive portal if the IP address overlapped with a ZPA application segment.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Fixes a UI issue where the PIN dialog for smart card authentication hid behind the Zscaler tray in some scenarios.
• Fixes an issue where Zscaler Client Connector consumed a high amount of resources when it was running for a prolonged period.
• Fixes an issue where the PAC file was not set after returning to a trusted network from a captive portal.
• Fixes an issue where the Zscaler Client Connector Portal displayed the wrong service status if the user was connected to Zscaler Private Access (ZPA) as a partner tenant.
• Adds the ability to use the EXE file with a CLI option to disable anti-tampering after it has been enabled.
• Fixes an issue where Zscaler Client Connector failed to connect to the private broker in a non-default route environment.
• Fixes an issue where Zscaler Client Connector continued to use the service edge IP address from the previous PAC file after the PAC file was updated in the app profile when the forwarding mode was also set to "None."
• Fixes an issue where Zscaler Client Connector didn't fall back to WebBrowser Control if there was a failure to start WebView 2.0.
• Fixes an issue where Zscaler Client Connector refreshed all VPN hostname bypasses even though no network change was detected.
• Fixes an issue with the V8-based PAC parser that caused the ZSATunnel process to encounter an error condition.
• Fixes an issue where some configuration files (including machine tunnel configurations) were not retained and strict enforcement was not reapplied after reverting Zscaler Client Connector to a previous version.
• Fixes an internal error that occurred when connecting to a partner tenant while ZPA was disabled on a VPN trusted network.
• Fixes an issue where Zscaler Client Connector entered a loop when running the Export Logs process for a large file.
• Fixes an issue where the posture-based app profile was not correctly applied in a specific case.
• Fixes an issue where Zscaler Client Connector failed to stop the previous version of the tunnel service during an upgrade, resulting in the upgrade failing for some users.
• Fixes an issue where Zscaler Client Connector did not load the captive portal page even though captive portal detection was enabled.
• Fixes a network error that occurred when Zscaler Client Connector tried to connect to Zscaler Internet Access (ZIA) if ZIA was configured to block domain fronting.

• Fixes an issue where Zscaler Client Connector consumed a high amount of resources when it was running for a prolonged period.
• Fixes an error where traffic could bypass the tunnel after a Zscaler Private Access (ZPA) connection error in some scenarios.
• Fixes an issue where the Zscaler Client Connector Portal displayed the wrong service status if the user was connected to ZPA as a partner tenant.
• Adds the ability to use the EXE file with a CLI option to disable anti-tampering after it has been enabled.
• Fixes an issue where Zscaler Client Connector failed to connect to the private broker in a non-default route environment.
• Fixes an issue where Zscaler Client Connector refreshed all VPN hostname bypasses even though no network change was detected.
• Fixes an issue where some configuration files (including machine tunnel configurations) were not retained and strict enforcement was not reapplied after reverting Zscaler Client Connector to a previous version.
• Fixes an internal error that occurred when connecting to a partner tenant while ZPA was disabled on a VPN trusted network.

• Fixes an issue where Zscaler Client Connector consumed a high amount of resources when it was running for a prolonged period.
• Fixes an error where traffic could bypass the tunnel after a Zscaler Private Access (ZPA) connection error in some scenarios.
• Fixes an issue where the Zscaler Client Connector Portal displayed the wrong service status if the user was connected to ZPA as a partner tenant.
• Adds the ability to use the EXE file with a CLI option to disable anti-tampering after it has been enabled.

This version of Zscaler Client Connector has a known issue with some embedded web pages appearing blank if you use WebView2. To learn more, see Zscaler Client Connector Displays Blank Page.

• Supports flow logging for partner tenants using Zscaler Private Access (ZPA) when the main tenant uses only Zscaler Internet Access (ZIA).
• Updates notification message text to indicate when the message applies to a partner tenant.
• Adds support to retain an active partner tunnel connection after a Zscaler Client Connector policy update for the main tenant.
• Adds Machine Tunnel support for the following device postures: File Path, Registry Key, Firewall, Full Disk Encryption, Domain Joined, and OS Version. To learn more, see Configuring Device Posture Profiles.
• Supports the AzureAD Domain Joined posture type for devices that are joined to an Azure AD domain.
• Adds support for latency-based server configuration for ZPA. To learn more, see Configuring Forwarding Profiles for Zscaler Client Connector.
• Adds support for DNS TXT records for ZPA domains.
• Adds enhancements to the packet capture functionality in Zscaler Client Connector.
• Adds a configuration in the Zscaler Client Connector Portal that restricts remote packet capture for administrators only.
• Adds the Server Certificate posture type that validates the client certificate against the cloud rather than only checking locally for managed devices.
• Adds the following trusted network conditions in the Zscaler Client Connector Portal: Network Range, Default Gateway IP Addresses, and DHCP Server.
• Supports Installing Windows Firewall Inbound Rule in the app profiles.
• Provides enhancements to the Repair App feature.
• Updates Npcap to version 1.78.
• Supports seamless integration with Imprivata to differentiate individual users sessions on shared clinical workstations.
• Adds support for login_hint SAML attributes to improve the Pre-populate the Zscaler Client Connector Username feature.
• Adds alternate cloud name support for both ZIA and ZPA.
• Adds enhancements to the Zscaler Cloud Performance Test tool.
• Supports an option to remove existing exempted containers in the app profiles.
• Adds a reauthenticate button to Zscaler Client Connector on the taskbar icon menu for authenticating ZPA in advance.
• Allows Zscaler Client Connector to block domain profile detection for various network types.
• Replaces HTTP-based probing with ICMP-based probing for improved performance.
• Provides Command Line Interface Access on Zscaler Client Connector and allows admins to interact with Zscaler Client Connector via CLI. To learn more, see Interacting with Zscaler Client Connector Remotely.
• Updates the V8 engine used for the PAC parser to version 11.9.
• Adds real-time posture checks for the following posture types: Process Check, Detect Carbon Black, Detect CrowdStrike, Detect SentinelOne, and Detect Microsoft Defender.
• Includes support for the Zscaler Digital Experience (ZDX) Self Service feature that suggests steps to resolve potential device issues without the need to contact customer support. To learn more, see Self Service Notifications in Zscaler Client Connector.
• Zscaler Client Connector supports the integration of the ZIdentity platform that allows you to use single sign-on (SSO) for the portals of all Zscaler services in the ZIdentity Admin Portal. To learn more, see Accessing and Navigating the Zscaler Client Connector Portal.
• Supports traffic forwarding to ZPA through the ZIA Inspected ZPA Apps forwarding rule.
• Adds functionality to defer the enrollment process when deploying Zscaler Client Connector using Microsoft Autopilot so that the Autopilot setup can complete before users are prompted to authenticate. Users must allow the setup to complete for the Zscaler Client Connector system tray to launch correctly.
• Supports the ability to prompt users to renew their ZPA certificate a specific number of days before the certificate expires.
• Updates Zscaler Client Connector to detect external proxies for all proxy action types to support application monitoring by ZDX.
• Supports enabling SSO for WebView 2.0 customers.
• Fixes a ZDX issue where customers using the ZSAUPM process encountered an error state.
• Fixes an issue where Zscaler Client Connector couldn’t parse larger DNS TXT records. At this time, Zscaler Client Connector doesn’t support DNS TXT query responses that are larger than 16,384 bytes.
• Fixes frequent disconnections on Zscaler Client Connector when using the routing-based app profile with ZPA on a domain-joined Windows machine.
• Fixes a delay in loading bypassed sites when the connection is reset by the server.
• Updates Zscaler Client Connector to refresh the proxy list and retry any failed proxies after a network change instead of waiting for the next standard PAC file download (every 15 minutes).
• Enhances security in the machine tunnel using Zscaler Diagnostics.
• Fixes an issue where Zscaler Client Connector generated too many DNS queries when detecting captive portals for customers using a No Default Route environment.
• Removes functionality that automatically excludes "F5 Networks VPN Adapter" when evaluating VPN trusted networks.
• Fixes an issue where the tunnel processes repeatedly encountered an error condition, causing ZPA to disconnect and reconnect.
• Fixes an error that could occur when ZPA/ZIA authentication was forwarded through an external proxy.
• Fixes an issue where some Zscaler Private Access (ZPA) apps were not accessible after upgrading to Zscaler Client Connector version 4.2.0.209 if users had IPv6 enabled on their devices but IPv6 did not have internet access.
• Fixes an issue where Zscaler Client Connector connected temporarily to a different ZIA Public Service Edge than the closest one after a network type change.
• Fixes an issue where Zscaler Client Connector entered a loop trying to connect to a ZPA IP address after detecting a captive portal.
• Updates the Certificate Revocation List (CRL) check for the Client Certificate device posture type to add a retrial mechanism in case of failure scenarios.
• Fixes an error where the ZSATray manager process became stuck on the Windows WMI API invocation during reauthentication.
• Fixes an issue where Zscaler Client Connector did not prompt for reauthentication after a system restart even though Force ZPA Authentication To Expire was set to On System Restart in the app profile.
• Fixes an issue where Zscaler Client Connector did not correctly detect a captive portal until users restarted the service if the captive portal shared an IP address with a ZPA app.
• Fixes a delay in Zscaler Client Connector connection after a system reboot when a large number of destination exclusions were configured.
• Fixes an issue where Zscaler Client Connector did not detect a captive portal even after getting a 307 response code.
• Fixes an internal error that occurred when users tried to reauthenticate ZPA after upgrading Zscaler Client Connector.
• Fixes an issue where the ZSATunnel.exe file encountered an error that caused Zscaler Client Connector to crash.
• Fixes an issue where Zscaler Client Connector bypassed some DNS requests for ZPA domains that are also public domains.
• Fixes an error where traffic could bypass the tunnel after a ZPA connection error in some scenarios.

• Fixes an issue with the hardware ID for ARM devices.

  After upgrading to this release, users with an ARM device must re-register ZPA in Zscaler Client Connector.

Updates the Certificate Revocation List (CRL) check for the Client Certificate device posture type to add a retrial mechanism in case of failure scenarios.

• Fixes an issue where some Zscaler Private Access (ZPA) apps were not accessible after upgrading to Zscaler Client Connector version 4.2.0.209 if users had IPv6 enabled on their devices but IPv6 did not have internet access.
• Fixes an issue where Zscaler Client Connector connected temporarily to a different ZIA Public Service Edge than the closest one after a network type change.
• Fixes a delay in opening files with Japanese characters in the file name for customers using anti-tampering protection.
• Updates the Certificate Revocation List (CRL) check for the Client Certificate device posture type to add a retrial mechanism in case of failure scenarios.
• Fixes an issue where Zscaler Client Connector did not prompt for reauthentication after a system restart even though Force ZPA Authentication To Expire was set to On System Restart in the app profile.
• Fixes an issue where Zscaler Client Connector did not correctly detect a captive portal until users restarted the service if the captive portal shared an IP address with a ZPA app.
• Fixes an issue where Zscaler Client Connector did not detect a captive portal even after getting a 307 response code.
• Fixes an internal error that occurred when users tried to reauthenticate ZPA after upgrading Zscaler Client Connector.
• Fixes an issue where the ZSATunnel.exe file encountered an error that caused Zscaler Client Connector to crash.

• Fixes an issue where some Zscaler Private Access (ZPA) apps were not accessible after upgrading to Zscaler Client Connector version 4.2.0.209 if users had IPv6 enabled on their devices but IPv6 did not have internet access.
• Fixes an issue where Zscaler Client Connector connected temporarily to a different ZIA Public Service Edge than the closest one after a network type change.
• Fixes an issue where Zscaler Client Connector did not prompt for reauthentication after a system restart even though Force ZPA Authentication To Expire was set to On System Restart in the app profile.
• Fixes an issue where Zscaler Client Connector did not correctly detect a captive portal until users restarted the service if the captive portal shared an IP address with a ZPA app.
• Fixes an issue where Zscaler Client Connector did not detect a captive portal even after getting a 307 response code.
• Fixes an internal error that occurred when users tried to reauthenticate ZPA after upgrading Zscaler Client Connector.
• Fixes an issue where the ZSATunnel.exe file encountered an error that caused Zscaler Client Connector to crash.

Fixes an issue with anti-tampering where users encountered network disconnections in some specific scenarios after upgrading to Zscaler Client Connector version 4.3.0.151 for Windows.

Fixes an issue with anti-tampering where users encountered network disconnections in some specific scenarios after upgrading to Zscaler Client Connector version 4.2.1 for Windows.