Client Connector
Client Connector App Release Summary (2025)
This article provides a summary of all new features and enhancements released per operating system (OS) for the Zscaler Client Connector app. To successfully update to the latest version of Zscaler Client Connector, see Best Practices for Updating Latest Versions of Zscaler Client Connector Application.
The Client Connector app versions for Windows listed below were deployed on the following dates.
March 07, 2025
- Release Available: Client Connector 4.6.0.168 for Windows
Zscaler Client Connector 4.6.0.168 Enhancements and Fixes
- Fixes an issue where the ZSATunnel process could crash and sometimes create dump files in the export logs after a fragmented packet was received.
- Fixes an issue where some apps couldn't connect to the internet if Zscaler Client Connector was installed using strict enforcement and Remove Existing Exempted Containers was enabled.
- Fixes an issue where Zscaler Client Connector displayed an
Internal Errormessage during device startup due to the Network Driver Interface Specification (NDIS) not binding the Zscaler Client Connector Windows Filter Driver to the network adapter. - Fixes an issue where users with Zscaler Private Access (ZPA) and either Zscaler Digital Experience (ZDX) or Zscaler Active Defense (ZAD) could receive an
Internal Error, Please Contact Admin [10112]message and be unable to log in to Zscaler Client Connector. - Fixes an issue where a ZIdentity user could not log in to Zscaler Client Connector if their login name included a special character (e.g., # or @).
- Fixes an issue where Zscaler Client Connector could be uninstalled in unattended mode without an Uninstall Password when anti-tampering was enabled.
- Fixes an issue where the ZPA reauthentication required notification didn’t display as a pop-up or in the Notifications window for enrolled users after Automatically Attempt ZPA Reauthentication was disabled.
- Fixes an issue where ZDX probes sent via Zscaler Tunnel (Z-Tunnel) 1.0 were not forwarded to the specific proxy address configured in the app profile.
- Fixes an issue that prevented Zscaler Client Connector from establishing a Zscaler Internet Access (ZIA) Z-Tunnel 2.0 connection when the ZIA Service Edge was configured as a ZPA application.
- Fixes an issue where an echo test request was sent to ZPA from a device on a dual-stack network if the synthetic IP range was beyond the 100.64.0.0/16 default range.
- Fixes an issue where the Microsoft System Center Configuration Manager (SCCM) ClientAlwaysOnInternet registry key was not updated based on the SCCM Client configuration after switching from a Trusted network to an Off-Trusted network or vice versa.
- Fixes an issue where the connection from Zscaler Client Connector to the ZPA Public Service Edge was not closed correctly, which could result in a slow response from the server.
- Fixes an issue where an
Internal Errormessage displayed when authenticating ZPA if ZPA was enabled after the user logged in to Zscaler Client Connector. - Fixes an issue where tunnel crashes were observed from pacparser failures due to a Windows API failing to fetch the proxy PAC file after Zscaler Client Connector was connected using ZPA, ZDX, and ZIA with a forwarding profile of None.
- Fixes an issue where ZPA reauthentication could fail after upgrading Zscaler Client Connector from a much earlier version (e.g., Zscaler Client Connector version 3.7).
March 06, 2025
- Release Available: Client Connector 4.5.0.381 for Windows
Zscaler Client Connector 4.5.0.381 Enhancements and Fixes
- Updates Npcap to version 1.80.
- Fixes an issue with anti-tampering that could cause a driver error when upgrading Zscaler Client Connector.
- Fixes an issue where the ZSATunnel process could crash and sometimes create dump files in the export logs after a fragmented packet was received.
- Fixes an issue where some apps couldn't connect to the internet if Zscaler Client Connector was installed using strict enforcement and Remove Existing Exempted Containers was enabled.
- Fixes an issue where Zscaler Client Connector displayed an
Internal Errormessage during device startup due to the Network Driver Interface Specification (NDIS) not binding the Zscaler Client Connector Windows Filter Driver to the network adapter. - Fixes an issue where Zscaler Client Connector did not register with Zscaler Private Access (ZPA) client-to-client capability and could not be connected to via RDP over ZPA.
- Fixes an issue where a ZIdentity user could not log in to Zscaler Client Connector if their login name included a special character (e.g., # or @).
- Fixes an issue where Zscaler Client Connector could be uninstalled in unattended mode without an Uninstall Password when anti-tampering was enabled.
- Fixes an issue where Zscaler Client Connector displayed a
Server Downerror after connecting to the default gateway if the primary and secondary proxy addresses in the PAC file were unavailable when using Tunnel with Local Proxy. - Fixes an issue where the ZPA reauthentication required notification didn’t display as a pop-up or in the Notifications window for enrolled users after Automatically Attempt ZPA Reauthentication was disabled.
- Fixes an issue where Zscaler Digital Experience (ZDX) probes sent via Zscaler Tunnel (Z-Tunnel) 1.0 were not forwarded to the specific proxy address configured in the app profile.
- Fixes an issue that prevented Zscaler Client Connector from establishing a Zscaler Internet Access (ZIA) Z-Tunnel 2.0 connection when the ZIA Service Edge was configured as a ZPA application.
- Fixes an issue where an echo test request was sent to ZPA from a device on a dual-stack network if the synthetic IP range was beyond the 100.64.0.0/16 default range.
- Fixes an issue where the Microsoft System Center Configuration Manager (SCCM) ClientAlwaysOnInternet registry key was not updated based on the SCCM Client configuration after switching from a Trusted network to an Off-Trusted network or vice versa.
- Fixes an issue where the connection from Zscaler Client Connector to the ZPA Public Service Edge was not closed correctly, which could result in a slow response from the server.
- Fixes an issue where tunnel crashes were observed from pacparser failures due to a Windows API failing to fetch the proxy PAC file after Zscaler Client Connector was connected using ZPA, ZDX, and ZIA with a forwarding profile of None.
- Fixes an issue where ZPA reauthentication could fail after upgrading Zscaler Client Connector from a much earlier version (e.g., Zscaler Client Connector version 3.7).
March 05, 2025
- Release Available: Client Connector 4.4.0.406 for Windows
Zscaler Client Connector 4.4.0.406 Enhancements and Fixes
- Updates Npcap to version 1.80.
- Fixes an issue with anti-tampering that could cause a driver error when upgrading Zscaler Client Connector.
- Fixes an issue where the ZSATunnel process could crash and sometimes create dump files in the export logs after a fragmented packet was received.
- Fixes an issue where some apps couldn't connect to the internet if Zscaler Client Connector was installed using strict enforcement and Remove Existing Exempted Containers was enabled.
- Fixes an issue where Zscaler Client Connector did not register with Zscaler Private Access (ZPA) client-to-client capability and could not be connected to via RDP over ZPA.
- Fixes an issue where Zscaler Client Connector could be uninstalled in unattended mode without an Uninstall Password when anti-tampering was enabled.
- Fixes an issue where the ZPA reauthentication required notification didn’t display as a pop-up or in the Notifications window for enrolled users after Automatically Attempt ZPA Reauthentication was disabled.
- Fixes an issue where Zscaler Digital Experience (ZDX) probes sent via Zscaler Tunnel (Z-Tunnel) 1.0 were not forwarded to the specific proxy address configured in the app profile.
- Fixes an issue that prevented Zscaler Client Connector from establishing a Zscaler Internet Access (ZIA) Z-Tunnel 2.0 connection when the ZIA Service Edge was configured as a ZPA application.
- Fixes an issue where an echo test request was sent to ZPA from a device on a dual-stack network if the synthetic IP range was beyond the 100.64.0.0/16 default range.
March 04, 2025
- Release Available: Client Connector 4.3.0.277 for Windows
Zscaler Client Connector 4.3.0.277 Enhancements and Fixes
- Fixes an issue with anti-tampering that could cause a driver error when upgrading Zscaler Client Connector.
- Fixes an issue where the ZSATunnel process could crash.
- Fixes an issue where Zscaler Client Connector could be uninstalled in unattended mode without an Uninstall Password when anti-tampering was enabled.
- Fixes an issue where the Zscaler Private Access (ZPA) reauthentication required notification didn’t display as a pop-up or in the Notifications window for enrolled users after Automatically Attempt ZPA Reauthentication was disabled.
- Fixes an issue that prevented Zscaler Client Connector from establishing a Zscaler Internet Access (ZIA) Z-Tunnel 2.0 connection when the ZIA Service Edge was configured as a ZPA application.
February 07, 2025
- Release in Limited Availability: Client Connector 4.6.0.146 for Windows
Zscaler Client Connector 4.6.0.146 Enhancements and Fixes
- Fixes an issue where the Firewall device posture check could fail even though the firewall was enabled on the user device.
- Limits the total size of all Zscaler log files for all Windows user profiles to 500 MB on a machine with Zscaler Client Connector integrated with Imprivata by deleting the oldest files when the maximum is reached.
- Fixes an issue with anti-tampering that could cause a driver error when upgrading Zscaler Client Connector.
- Fixes an issue where packet capture failed to start but a notification displayed that packet capture was started and quickly finished.
- Fixes an issue where ZSAHelper log files were created frequently for forwarding profiles with the Route-Based tunnel driver type and Enable Split VPN Trusted Network disabled.
- Fixes an issue where Zscaler Client Connector did not prevent the Windows Defender firewall domain profile from being applied to the device even though the device network type (e.g., Off Trusted Network) was selected in Block Domain Profile Detection.
- Fixes an issue where the Zscaler Client Connector tray icon disappeared after logging in due to receiving two authentication responses via browser-based authentication.
- Fixes an issue where the Service Status on the Private Access window continued to display as
Connectingafter a change in network type, even though the traffic was forwarded correctly to the Zscaler service. - 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 the incorrect forwarding action (tunnel or bypass) could be applied because the network detection process wasn't re-run after reconnecting to a network that was interrupted initially.
- Fixes an issue where Zscaler Client Connector removed loopback exemptions even though the Remove Existing Exempted Containers feature was disabled.
- Fixes an issue where users on a dual stack network or an IPv6-only network intermittently were unable to access ZPA applications after the device woke up from sleep mode.
- Fixes an issue where user traffic bypassed the Zscaler cloud (e.g., users could access restricted websites) for a short interval of time while the Zscaler Tunnel (Z-Tunnel) 2.0 was connecting due to a network type switch.
- Fixes an issue where a partner tenant did not reconnect after a machine reboot.
- Fixes an issue where the Private Access tab did not automatically display for a user who was assigned service entitlement to ZPA in ZIdentity after upgrading Zscaler Client Connector.
- Fixes an issue where Zscaler Client Connector took a long time to connect after rebooting because of a trusted network evaluation delay with IPv6 DNS servers using a forwarding profile with Drop IPv6 Packets enabled.
- Fixes an issue where DNS traffic in Domain Inclusion was not forwarded because Zscaler Client Connector's internal DNS proxy state was stuck in an initialized state after network disconnect and reconnect events.
- Fixes an issue where Zscaler Client Connector did not register with ZPA client-to-client capability and could not be connected via RDP over ZPA.
- Fixes an issue where Zscaler Client Connector continually displayed
Registering Deviceafter a ZIdentity user reauthenticated even though the device was successfully registered.
January 24, 2025
- Release Available: Client Connector 4.5.0.366 for Windows
Zscaler Client Connector 4.5.0.366 Enhancements and Fixes
- Fixes an issue where Zscaler Client Connector intermittently did not follow IP-based Zscaler Tunnel (Z-Tunnel) 2.0 inclusion and exclusion rules.
- Limits the total size of all Zscaler log files for all Windows user profiles to 500 MB on a machine with Zscaler Client Connector integrated with Imprivata by deleting the oldest files when the maximum is reached.
- Fixes an issue where packet capture failed to start but a notification displayed that packet capture was started and quickly finished.
- Fixes an issue where ZSAHelper log files were created frequently for forwarding profiles with the Route-Based tunnel driver type and Enable Split VPN Trusted Network disabled.
- Fixes an issue where Zscaler Client Connector did not prevent the Windows Defender firewall domain profile from being applied to the device even though the device network type (e.g., Off Trusted Network) was selected in Block Domain Profile Detection.
- Fixes an issue where the Zscaler Client Connector tray icon disappeared after logging in due to receiving two authentication responses via browser-based authentication.
- Fixes an issue where the Service Status on the Private Access window continued to display as
Connectingafter a change in network type, even though the traffic was forwarded correctly to the Zscaler service. - Fixes an issue where the incorrect forwarding action (tunnel or bypass) could be applied because the network detection process wasn't re-run after reconnecting to a network that was interrupted initially.
- Fixes an issue where Zscaler Client Connector removed loopback exemptions even though the Remove Existing Exempted Containers feature was disabled.
- Fixes an issue where user traffic bypassed the Zscaler cloud (e.g., users could access restricted websites) for a short interval of time while the Z-Tunnel 2.0 was connecting due to a network type switch.
- Fixes an issue where a partner tenant did not reconnect after a machine reboot.
- Fixes an issue where the Private Access tab did not automatically display for a user who was assigned service entitlement to Zscaler Private Access (ZPA) in ZIdentity after upgrading Zscaler Client Connector.
- Fixes an issue where Zscaler Client Connector took a long time to connect after rebooting because of a trusted network evaluation delay with IPv6 DNS servers using a forwarding profile with Drop IPv6 Packets enabled.
- Fixes an issue where DNS traffic in Domain Inclusion was not forwarded because Zscaler Client Connector's internal DNS proxy state was stuck in an initialized state after network disconnect and reconnect events.
- Fixes an issue where Zscaler Client Connector continually displayed Registering Device after a ZIdentity user reauthenticated even though the device was successfully registered.
January 23, 2025
- Release Available: Client Connector 4.4.0.395 for Windows
Zscaler Client Connector 4.4.0.395 Enhancements and Fixes
- Fixes an issue where Zscaler Client Connector intermittently did not follow IP-based Zscaler Tunnel (Z-Tunnel) 2.0 inclusion and exclusion rules.
- Limits the total size of all Zscaler log files for all Windows user profiles to 500 MB on a machine with Zscaler Client Connector integrated with Imprivata by deleting the oldest files when the maximum is reached.
- Fixes an issue where packet capture failed to start but a notification displayed that packet capture was started and quickly finished.
- Fixes an issue where ZSAHelper log files were created frequently for forwarding profiles with the Route-Based tunnel driver type and Enable Split VPN Trusted Network disabled.
- Fixes an issue where the Zscaler Client Connector tray icon disappeared after logging in due to receiving two authentication responses via browser-based authentication.
- Fixes an issue where a partner tenant did not reconnect after a machine reboot.
- Fixes an issue where Zscaler Client Connector took a long time to connect after rebooting because of a trusted network evaluation delay with IPv6 DNS servers using a forwarding profile with Drop IPv6 Packets enabled.
January 21, 2025
- Release Available: Client Connector 4.3.0.272 for Windows
Zscaler Client Connector 4.3.0.272 Enhancements and Fixes
- Fixes an issue where Zscaler Client Connector intermittently did not follow IP-based Zscaler Tunnel (Z-Tunnel) 2.0 inclusion and exclusion rules.
- Fixes an issue where ZSAHelper log files were created frequently for forwarding profiles with the Route-Based tunnel driver type and Enable Split VPN Trusted Network disabled.
- Fixes an issue where the Zscaler Client Connector tray icon disappeared after logging in due to receiving two authentication responses via browser-based authentication.