End-of-Life (EoL)

GlobalProtect App 4.1.3 Addressed Issues

GlobalProtect™ app 4.1.3 addressed issues
The following table lists the issues that are addressed in GlobalProtect™ app 4.1.3.
Issue ID
Fixed an issue with split tunneling that allowed traffic for excluded domains to be sent over the GlobalProtect tunnel when the domain entry included a wildcard (for example, *.domain.com).
Fixed an issue on Google Chromebooks where the GlobalProtect app displayed a blank page when an end user launched the app.
Fixed an issue on the GlobalProtect app for Windows and macOS endpoints where the
Sign Out
option was missing from the
tab of the GlobalProtect Settings panel. This issue occurred when you configured the GlobalProtect portal or gateway to use SAML authentication with single logout (SLO) enabled.
Fixed an issue where the GlobalProtect app selected a certificate from the user store (if present) when the
Client Certificate Store Lookup
option is set to Machine only. With this fix, the GlobalProtect app performs certificate lookup only within stores indicated by the
Client Certificate Store Lookup
Fixed an issue on Mac endpoints where OPSWAT libraries were unable to detect Sophos Home antivirus software for HIP reports.
In PAN-OS 8.0.x and earlier releases, Sophos Home is called Sophos Anti-Virus.
Fixed an issue with the
Enforce GlobalProtect
feature on Mac endpoints where GlobalProtect did not restrict access to the internet when the GlobalProtect app was disconnected or if the end user rediscovered the network.
Fixed an issue where Windows users were unable to connect to GlobalProtect after manually upgrading from GlobalProtect app 4.0.5 to GlobalProtect app 4.1.1 or 4.1.2 using the Windows Installer (Msiexec). During the upgrade, the PanGPS service failed to install due to a timing issue between the DeleteServices and InstallServices actions in the Windows Installer.
Fixed an issue on Windows endpoints where, if users configured a local host proxy to, ran a continuous ping to the local host address (, and then established a GlobalProtect connection, the ping output stopped when they disconnected GlobalProtect due to a corruption in the TCP/IP and Winsock catalog.
Fixed an issue on Windows endpoints where, if you configured the GlobalProtect app to support multi-factor authentication, browser-based authentication prompts did not close when users clicked
. Users could close the authentication prompt only by clicking the close (
) button.
Fixed an issue on Windows and macOS endpoints where the GlobalProtect app intermittently prompted users to upgrade the app when you set the
Allow User to Upgrade GlobalProtect App
option to
in the portal agent configuration.
Fixed an issue where you could not adjust the size of the GlobalProtect Settings panel in the GlobalProtect app for Windows endpoints.

Recommended For You