July 03; 2025$$$Zscaler Client Connector 4.5.0.471 Enhancements and Fixes$$$Updates Zscaler Client Connector to retrieve the system PAC file settings and pass them to WebView2 for authentication during enrollment to ensure that the correct proxy setting is used.$$$Fixes an issue where users still received an Authentication required on Lock screen message to onboard the machine tunnel even after the ZPA Machine Authentication option was disabled in the policy.$$$Fixes an issue where Zscaler Client Connector did not allow remote access via NinjaOne if the app profile included a process-based application bypass.$$$Fixes an issue where Zscaler Private Access (ZPA) incoming traffic processing could be delayed when the Send Location Hint to Client Connector feature was enabled.$$$Fixes an issue where Zscaler Client Connector sent incorrect logs to the server for flow logging when multiple connections were opened on the same local port.$$$Fixes an issue where users could not log in to Zscaler Client Connector again after their device was soft-removed if the Automatically Attempt ZPA Reauthentication option was enabled.

June 30; 2025$$$Zscaler Client Connector 4.4.0.456 Enhancements and Fixes$$$Updates Zscaler Client Connector to retrieve the system PAC file settings and pass them to WebView2 for authentication during enrollment to ensure that the correct proxy setting is used.$$$Fixes an issue where users still received an Authentication required on Lock screen message to onboard the machine tunnel even after the ZPA Machine Authentication option was disabled in the policy.$$$Fixes an issue where the machine tunnel didnt start after upgrading Zscaler Client Connector.$$$Fixes an issue where a users device couldnt connect to the domain controller through the machine tunnel before the user logged in if Strict Enforcement mode and App Scaling were enabled.$$$Fixes an issue where Zscaler Private Access (ZPA) applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes an issue where Zscaler Client Connector sent incorrect logs to the server for flow logging when multiple connections were opened on the same local port.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes an issue where users could not log in to Zscaler Client Connector again after their device was soft-removed if the Automatically Attempt ZPA Reauthentication option was enabled.

June 27; 2025$$$Zscaler Client Connector 4.6.0.240 Enhancements and Fixes$$$Updates Zscaler Client Connector to retrieve the system PAC file settings and pass them to WebView2 for authentication during enrollment to ensure that the correct proxy setting is used.$$$Fixes an issue where users still received an Authentication required on Lock screen message to onboard the machine tunnel even after the ZPA Machine Authentication option was disabled in the policy.$$$Fixes an issue where Zscaler Client Connector did not allow remote access via NinjaOne if the app profile included a process-based application bypass.$$$Fixes an exception handling issue that caused Zscaler Client Connector to not run in a virtual desktop infrastructure (VDI) when the Zscaler Client Connector processes did not have access permission to the users roaming application data directory.$$$Fixes an issue where a users device couldnt connect to the domain controller through the machine tunnel before the user logged in if Strict Enforcement mode and App Scaling were enabled.$$$Fixes an issue where Zscaler Private Access (ZPA) incoming traffic processing could be delayed when the Send Location Hint to Client Connector feature was enabled.$$$Fixes an issue where Zscaler Client Connector sent incorrect logs to the server for flow logging when multiple connections were opened on the same local port.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes an issue where Zscaler Client Connector did not connect to a domain set to bypass Zscaler Tunnel (Z-Tunnel) 2.0 in the forwarding profile if the proxy to which the app profile PAC file sent all non-Z-Tunnel 2.0 traffic was unavailable; even though the app profile included another specific proxy for the domain.$$$Fixes an issue where users could not access a URL bypassed by the app profile PAC file if the URL was also in the Zscaler Internet Access (ZIA) disaster recovery global database allowlist and the ZIA Cloud Not Reachable app fail-open setting was configured to fallback to ZIA DR; even though ZIA was not in disaster recovery mode.$$$Fixes an issue where Zscaler Client Connector could repeatedly enter a Registration required state for ZPA if it was deployed in Strict Enforcement mode.$$$Fixes an issue where Zscaler Client Connector did not update the correct device trust level to the ZIA Public Service Edge during initial enrollment if the tunnel was in a connecting state and took longer to transition to a connected state.$$$Fixes an issue where users could not log in to Zscaler Client Connector again after their device was soft-removed if the Automatically Attempt ZPA Reauthentication option was enabled.$$$Fixes an issue where Zscaler Client Connector did not send DNS requests to the DNS server for the VPN Service Edge; even though the Network Connector was connected.$$$Fixes an issue where Zscaler Client Connector did not reconnect to the VPN Service Edge after a ZPA reconnection using VPN (for Legacy Apps).$$$Fixes an issue where users on an IPv6-only network experienced ZPA disconnections if Hyper-V was enabled on their device.

June 27; 2025$$$Zscaler Client Connector 4.6.0.240 Enhancements and Fixes$$$Updates Zscaler Client Connector to retrieve the system PAC file settings and pass them to WebView2 for authentication during enrollment to ensure that the correct proxy setting is used.$$$Fixes an issue where users still received an Authentication required on Lock screen message to onboard the machine tunnel even after the ZPA Machine Authentication option was disabled in the policy.$$$Fixes an issue where Zscaler Client Connector did not allow remote access via NinjaOne if the app profile included a process-based application bypass.$$$Fixes an exception handling issue that caused Zscaler Client Connector to not run in a virtual desktop infrastructure (VDI) when the Zscaler Client Connector processes did not have access permission to the users roaming application data directory.$$$Fixes an issue where a users device couldnt connect to the domain controller through the machine tunnel before the user logged in if Strict Enforcement mode and App Scaling were enabled.$$$Fixes an issue where Zscaler Private Access (ZPA) incoming traffic processing could be delayed when the Send Location Hint to Client Connector feature was enabled.$$$Fixes an issue where Zscaler Client Connector sent incorrect logs to the server for flow logging when multiple connections were opened on the same local port.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes an issue where Zscaler Client Connector did not connect to a domain set to bypass Zscaler Tunnel (Z-Tunnel) 2.0 in the forwarding profile if the proxy to which the app profile PAC file sent all non-Z-Tunnel 2.0 traffic was unavailable; even though the app profile included another specific proxy for the domain.$$$Fixes an issue where users could not access a URL bypassed by the app profile PAC file if the URL was also in the Zscaler Internet Access (ZIA) disaster recovery global database allowlist and the ZIA Cloud Not Reachable app fail-open setting was configured to fallback to ZIA DR; even though ZIA was not in disaster recovery mode.$$$Fixes an issue where Zscaler Client Connector could repeatedly enter a Registration required state for ZPA if it was deployed in Strict Enforcement mode.$$$Fixes an issue where Zscaler Client Connector did not update the correct device trust level to the ZIA Public Service Edge during initial enrollment if the tunnel was in a connecting state and took longer to transition to a connected state.$$$Fixes an issue where users could not log in to Zscaler Client Connector again after their device was soft-removed if the Automatically Attempt ZPA Reauthentication option was enabled.$$$Fixes an issue where Zscaler Client Connector did not send DNS requests to the DNS server for the VPN Service Edge; even though the Network Connector was connected.$$$Fixes an issue where Zscaler Client Connector did not reconnect to the VPN Service Edge after a ZPA reconnection using VPN (for Legacy Apps).$$$Fixes an issue where users on an IPv6-only network experienced ZPA disconnections if Hyper-V was enabled on their device.

July 07; 2025$$$Zscaler Client Connector 4.7.0.61 Enhancements and Fixes$$$Updates Zscaler Client Connector to retrieve the system PAC file settings and pass them to WebView2 for authentication during enrollment to ensure that the correct proxy setting is used.$$$Fixes an issue where users still received an Authentication required on Lock screen message to onboard the machine tunnel even after the ZPA Machine Authentication option was disabled in the policy.$$$Fixes an issue where Zscaler Client Connector did not allow remote access via NinjaOne if the app profile included a process-based application bypass.$$$Fixes an exception handling issue that caused Zscaler Client Connector to not run in a virtual desktop infrastructure (VDI) when the Zscaler Client Connector processes did not have access permission to the users roaming application data directory.$$$Fixes an issue where a users device couldnt connect to the domain controller through the machine tunnel before the user logged in if Strict Enforcement mode and App Scaling were enabled.$$$Fixes an issue where Zscaler Private Access (ZPA) incoming traffic processing could be delayed when the Send Location Hint to Client Connector feature was enabled.$$$Fixes an issue where Zscaler Client Connector sent incorrect logs to the server for flow logging when multiple connections were opened on the same local port.$$$Fixes an issue where Zscaler Client Connector did not connect to a domain set to bypass Zscaler Tunnel (Z-Tunnel) 2.0 in the forwarding profile if the proxy to which the app profile PAC file sent all non-Z-Tunnel 2.0 traffic was unavailable; even though the app profile included another specific proxy for the domain.$$$Fixes an issue where users could not access a URL bypassed by the app profile PAC file if the URL was also in the Zscaler Internet Access (ZIA) disaster recovery global database allowlist and the ZIA Cloud Not Reachable app fail-open setting was configured to fallback to ZIA DR; even though ZIA was not in disaster recovery mode.$$$Fixes an issue where Zscaler Client Connector could repeatedly enter a Registration required state for ZPA if it was deployed in Strict Enforcement mode.$$$Fixes an issue where Zscaler Client Connector did not update the correct device trust level to the ZIA Public Service Edge during initial enrollment if the tunnel was in a connecting state and took longer to transition to a connected state.$$$Fixes an issue where users could not log in to Zscaler Client Connector again after their device was soft-removed if the Automatically Attempt ZPA Reauthentication option was enabled.$$$Fixes an issue where Zscaler Client Connector did not send DNS requests to the DNS server for the VPN Service Edge; even though the Network Connector was connected.$$$Fixes an issue where Zscaler Client Connector did not reconnect to the VPN Service Edge after a ZPA reconnection using VPN (for Legacy Apps).$$$Fixes an issue where users on an IPv6-only network experienced ZPA disconnections if Hyper-V was enabled on their device.

June 04; 2025$$$Zscaler Client Connector 4.7.0.47 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes performance issues due to logging; particularly for ICMP request packets.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where Zscaler Client Connector authentication could fail with an internal error when a manually configured external proxy was not correctly identified on the system.$$$Fixes an issue where Zscaler Client Connector entered Business Continuity mode in a no-default route environment; even though the cloud was available.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes an issue where Zscaler Client Connector sent traffic from devices via the built-in cellular adapter instead of the Wi-Fi network; which caused connectivity issues for IPv6-only Wi-Fi networks.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes traffic forwarding issues that could occur while accessing ZPA and Zscaler Internet Access (ZIA) apps due to Zscaler Client Connector indefinitely retaining the source port-based bypass used during proxy health checks.$$$Fixes an issue where Zscaler Client Connector didnt end the connection to the ZPA Private Service Edge and exit Business Continuity; even though the Zero Trust Exchange (ZTE) was reachable.$$$Fixes an issue where external proxy detection failed due to third-party process interference; preventing the system from correctly determining proxy settings from the PAC file.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP Microtunnel (M-Tunnel) requests.

June 04; 2025$$$Zscaler Client Connector 4.5.0.459 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue with Zscaler Digital Experience (ZDX) probes that occurred after Zscaler Tunnel (Z-Tunnel) 1.0 failures; even though the Z-Tunnel 2.0 connection was healthy and both the Use Tunnel 2.0 for Proxied Traffic option and the Redirect Web Traffic to Local Proxy option were enabled.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where the machine tunnel didn’t start after upgrading Zscaler Client Connector.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where a users device couldnt connect to the domain controller through the machine tunnel before the user logged in if Strict Enforcement mode and App Scaling were enabled.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP M-Tunnel requests.

June 04; 2025$$$Zscaler Client Connector 4.7.0.47 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes performance issues due to logging; particularly for ICMP request packets.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where Zscaler Client Connector authentication could fail with an internal error when a manually configured external proxy was not correctly identified on the system.$$$Fixes an issue where Zscaler Client Connector entered Business Continuity mode in a no-default route environment; even though the cloud was available.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes an issue where Zscaler Client Connector sent traffic from devices via the built-in cellular adapter instead of the Wi-Fi network; which caused connectivity issues for IPv6-only Wi-Fi networks.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes traffic forwarding issues that could occur while accessing ZPA and Zscaler Internet Access (ZIA) apps due to Zscaler Client Connector indefinitely retaining the source port-based bypass used during proxy health checks.$$$Fixes an issue where Zscaler Client Connector didnt end the connection to the ZPA Private Service Edge and exit Business Continuity; even though the Zero Trust Exchange (ZTE) was reachable.$$$Fixes an issue where external proxy detection failed due to third-party process interference; preventing the system from correctly determining proxy settings from the PAC file.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP Microtunnel (M-Tunnel) requests.

June 04; 2025$$$Zscaler Client Connector 4.5.0.459 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue with Zscaler Digital Experience (ZDX) probes that occurred after Zscaler Tunnel (Z-Tunnel) 1.0 failures; even though the Z-Tunnel 2.0 connection was healthy and both the Use Tunnel 2.0 for Proxied Traffic option and the Redirect Web Traffic to Local Proxy option were enabled.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where the machine tunnel didn’t start after upgrading Zscaler Client Connector.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where a users device couldnt connect to the domain controller through the machine tunnel before the user logged in if Strict Enforcement mode and App Scaling were enabled.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes an issue where Zscaler Client Connector experienced a connection error when a cellular device was placed in isolation through the Intune Microsoft Defender portal; and the device could not be removed from isolation through the portal.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP M-Tunnel requests.

May 28; 2025$$$Zscaler Client Connector 4.6.0.216 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where Zscaler Client Connector sent traffic from devices via the built-in cellular adapter instead of the Wi-Fi network; which caused connectivity issues for IPv6-only Wi-Fi networks.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes performance issues due to logging; particularly for ICMP request packets.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where Zscaler Client Connector authentication could fail with an internal error when a manually-configured external proxy was not correctly identified on the system.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes traffic forwarding issues that could occur while accessing ZPA and Zscaler Internet Access (ZIA) apps due to Zscaler Client Connector indefinitely retaining the source port-based bypass used during proxy health checks.$$$Fixes an issue where Zscaler Client Connector didnt end the connection to the ZPA Private Service Edge and exit Business Continuity; even though the Zero Trust Exchange (ZTE) was reachable.$$$Fixes an issue where external proxy detection failed due to a third-party process interference; preventing the system from correctly determining proxy settings from the PAC file.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP M-Tunnel requests.

May 28; 2025$$$Zscaler Client Connector 4.6.0.216 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where Zscaler Client Connector sent traffic from devices via the built-in cellular adapter instead of the Wi-Fi network; which caused connectivity issues for IPv6-only Wi-Fi networks.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes performance issues due to logging; particularly for ICMP request packets.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where Zscaler Client Connector authentication could fail with an internal error when a manually-configured external proxy was not correctly identified on the system.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes traffic forwarding issues that could occur while accessing ZPA and Zscaler Internet Access (ZIA) apps due to Zscaler Client Connector indefinitely retaining the source port-based bypass used during proxy health checks.$$$Fixes an issue where Zscaler Client Connector didnt end the connection to the ZPA Private Service Edge and exit Business Continuity; even though the Zero Trust Exchange (ZTE) was reachable.$$$Fixes an issue where external proxy detection failed due to a third-party process interference; preventing the system from correctly determining proxy settings from the PAC file.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP M-Tunnel requests.

May 28; 2025$$$Zscaler Client Connector 4.6.0.216 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where Zscaler Client Connector sent traffic from devices via the built-in cellular adapter instead of the Wi-Fi network; which caused connectivity issues for IPv6-only Wi-Fi networks.$$$Fixes an issue where a Detect Antivirus device posture check passed for an outdated AV signature; even though the Check if AV definitions are up to date option was enabled.$$$Fixes an issue where Zscaler Client Connector did not clear added DNS search domains from Zscaler Private Access (ZPA) after moving from a machine tunnel to a user tunnel.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes an issue where a blank screen displayed when authenticating using the embedded browser to access a ZPA application and the Automatically Attempt ZPA Reauthentication feature was enabled.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes performance issues due to logging; particularly for ICMP request packets.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.$$$Fixes an issue where Zscaler Client Connector authentication could fail with an internal error when a manually-configured external proxy was not correctly identified on the system.$$$Fixes an issue where ZPA applications could not be accessed after a user who was already connected to Zscaler Client Connector clicked Update Policy on Zscaler Diagnostics.$$$Fixes traffic forwarding issues that could occur while accessing ZPA and Zscaler Internet Access (ZIA) apps due to Zscaler Client Connector indefinitely retaining the source port-based bypass used during proxy health checks.$$$Fixes an issue where Zscaler Client Connector didnt end the connection to the ZPA Private Service Edge and exit Business Continuity; even though the Zero Trust Exchange (ZTE) was reachable.$$$Fixes an issue where external proxy detection failed due to a third-party process interference; preventing the system from correctly determining proxy settings from the PAC file.$$$Fixes disconnections to the ZPA service caused by parallel ICMP and TCP M-Tunnel requests.

May 16; 2025$$$Zscaler Client Connector 4.4.0.432 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where Zscaler Client Connector could not access an IP-based Zscaler Private Access (ZPA) application due to LWF filters created based on an incomplete application list.$$$Fixes an issue where WFP filters were not deleted correctly after a tunnel crash; resulting in an FW/AV error when trying to reconnect.$$$Fixes an issue with Zscaler Digital Experience (ZDX) probes that occurred after Zscaler Tunnel (Z-Tunnel) 1.0 failures; even though the Z-Tunnel 2.0 connection was healthy and both the Use Tunnel 2.0 for Proxied Traffic option and the Redirect Web Traffic to Local Proxy option were enabled.$$$Fixes an issue where Zscaler Client Connector did not download the PAC file after switching to a Split VPN-Trusted network with Zscaler Internet Access (ZIA) enabled; which could cause unexpected traffic handling.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes issues where the ZSATunnel service could crash when restarting due to conflicts in background processes.$$$Fixes an issue where Zscaler Client Connector stopped working after users clicked Revert App if they had previously opened the app from the tray icon during an upgrade.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes an issue where Zscaler Client Connector didnt connect to the ZPA Service Edge after switching from a machine tunnel to a user tunnel; causing some users to experience authentication errors.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.

May 16; 2025$$$Zscaler Client Connector 4.4.0.432 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector started the enrollment process in the background before the Autopilot setup was complete when deploying Zscaler Client Connector using Microsoft Autopilot.$$$Fixes an issue where Zscaler Client Connector could not access an IP-based Zscaler Private Access (ZPA) application due to LWF filters created based on an incomplete application list.$$$Fixes an issue where WFP filters were not deleted correctly after a tunnel crash; resulting in an FW/AV error when trying to reconnect.$$$Fixes an issue with Zscaler Digital Experience (ZDX) probes that occurred after Zscaler Tunnel (Z-Tunnel) 1.0 failures; even though the Z-Tunnel 2.0 connection was healthy and both the Use Tunnel 2.0 for Proxied Traffic option and the Redirect Web Traffic to Local Proxy option were enabled.$$$Fixes an issue where Zscaler Client Connector did not download the PAC file after switching to a Split VPN-Trusted network with Zscaler Internet Access (ZIA) enabled; which could cause unexpected traffic handling.$$$Fixes an issue where crash events were observed in the logs after shutdown of a device with machine tunnels enabled.$$$Fixes issues where the ZSATunnel service could crash when restarting due to conflicts in background processes.$$$Fixes an issue where Zscaler Client Connector stopped working after users clicked Revert App if they had previously opened the app from the tray icon during an upgrade.$$$Fixes an issue where Zscaler Client Connector did not open a Microtunnel (M-Tunnel) for an ICMP request for a ZPA application that came in during the Cooldown period (the one-second period after receiving 100 requests with less than a one-second gap between them).$$$Fixes an issue where Zscaler Client Connector didnt connect to the ZPA Service Edge after switching from a machine tunnel to a user tunnel; causing some users to experience authentication errors.$$$Fixes a machine tunnel authentication failure that occurred due to Zscaler Client Connector not handling the config file correctly if an error was encountered after a system proxy change.

April 24; 2025$$$Zscaler Client Connector 4.6.0.200 Enhancements and Fixes$$$Fixes a delay in detecting the captive portal when Zscaler Client Connector encountered network issues while establishing a connection.$$$Fixes an issue where Zscaler Client Connector displayed incorrect connectivity information in the app after a users device switched from an off-trusted network to a VPN network.$$$Fixes an issue where the Zscaler Internet Access (ZIA) trust level was incorrectly calculated using device posture results from the cache after a reboot.$$$Fixes an issue for ZIdentity users where the number in the Zscaler Client Connector Version field displayed incorrectly on the Device Management page and in the Registered Device Details window of the Zscaler Client Connector Portal.$$$Fixes an issue where ZIdentity users were unable to complete the ZPA reauthentication process.$$$Fixes an issue where Windows could display a blue screen for some users when flow logging was enabled.$$$Fixes an issue where Zscaler Client Connector could not access an IP-based Zscaler Private Access (ZPA) application due to LWF filters created based on an incomplete application list.$$$Fixes an issue where uploads to a network drive were slow when using the Server Message Block (SMB) protocol using ZPA.$$$Fixes an issue with tunnel disconnects caused by pacparser crashes due to running out of memory.$$$Fixes an issue where a ZPA application sometimes could not be accessed due to Zscaler Client Connector not removing a previous entry for a proxied connection to use for the direct bypass connection.$$$Updates Zscaler Client Connector to ignore blank serial numbers when generating UDIDs; preventing multiple devices for a single user from having the same UDID.$$$Fixes an issue where Zscaler Client Connector remained on the Loading page when reauthenticating ZPA due to a posture evaluation delay.$$$Fixes an internal error (302) that occurred during a ZPA automatic reauthentication attempt after a user restarted the system.$$$Fixes an issue with posture updates that caused Zscaler Client Connector to be in a Connecting state for a prolonged time; resulting in a delayed connection to ZPA applications via an external proxy.$$$Updates the way Zscaler Client Connector retrieves the MAC Address from the device during registration to prioritize the active adapter connected to the internet.$$$Fixes an issue where WFP filters were not deleted correctly after a tunnel crash; resulting in an FW/AV error when trying to reconnect.$$$Fixes a delay in ZPA reauthentication that could occur when loading the page after a user authenticated with an IdP.$$$Fixes an issue where Zscaler Client Connector used the incorrect app profile after login for a user who was assigned an app profile configured for a device group using the Registry Key device posture profile with an HKEY_CURRENT_USER registry key.$$$Updates Zscaler Client Connector to not launch if a user starts the device in Safe mode.$$$Fixes an issue where process-based application bypasses sometimes did not work if the policy update of the app identity list failed.$$$Fixes an issue where Zscaler Client Connector did not download the PAC file after switching to a Split VPN-Trusted network with ZIA enabled; which could cause unexpected traffic handling.$$$Fixes an issue where the machine tunnel didn’t start after upgrading Zscaler Client Connector.$$$Fixes an issue where Zscaler Client Connector stopped working after users clicked Revert App if they had previously opened the app from the tray icon during an upgrade.$$$Fixes issues where the ZSATunnel service could crash when restarting due to conflicts in background processes.$$$Fixes connectivity issues with SQL Server for customers using ZPA without ZIA or Zscaler Digital Experience (ZDX) sending traffic through Z-Tunnel 1.0 to port 1433.$$$Fixes an issue where Zscaler Client Connector didnt connect to the ZPA Service Edge after switching from a machine tunnel to a user tunnel; causing some users t

April 22; 2025$$$Zscaler Client Connector 4.5.0.434 Enhancements and Fixes$$$Fixes a delay in detecting the captive portal when Zscaler Client Connector encountered network issues while establishing a connection.$$$Fixes an issue where Zscaler Client Connector displayed incorrect connectivity information in the app after a users device switched from an off-trusted network to a VPN network.$$$Fixes an issue where the Zscaler Internet Access (ZIA) trust level was incorrectly calculated using device posture results from the cache after a reboot.$$$Fixes an issue where Windows could display a blue screen for some users when flow logging was enabled.$$$Fixes an issue where Zscaler Client Connector could not access an IP-based Zscaler Private Access (ZPA) application due to LWF filters created based on an incomplete application list.$$$Fixes an issue where uploads to a network drive were slow when using the SMB (Server Message Block) protocol using ZPA.$$$Fixes an issue where a ZPA application sometimes could not be accessed due to Zscaler Client Connector not removing a previous entry for a proxied connection to use for the direct bypass connection.$$$Updates Zscaler Client Connector to ignore blank serial numbers when generating UDIDs; preventing multiple devices for a single user from having the same UDID.$$$Fixes an issue where Zscaler Client Connector remained on the Loading page when reauthenticating ZPA due to a posture evaluation delay.$$$Fixes an internal error (302) that occurred during a ZPA automatic reauthentication attempt after a user restarted the system.$$$Updates the way Zscaler Client Connector retrieves the MAC Address from the device during registration to prioritize the active adapter connected to the internet.$$$Fixes an issue where WFP filters were not deleted correctly after a tunnel crash; resulting in an FW/AV error when trying to reconnect.$$$Fixes a delay in ZPA reauthentication that could occur when loading the page after a user authenticated with an IdP.$$$Fixes an issue where Zscaler Client Connector used the incorrect app profile after login for a user who was assigned an app profile configured for a device group using the Registry Key device posture profile with an HKEY_CURRENT_USER registry key.$$$Updates Zscaler Client Connector to not launch if a user starts the device in Safe mode.$$$Fixes an issue where process-based application bypasses sometimes did not work if the policy update of the app identity list failed.$$$Fixes an issue where Zscaler Client Connector did not download the PAC file after switching to a Split VPN-Trusted network with ZIA enabled; which could cause unexpected traffic handling.$$$Fixes an issue where Zscaler Client Connector stopped working after users clicked Revert App if they had previously opened the app from the system tray icon during an upgrade.$$$Fixes issues where the ZSATunnel service could crash when restarting due to conflicts in background processes.$$$Fixes an issue where Zscaler Client Connector didnt connect to the ZPA Service Edge after switching from a machine tunnel to a user tunnel.

April 16; 2025$$$Zscaler Client Connector 4.4.0.428 Enhancements and Fixes$$$Fixes an issue where Zscaler Client Connector displayed incorrect connectivity information in the app after a users device switched from an off-trusted network to a VPN network.$$$Fixes an issue where the Zscaler Internet Access (ZIA) trust level was incorrectly calculated using device posture results from the cache after a reboot.$$$Updates Zscaler Client Connector to ignore blank serial numbers when generating unique device identifiers (UDIDs); preventing multiple devices for a single user having the same UDID.$$$Updates the way Zscaler Client Connector retrieves the MAC Address from the device during registration to prioritize the active adapter connected to the internet.$$$Fixes a delay in Zscaler Private Access (ZPA) reauthentication that could occur when loading the page after a user authenticated with an IdP.$$$Fixes an issue where Zscaler Client Connector used the incorrect app profile after login for a user who was assigned an app profile configured for a device group using the Registry Key device posture profile with an HKEY_CURRENT_USER registry key.$$$Fixes an issue where process-based application bypasses sometimes did not work if the policy update of the app identity list failed.

March 07; 2025$$$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 couldnt 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 Error message 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 Error message 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 07; 2025$$$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 couldnt 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 Error message 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 Error message 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$$$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 couldnt 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 Error message 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 Down error 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 06; 2025$$$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 couldnt 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 Error message 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 Down error 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 04; 2025$$$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.$$$Improves Zscaler Client Connectors handling of unattended installs when anti-tampering is 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.