Fixed Issues

Release 9.1R13.1

MacOS users are getting disconnected with latest PDC.

End users see disconnects and reconnects on the PDC UI, When connected to PCS that resolves to IPv6.

(Host Checker) OS check pass on Windows 11 systems. Policy is configured for "Windows 10-64-Bit".

Pulse Desktop Client continuously changes between connected and connecting states, When connected to PCS that is configured in SSL Transport mode.

Users are not able to connect the resource from WSL on windows 11 through PSAM, Install Ubuntu 20 with WSL 2 on Windows 11 and try to connect to resource behind PCS server through PSAM.

SAML, Custom Sign-in pages and Pulse Collaboration features do not work with External Browser on Windows 11, When using external browser.

Pulse Client Agent Type on PCS “Active Users” Page shows as "Windows 10 Pulse Secure" for Windows 11 end points, When using Windows 11 Operating System.

Pulse client VPN tunnel connection fluctuates with Split-Tunnel, When connected to PCS that is configured in ESP Transport mode along with (IP/FQDN) Split-Tunneling.

Telnet/SSH bookmarks are not working on Windows 11, When using Windows 11 as client machine.

Merging Occasional PulseSecureService.exe crash fix to R13.1.

Release 9.1R13

User Certificate authentication fails in Mac OS when a generic exception occurs during the certificate structure is validation.

Client cert information, such as serial number and certificate, is not available in PCS user access logs.

PDC Support for Debian 10.10 past PDC 9.1R8.2

“Failed to setup virtual adapter error” message displays when PDC upgrade fails and rolls back to older version.

Pulse Desktop Client gets disconnected while accessing resource if the DNS response packet is very big and does not reconnect automatically.

Conditional Access "Certificate selection prompt" does not appear through PDC on macOS 11.3 and later

CentOS 8 shows blank screen while trying to authenticate with Pulse client having AZURE SAML Authentication.

Intune compliance check fails with macOS native embedded browser.

Memory / Handler Utilization increases with Pulse client installed over a period and cause laptops to slow down until it is rebooted.

EAPOL flooding causes high CPU Utilization.

After PDC Upgrade from 9.1R2 to 9.1R11, machine tunnel is not formed.

Machine cert detection fails on Pulse Client version 9.1R11 when using credential provider.

Any screen sharing application does not work when Pulse Client is running.

Performance improvements (Download) for Pulse Windows Clients in ESP mode

Release 9.1R12

Connection set-- name is not populating special characters properly.

ESAP download fails through Pulse Client when host header validation is enabled on PCS.

Pulse Client Repair Tool Fails To Complete - Error 1720.

Machine authentication using certificate failing with error CertOpenStore() failed error: 0x5: Access is denied when using pulselauncher command.

On some machines, the pulse client upgrade prompt is not seen for the end-user when connecting to 9.1R11.5 PCS using the older client (like 9.1R11.3 or 9.1R11.4).

PDC 9.1R11 disconnects lead to Kernel panic in macOS Catalina 10.15.7.

Memory / Handler Utilization increases with Pulse client installed over a period of time and causes slowness on Laptops until the laptop is rebooted.

Unable to assign NCIP from the static IP pool in PCS 9.1R11.4.

Users are facing the Blue Screen of Death issue after upgrading to the 9.1R11 client.

PulseUI crashes Ubuntu 20.04 LTS.

PDC Linux PulseUI Crash Due to ZTA.

Windows Pulse Client 9.1r11 with Avaya One-X causing BSOD.

Machine cert detection failing on Pulse Client version 9.1R11 when using credential provider.

Pulse Linux client requires interaction for upgrade.

A user with a Mac PC running Mojave 10.14.6 runs into a issue where at times it takes three minutes to disconnect.

IPv6 default route on Mac is not set correctly with PDC 9.1r11.

SAML authentication looping after entering the credentials in Ubuntu 20.04.

PulseTray process crash due to PZTA code merge on MacOS client.

FQDN based AlwaysON VPN connection disconnects while undocking or coming out of sleep mode

VPN session reconnects from Pulse Linux CLI client if the session is deleted from PCS

After upgrade the PDC 9.1R10 lockdown is not working

User is unable to open the HMTL link in the remediation instruction when the HC fails on MAC machine.

Domain suffix cleanup issue after VPN tear down when customer modifies DNS suffix list during runtime.

No Internet access when connected via Pulse; but in 9.1R10.

PDC 9.1R11 Windows client behavior taking 2x longer time for “securing connection” and disappearing UI profiles.

PDC upgrade to 9.1R9 or 9.1R10 breaks PSAM for certain users.

Pulse: Kernel panic on macOS when traffic enforcement is enabled

Pulse 9.1R9 for MacOS behavior: Menu disappears and reappears continually with no internet access but was fine in 9.0R6.

PDC fails to download PAC file defined in IE browser auto proxy URL location.

PAC file has extra line added which cause resource access issue with same connection again.

When FQDN based Split Tunnel is enabled, DDNS registers both physical and virtual IPs to internal DNS server.

SAML Embedded Browser tries to open on Secondary Screen while the Monitor is in disconnect state.

Multiple Users getting disconnected immediately after connecting to PCS server.

PDC VPN connection failover in A/A cluster setup taking more than 3 mins time.

Query regarding the NCF_HIDDEN flag

FQDN url configured under split tunnel deny policy is passing through tunnel.

Host Checker Crash in Mac OS.

Unable to switch between the server URL's post upgrading to Pulse Client 9.1R7 from 5.3R7

802.1x Pulse is not connecting automatically while boot from Hibernate Mode.

Long delay when disconnecting with Pulse client 5.2RX on macOS connecting to 8.1RX.

Release 9.1R11.5

ESAP download fails through Pulse Client when host header validation is enabled on PCS.

Intermittently, physical Interface DNS is not Restored.

Release 9.1R11.4

PDC 9.1R11 triggers lockdown enforcement when the workstation is unattended.

PDC 9.1R11 in MacOS Big Sur and Catalina after "sudo reboot" loses internet connectivity until Pulse service is disabled.

Any screen sharing application does not work when Pulse client is running.

Release 9.1R11

Failed to download the CEF package from Spotify download location.

For more information on fix, refer KB44699.

Host Check fails on macOS 11.1 when the policy is enforced.

For more information on fix, refer KB44663.

Customizing username/password and secondary username / secondary password label is not displayed on PDC Linux client.

Host checker policy based on process check failed on Linux machine.

COM API failure during initialization leads to the failure of the interface classification. Hence, the Hyper-V virtual adapter is wrongly classified as a Physical adapter.

Host checker not detecting Linux process running under root.

PSAM fails to intercept Web application traffic using Java Applet.

Browser-based Host checker fails to get launched in 64 Bit Internet Explorer.

Premier Java RDP does not launch when Java8u261 is used in MAC OS.

PSAM: DNS resolution fails intermittently.

PSAM fails to tunnel ipv6 traffic when a resource is configured more than once with a different port (For instance, [fc01:2001:xx:xx::xx]:80 [fc01:2001:xx:xx::xx]:443).

Predefined Host Checker policy can now be configured with a ignore category based on the vendor.

Release 9.1R10

Pulse Client Debug log file path contains spaces.

Host Checker OS check failure on Big Sur.

The auto connection is not triggered when connecting through Bluetooth tethering, as it is treated as a virtual adapter.

Certificate Authentication is not working with EKU/OID Filtering enabled when certificates are stored in machine store.

IT administrators can now upgrade/install Pulse macOS Client from PCS successfully.

Proxy PAC file is populated incorrectly since the buffer is not clearing after each update.

When branding option is used to customize Pulse Desktop Client and an upgrade is attempted, it fails in some cases.

The fix is to not to evaluate the LA policy before connection establishment. Also, we have verified that the DNS are restored after the first connection gets disconnected and before the second connection tries to establish the connection. This affects the PDC Releases between 9.1R5-9.1R9.1

'Advanced Connection Details' translation string of Pulse client on non-english OS is not correct.

The existing Opswat SDK/ESAP files are retained during the Pulse Client Upgrade on Windows, instead of replacing it with the default ESAP version.

End-Points connected through slow internet will not hit the incomplete ESAP package download scenario.

Juniper Network Service is disabled by default from 9.1R10 Release when connecting to PCS.

Release 9.1R9

Due to Memory Corruption caused by the Pulse SAM driver, the computer crashes with Blue screen Stop code: “PDC WATCHDOG TIMEOUT”.

Agent Type on active users page on PCS fails to show Windows OS version with 9.1R8 PDC builds.

Certificate authentication fails from 9.1 R5 to 9.1 R8 on Ubuntu machines.

Pulse adapter shows as “Unidentified Network” intermittently. The fix is implemented per MSFT recommendation :

https://support.microsoft.com/en-us/help/4550028/firewall-profile-does-not-switch-to-domain-when-using-third-party-vpn

Connection fails even after successful authentication at IdP if capital letters are used to create SAML Connection URL in Pulse Desktop Client.

Unable to intercept traffic using WFP driver when a subnet is defined in WSAM destination.

Pulse Collaboration stops working after Setup Client download fails, after upgrading it to PCS 9.1R8.

Lockdown exception path for MS Teams using system variables is not working.

PSAM driver memory leaks for UDP traffic.

Session extension fails when custom sign-in page is configured for the sign-in policy. This is addressed in 9.1R9.

Release 9.1R8.2

Wireless Dot1x authentication fails on upgrading to PDC 9.1R8.

Host Checker fails with TnccHandleException.

The Sign-In Notification page shows the text underlined.

GPU used by the Pulse Client on MAC with SAML Embedded Browser is used to connect to VPN.

Some heavy applications such as Microsoft Teams configured through PSAM may exhibit slowness with time due to a Memory Leak in PSAM driver.

RHEL 8 has deprecated many libraries that are required by libwebkitgtk, which is used by Pulse Client.

Pulse Client does not change the interface metric to “1” and sets to “automatic”.

Pulse client not reverting back the windows hosts file after the pulse client logs off.

Setup client unable to invoke PSAL on MAC machines.

Release 9.1R8

Pulse Client UI reports “Pulse Secure service is not running”.

System proxy settings are ignored due to wrong hardcoded path to libproxy.so.

Pulse Desktop Client (Windows/MAC) does not honor the configured Split-Tunneling policies (Allow or Deny) due to Non-Compressed DNS responses.

Pulse Client on macOS uses dedicated graphics card, causing faster battery drain.

Pulse Client gets stuck at Host Checker when endpoint has Pulse Secure Installer Service (PSIS) older than 9.1R7.1 installed.

Microsoft APIs return the incorrect value '6.2' when running Host Checker for system files such as GdiPlus.dll, as the applications are not manifested for Windows 8.1 and Windows 10.

Release 9.1R7.1

Upgrade to PDC 9.1R7 results in folder access issues. Pulse Logs can miss certain files or folders.

DNS entries set manually on Physical adapters are not restored when FQDN Split Tunneling is configured.

Not able to open 'C:\ProgramData\Pulse Secure' folder after installing PULSE9.1R7.

Some heavy applications such as Microsoft Teams configured through PSAM may exhibit slowness with time due to a Memory Leak in PSAM driver.

PSAM resource is not accessible when configured more than once with different port numbers on multiple lines. Only resource:port configured in first line is accessible.

This issue is fixed only for IPV4, IPV6 issue is tracked with PRS-392916.

Intermittently, DNS entries on physical adapters are not restored if the machine is rebooted during a tunneled connection that has FQDN split tunneling configured.

Release 9.1R7

Pulse Desktop Client (Windows) does not honor the configured Split-Tunneling policies (Allow or Deny) due to Non-Compressed DNS responses.
For more information, refer to KB article https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44461/?kA13Z000000L3IN.

MSI uninstall through SCCM fails with “1622 (ERROR_INSTALL_LOG_FAILURE)”.

PDC sets the “Domain Suffix Order” set incorrectly on macOS.

Intermittently, Pulse Desktop Client (Windows) does not update the exclude routes in its routing table after a tunnel connection.

For more information, refer to KB article https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44461/?kA13Z000000L3IN.

FQDN Split tunneling Deny Policies matches the substring as opposed to the complete suffix match (e.g. rass.net goes out of the tunnel even when the FQDN ST Deny rule is set to *.s.net).

Pulse client installation may fail on native foreign Windows 10 operating system.

For more information, refer to KB article https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44485/?kA13Z000000L3IN.

Release 9.1R6

Intermittently, DNS entries on physical adapters are not restored if the machine loses Network connectivity or if it goes to sleep/hibernate during a tunnelled connection when using FQDN split tunnelling.

For more information, refer to KB article https://kb.pulsesecure.net/articles/
Pulse_Secure_Article/KB44429/?kA13Z000000L3Fn.

Release 9.1R5

Unable to access Internet Sites after upgrading PDC to 9.1R4 on Mac OS

It has been reported that the location awareness rule evaluation is returning unexpected results in 9.0R6 & 9.1R4 compared to the previous versions.

Virtual adapter stops intercepting packets on Mac using PDC 9.1.3 build 1413

Juniper Network Service can be disabled on Pulse client if it causes interop issues (Such as Slowness/Still Traffic).

PAC file is not changing to instantproxy.pac when "No proxy" is configured on the PCS server.

During cert auth, Pulse client is reconnecting multiple times leading to increased authentication attempts.

IPv6 Default route does not get created for the VA if the native adapter (en0) is configured with both v4 and v6 addresses.

While processing 802.1x connection setup in "machine then user" mode, PPS ends up using the same Access-Accept attributes for both machine and user auth.

Prompts saying unable to import Certificate Revocation List while Captive portal in Embedded browser loads on Windows machine - PDC 9.1.4 (1937.1).

MAC PDC client fails to detect the smart card in the presence of client auth EKU has configured till pulse App restarted.

Multiple windows login prompt when we use Pulse Credential Provider with Host Checker.

Upon performing a switch user, 802.1x connection is disconnected when using a pulse client whereas it doesn't while using Native supplicant.

Release 9.1R4.2

After upgrading to 9.1R4 and above, PSAM is unable to access any resources when multiple ports are configured.

Pulse Client connection is not connected after resuming from Sleep.

Pulse Layer 3 session disconnects when RDP session is closed, causing the resource to drop.

Release 9.1R4.1

PSAM forces all the Java URL's request default to IPv6.

PDC throws Authentication rejected by server [Error : 1319] when using global url

Users are facing issues while accessing the Shock Wave Flash application via PSAM. The application gets stuck randomly.

PSAM WFP mode blocks local socket bind operation.

PSAM sending unintended traffic via tunnel to VPN in PULSE9.1R3

Release 9.1R4

PSAM resource access does not work when connecting to 9.0 or 8.3 gateways using 9.1 client.

PSAM does not work with local host-based applications when WFP is enabled.

CAV feature generating traffic to PCS node, though not enabled. Cloud license is not installed on PCS.

Pulse: File Based PAC support deprecated.

CLI based PDC on Linux fails to prompt for password during authentication.

Route table is not getting updated once the session is extended, when Embedded browser is enabled.

Lockdown mode is not getting enforced on the Client machine.

For macOS machines, Pulse SAML embedded browser prompts to pick the certificate from the list of incorrect certificates to authenticate with Microsoft Azure IDP.

Pulse client wireless suppression does not re-enable wireless adapter intermittently.

Chrome browser version 76.x on macOS is unable to proxy the traffic and access the resource.

Embedded Browser for Captive portal comes up blank when Lockdown mode is enabled.

The pop-up message in Japanese is garbled while un-installing Pulse Client 9.1R2.

Location Awareness policy is getting evaluated for both physical and virtual adapter and causing the Pulse client disconnection.

Release 9.1R3.1

Unable to resolve the DNS in Pulse Desktop Client - 9.1R2 for macOS.

Wireless Suppression - Wireless adapters are disabled and needs to be enabled manually.

Unable to establish tunnel with smart card reader when end-user has latest 10.15 macOS i.e.Catalina.

Release 9.1R3

FQDN Split Tunneling Route, AddRoute shows error 87.

“Host checker did not get installed properly" error appears on browser after the machine reboot.

Incorrect client platform as 'Windows' instead of 'Win' causes lockdown exception to fail.

"Failed to clear PIN" error when using Yubikey smart card.

Pulse Client prompt "Blank screen" when using SAML-OKTA Authentication with Pulse Embedded Browser.

Pulse UI will be in securing connection state for more than 3 minutes. when traffic enforcement is enabled for both Ipv4 and Ipv6

On multi-display setups, the Pulse Secure desktop client login window spawns offscreen.

Enter Key is not working when using SAML Authentication with Pulse Embedded Browser.

Username is limited to 32 character on ChromeOS Pulse Client.

For stealth mode connection Use Desktop Credentials option should not be enabled while creating the connection.

Release 9.1R2

Missing certificate issue when Pulse Client is launched in Ubuntu 18.0.4 version.

IPv6 - After upgrading Pulse Client from 5.3R2 to 5.3R4.1 on a macOS machine, IPv6 DNS is not getting set on the Virtual adapter.

Pulse Client Uninstall.app is not code signed.

Logon Scripts are not running with lockdown mode enabled.

Installing Pulse Client 9.0R2+ on macOS is creating a performance hit over time.

Kernel panic issues is observed on macOS Mojave (10.14) with Pulse Client version 9.0R3 (build 1599).

Machine tunnel is not working as expected with DNS domain suffix and step up deletes the domain from the list incorrectly.

NSIS error message is thrown after installing Pulse Client through SCCM.

Smart card (Certificate) authentication is failing with Pulse Client 9.0R3 after Gemalto SafeNet client is upgraded to 10.2.

Overwrite DNS suffixes on macOS clients.

Random IPv4 resource is failing when ACL and split tunneling are configured with FQDN.

Release 9.1R1

Symbolic link creation fails after Pulse upgrade.

Authentication with Host Checker verification fails on Kernel 4.18.0-10.

Unable to add multiple certificates to gnome-keyring.

Pulse: Customer facing frequent disconnection post adding FQDN and IPv4 addresses in Split tunneling rules.

Wireless suppression fails to re-enable wireless NIC when surface PRO's USB network adapter is unplugged.

Pulse: macOS: Re-branding: Modified Username and Password Label not showing completely on MAC machines.

Color management is not working in macOS 10.14(Mojave) when French language is used.

Wireless disconnects after upgrading to Win 10 1803.

Pulse desktop client prompts for proxy credentials when wild card exception is used in PCS URL.

Captive Portal detection via Pulse client fails and shows a blank page with latest 9.0R2.1 version in Windows 10 OS.

Pulse is not honoring the zscaler proxy exception.