End-of-Life (EoL)

GlobalProtect App 4.1.7 Addressed Issues

The following table lists the issues that are addressed in GlobalProtect™ app 4.1.7.
Issue ID
Description
GPC-7604
Fixed an issue where the GlobalProtect app for Chrome displayed the incorrect connection status after users closed and then reopened the app.
GPC-7537
Fixed an issue on Windows 10 endpoints where, if you configured the GlobalProtect app to wrap third-party credentials, users were unable to change expired passwords using the GlobalProtect Credential Provider.
GPC-7475
Fixed an issue on Windows 10 endpoints where, if a GlobalProtect user connected to a gateway with split tunneling and then switched to a gateway without split tunneling, the split tunnel logic from the original gateway persisted on the GlobalProtect app. This issue caused users to lose access to applications, as network traffic incorrectly continued to bypass the VPN tunnel.
GPC-7469
Fixed an issue on GlobalProtect app 4.1.6 where, if you configured a split tunnel to exclude traffic from the VPN tunnel based on access routes, GlobalProtect incorrectly installed all exclude access routes with a
/32
subnet mask instead of the configured subnet masks.
GPC-7438
Fixed an issue where the GlobalProtect app for macOS was not being upgraded transparently because the refresh configuration was not triggered properly.
GPC-7425
Fixed an issue where the GlobalProtect app could not connect to external gateways if you specified a
Source Region
other than
Any
in the external gateway configuration (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
External
<external-gateway-config>
). This issue occurred when you configured all external gateways as manual-only gateways and set the GlobalProtect
Connect Method
to
User-logon (Always On)
in the portal agent configuration (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
App
).
GPC-7406
Fixed an issue on Windows endpoints where, if you configured GlobalProtect with the SAML authentication method, the app displayed a
Portal Not Found
error message after users restarted their endpoints.
GPC-7404
Fixed an issue on Windows 10 endpoints where, if you configured GlobalProtect with the pre-logon connect method, the GlobalProtect Credential Provider displayed incorrect translations for the pre-logon connection status in all non-English languages.
GPC-7395
Fixed an issue with the UWP plugin for Windows 10 endpoints which caused GlobalProtect to report an
Invalid Argument
exception.
GPC-7345
Fixed an issue on Windows endpoints where gateway authentication failed when the network was unreachable during tunnel restoration.
GPC-7319
Fixed an issue where, if you configured a split tunnel to exclude application traffic based on the application process name, application traffic destined for UDP port 9000 was incorrectly sent through the VPN tunnel.
GPC-7314
Fixed an issue on Windows endpoints where the GlobalProtect app displayed the Welcome page only after connecting to a GlobalProtect gateway instead of after connecting to the GlobalProtect portal.
GPC-7309
Fixed an issue where the GlobalProtect app incorrectly saved usernames when you set the
Save User Credentials
option to
No
in the portal agent configuration (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
Authentication
).
GPC-7303
Fixed an issue where PanGPA halted unexpectedly when the endpoint was brought back from sleep and GlobalProtect switched from an internal to an external gateway.
GPC-7298
Fixed an issue with pre-logon where GlobalProtect prompted the user to authenticate to both the portal and gateway when the network was unavailable when the user logged into the endpoint.
GPC-7270
Fixed an issue on Windows 7 endpoints where, if you configured the options to
Enforce GlobalProtect Connection for Network Access
and
Display Traffic Blocking Notification Message
(
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
App
), the GlobalProtect app intermittently displayed the
Captive Portal Detected
message instead of the specified traffic blocking notification message even though a captive portal was not detected.
GPC-7178
Fixed an issue on Windows 10 endpoints where the domain name was pre-populated on the Windows login screen even when users selected the
Other
user login option. This issue occurred because the GlobalProtect credential provider was automatically set as the default credential provider on Windows 10 endpoints.
GPC-7176
Fixed an issue on Windows 10 endpoints where GlobalProtect displayed password expiry notification messages as toast notifications. With this fix, password expiry notification messages now appear as notification balloons in the system tray. If multiple GlobalProtect notifications trigger at the same time, the notification balloon also displays a
More Notifications
link, which enables users to view a summary list of the notifications.
GPC-7094
Fixed an issue where, if GlobalProtect was connected to an internal network with no internal gateways, the GlobalProtect app intermittently displayed the
Connecting
status even though network discovery was complete.
GPC-7023
Fixed an issue on Windows endpoints where the GlobalProtect app misidentified Kapersky Endpoint Security as Kapersky Antiphishing and indicated an incorrect version number in the Host Profile.
GPC-7018
Fixed an issue where the GlobalProtect app did not retain the domain name from
Username
inputs in the
domain\username
format following unsuccessful GlobalProtect authentication attempts.
GPC-6981
Fixed an issue where Windows activation failed upon system reboot because the Windows license was getting deleted when you enabled HIP checks.
GPC-6693
Fixed an issue on Linux endpoints where, after users established the GlobalProtect connection, network traffic was sent through the default route of the physical adapter instead of the default tunnel route. This issue occurred because the default route of the physical adapter had a lower metric and therefore higher priority than the default tunnel route.
GPC-6613
Fixed an issue where, if you set the
Save User Credentials
option to
Save Username Only
in the portal agent configuration (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
Authentication
), the GlobalProtect app incorrectly placed the cursor in the
Username
field instead of the
Password
field when users were prompted to enter their passwords for portal or gateway authentication.

Recommended For You