GlobalProtect
GlobalProtect App 6.2.1 Windows and macOS Addressed Issues
Table of Contents
Expand All
|
Collapse All
GlobalProtect Docs
-
- 10.1 & Later
- 9.1 (EoL)
-
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
-
- 6.1
- 6.0
- 5.1
-
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
GlobalProtect App 6.2.1 Windows and macOS Addressed Issues
GlobalProtect App 6.2.1 Windows and macOS Addressed Issues
The following table lists the issues that are addressed in GlobalProtect app 6.2.1 for
Windows and macOS.
Issue ID | Description |
---|---|
GPC-18789
|
Fixed an issue where the GlobalProtect app took a long time to
connect to the gateway when the include domain list was used, while
the enhanced split-tunnel feature was not used.
|
GPC-18788
|
Fixed an issue where the GlobalProtect HIP check did not detect
McAfee Total Protection as an anti-malware application, which caused
the device to fail the HIP check.
|
GPC-18594
|
Fixed an issue where the GlobalProtect app was unable to send HIP
reports when the app was connected using IPv6.
|
GPC-18566
|
Fixed an issue where the GlobalProtect app incorrectly displayed the
gateway as internal when it was connected to an external
gateway.
|
GPC-18528
|
Fixed an issue where the GlobalProtect HIP check incorrectly detected
the version for KES 12 (Kaspersky Endpoint Security), which caused
the device to fail the HIP check.
|
GPC-18509
|
Fixed an issue where, when the GlobalProtect app was configured with
the Internal Host Detection and Conditional Connect method, the app
did not connect to the internal network when the network was changed
from external to internal as it should have with the Conditional
Connect method enabled.
|
GPC-18452
|
Fixed an issue where, when the GlobalProtect app was installed on
Windows devices the app did not start right away after a system
reboot.
|
GPC-18426
|
Fixed an issue where when the GlobalProtect app was configured with
the Disable GlobalProtect set to
Allow with Ticket, the app did not
display the correct Disable Duration time.
|
GPC-18336
|
Fixed an issue where the GlobalProtect app got automatically
connected after a system reboot even though the connection method
configured was On-Demand.
|
GPC-18318
|
Fixed an issue where, when the GlobalProtect app was connected to the
internal gateway, the app displayed the message as
Connected - Inter.... instead of
Connected - Internal.
|
GPC-18281
|
Fixed an issue where the MSI install logs showed mutiple messages for
Autonomous DEM installation.
|
GPC-18251
|
Fixed an issue where the GlobalProtect HIP check did not detect
McAfee LiveSafe as an anti-malware application, which caused the
device to fail the HIP check.
|
GPC-18230
|
Fixed an issue where, when the user entered credentials during SAML
authentication after the set internal login timer, the app displayed
an authentication failed message without providing the reason. The
Retry button on the app web interface did
not work properly when using an embedded browser for authentication.
The Retry button was not fully visible on the
embedded browser.
|
GPC-18175
|
Fixed an issue where users were prompted to enter their credentials
even when the GlobalProtect app was configured for authenticating
with either Authentication Profile /Cookie or Client
Certificate.
|
GPC-18173
|
Fixed an issue where the vertical scroll bar on the GlobalProtect app
web interface did not work properly when users tried to select the
certificate from the drop-down.
|
GPC-18171
|
Fixed an issue where users were unable to select the external gateway
manually when connected to the internal network. The GlobalProtect
stayed in Connecting state and users
had to manually disconnect the connection and connect to the
internal network to exit the Connecting
state.
|
GPC-18167
|
Fixed an issue where the GlobalProtect app displayed the Prisma
Access gateways that are not set for manual selection.
|
GPC-18146
|
Fixed an issue where, when the GlobalProtect app was installed on
Windows devices, the GlobalProtect HIP check did not detect the
correct details for Cortex XDR, which caused the device to fail the
HIP check.
|
GPC-18135
|
Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the GlobalProtect HIP check detected the
WithSecure antivirus software as XProtect, which caused the device
to fail the HIP check.
|
GPC-18107
|
Fixed an issue where the GlobalProtect HIP check did not detect
McAfee LiveSafe – Internet Security, which caused the device to fail
the HIP check.
|
GPC-18092
|
Fixed an issue where GlobalProtect connected to an internal gateway
got automatically disconnected after a certain period of time.
|
GPC-18073
|
Fixed an issue where the GlobalProtect app selected an unexpected
gateway due to a latency discrepancy seen between PanGPS and packet
capture.
|
GPC-18060
|
Fixed an issue where the GlobalProtect HIP check did not detect
McAfee Total Protection, which caused the device to fail the HIP
check.
|
GPC-18036
|
Fixed an issue where, when the No direct access to local
network option was enabled on the GlobalProtect app
with access routes excluded from the GlobalProtect VPN tunnel, the
feature did not work as expected when Endpoint Traffic Policy
Enforcement was enabled.
|
GPC-17936
|
Fixed an issue where the Conditional Connect method did not work as
expected and users had to manually connect the app when they changed
their network.
|
GPC-17921
|
Fixed an issue where, when the language was set to Japanese, the time
to connect was not displayed properly when Disconnect
Timeout for the app was configured.
|
GPC-17896
|
Fixed an issue where users were unable to connect to GlobalProtect
gateway when only one external gateway was added due to the
following error: Cannot Verify Server Certificate of
Gateway.
|
GPC-17816
|
Fixed an issue ehere after entering CIE SAML authentication
credentials to refresh an expired explicit proxy token or cookie
when connected in Tunnel and Proxy mode or
proxy mode, the
GlobalProtect app got stuck while retrieving the portal
configuration.
|
GPC-17795
|
Fixed an issue where the GlobalProtect HIP check did not detect the
Xcitium Enterprise, the Endpoint Protection Platform by COMODO,
which caused the device to fail the HIP check.
|
GPC-17776
|
Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS and GlobalProtect enforcer was configured with
allowed FQDNs, users were still able to access the internet and
other public domains.
|
GPC-17762
|
Fixed an issue when the GlobalProtect app was configured with the
option Allow User to Disable GlobalProtect
App with comment, the option did not work as
expected.
|
GPC-17748
|
Fixed an issue where the GlobalProtect HIP check did not detect the
Real-Time Protection status correctly for the CrowdStrike Falcon
application, which caused the device to fail the HIP check.
|
GPC-17740
|
Fixed an issue where, when the GlobalProtect app was connected
through the Prisma Access gateway, the upload speed of the internet
was reduced to 2 Mbps.
|
GPC-17728
|
Fixed an issue where users were unable to connect to GlobalProtect
gateway when only one external gateway was added due to the
following error: Cannot Verify Server Certificate of
Gateway.
|
GPC-17460
|
Fixed an issue where, when the GlobalProtect app was installed on
Windows 10 or 11 devices, and when the user tried to authenticate
using SAML authentication, the app did not display the
Term of Use pop-up on the
Welcome page properly.
|
GPC-17398
|
Fixed an issue where the GlobalProtect app SettingsConnection tab did not display the Assigned IP
Address(es) and Gateway IP
Address properly.
|
GPC-17206
|
Fixed an issue where, when Internal Host Detection (IHD) was enabled
but failed to detect the internal network properly, the app failed
to switch to the external gateway when users switched from an
internal network to an external network.
|
GPC-17161
|
Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the GlobalProtect app failed to reconnect and
continued to stay in the Connecting state
after the device woke up from Modern Standby mode.
|
GPC-17099
|
When the GlobalProtect app for Windows is upgraded to version 6.0.5,
devices with Driver Verifier enabled and configured to monitor the
PAN virtual adapter driver (pangpd.sys) display the
DRIVER_VERIFIER_DETECTED_VIOLATION Blue Screen error.
|
GPC-17001
|
Fixed an issue where, when the GlobalProtect app was installed on
devices running on macOS, the app did not display the
Connect button and Refresh
Connection button properly.
|
GPC-16978
|
Fixed an issue where the GlobalProtect app took a long time to
establish a connection due to an erroneous packet capture
process.
|
GPC-16851
|
Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the app did not try to auto-connect to the
gateway after exceeding the Disable Timeout
Value.
|
GPC-16397
|
Fixed an issue where the GlobalProtect app was installed on devices
running macOS, a blank GlobalProtect app user interface was
displayed instead of the correct page.
|
GPC-16126
|
Fixed an issue where the GlobalProtect app did not display the
certificate name in the Client Certificate selection field
properly.
|
GPC-16003
|
Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the app was not connected when the proxy was
configured for Safari or Chrome.
|
GPC-15968
|
Fixed an issue where the GlobalProtect app was stuck in
Connecting state when users failed to
authenticate with SAML and using an embedded browser. Users were
unable to disconnect the app and had to reboot the device.
|
GPC-15262
|
Fixed an issue where when single sign-on (SSO) for Smart Cards was
used for authentication, users were prompted to enter a PIN instead
of a password on the Windows login screen.
|
GPC-15234
|
Fixed an issue where the app would get stuck at Connecting state
while trying to connect to a gateway.
|
GPC-15080
|
Fixed an issue where when the split tunnel was configured based on
the destination domain, split tunneling did not work as expected
when IPv6 traffic exclusion was configured.
|