GlobalProtect
Addressed Issues in GlobalProtect App 6.2
Table of Contents
Expand All
|
Collapse All
GlobalProtect Docs
-
- 10.1 & Later
- 9.1
-
- 6.2
- 6.1
- 6.0
- 5.3
- 5.2
- 5.1
-
- 6.1
- 6.0
- 5.2
- 5.1
-
- 6.2
- 6.1
- 6.0
- 5.3
- 5.2
- 5.1
Addressed Issues in GlobalProtect App 6.2
Review the list of addressed issues in GlobalProtect app 6.2 for Windows and
macOS.
GlobalProtect App 6.2.3 Addressed Issues
The following table lists the issues that are addressed in GlobalProtect app 6.2.3
Windows and macOS.
Issue ID | Description |
---|---|
GPC-19968 | Fixed an issue where the GlobalProtect agent failed to detect
Bitdefender Antivirus Plus on the Windows ARM64 platform during the
HIP check. |
GPC-19924 | Resolved intermittent connection issues for users accessing
GlobalProtect via an embedded browser. |
GPC-19901 | Fixed an issue where the GlobalProtect client for Mac users was
intermittently disconnecting and reconnecting. |
GPC-19840 | Fixed an issue where Mac computers did not display all gateways
in the Search Gateway tab. |
GPC-19818 | Fixed an issue where when the Enforcer was enabled, Jamf connect
was not working after the MacBook was rebooted. Users had to log in
manually. |
GPC-19784 | Fixed an issue where McAfee Premium individual was not detected
by OPSWAT. |
GPC-19753 | Fixed an issue where the GlobalProtect icon could not be selected
using the keyboard. |
GPC-19712 | Fixed an issue where PanGPS crashed on 6.0.4 caused by invalid
memory reference. GlobalProtect did not run correctly after the
system was rebooted. |
GPC-19686 | Fixed an issue where translation errors were observed in the
GlobalProtect app for French localization. |
GPC-19664 | Fixed an issue where users were able to deploy GlobalProtect from
JAMF on Mac Sonoma, but the connection to the portal was
stuck. |
GPC-19659 | Fixed an issue where macOS users were connected to the
GlobalProtect app before they agreed to their company’s terms of
service. |
GPC-19656 | Resolved an issue where connecting to a GlobalProtect gateway
with IPv6 from macOS resulted in the tunnel connection dropping
every 45 seconds when Endpoint Traffic Policy Enforcement was set to
All Traffic. |
GPC-19630 | Fixed an issue where the prelogon connect method failed on the
gateway prelogin stage. |
GPC-19587 | Fixed an issue where the user could not login with Okta on macOS
when Endpoint Traffic Policy Enforcement was set to All
traffic . |
GPC-19581 | Fixed an issue where GlobalProtect indicated that Windows
firewall was not enabled in the HIP report even though it was
enabled. |
GPC-19545 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, users were unable to connect to the
GlobalProtect app when they used T-Mobile iPhone hotspot. |
GPC-19524 | Fixed an issue where the GlobalProtect app connection failed when
the user used CAS authentication to authenticate to the app. The app
displayed the error message, "Username from CAS SSO response is
different from the input". |
GPC-19513 | Fixed an issue where the GlobalProtect client was trying to use
the old portal's authorization cookie to login instead of the newly
migrated portal. This happened when the user changed from secondary
portal to primary portal or vice versa without signing out. |
GPC-19475 | Fixed an issue where users got connection errors in an embedded
browser after the computer woke up from sleep or when the user
switched gateways. |
GPC-19449 | Fixed an issue where the GlobalProtect client was trying to use
the old portal's authorization cookie to login instead of the newly
migrated portal. This happened when the user changed the portal from
secondary to primary or vice versa without signing out. |
GPC-19433 | Fixed an issue where a small white blank page randomly popped up
on the user's screen and the focus shifted to this blank page. This
issue occurs while the computer is connected to Global
Protect. |
GPC-19431 | Fixed an issue where interactive components in the session tray
on Windows did not receive keyboard focus and were not keyboard
operable. |
GPC-19418 | Fixed an issue where GlobalProtect users randomly experienced
issues connecting to the gateway after their computer woke up. This
occurred when Enforce GlobalProtect for Network Access was enabled
and Tunnel and Proxy was set to agent mode. |
GPC-19416 | Fixed a GlobalProtect redirection issue in embedded browser. When
a user tried to connect to GlobalProtect, an error was displayed
while waiting for the SAML response instead of being redirected to
the embedded browser. |
GPC-19414 | Fixed an issue where GlobalProtect Always-On connect method was
not triggered after a reboot when the connect-method setting was set
to on-demand in the Windows Registry. |
GPC-19403 | Fixed an issue where OPSWAT was unable to detect Kaspersky after
an upgrade from 21.3.10.391 to 21.15.8.493. |
GPC-19400 | Fixed an issue where the GlobalProtect HIP check did not detect
the Definition Date for Bitdefender Virus Scanner, which caused the
device to fail the HIP check. |
GPC-19391 | Fixed an issue where GlobalProtect stayed disconnected even after
being unlocked. |
GPC-19387 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the app displayed text incorrectly when the
system language was German. |
GPC-19374 | Fixed an issue where the GlobalProtect debug logs displayed
information, which was not supposed to display in the logs. |
GPC-19359 | Fixed an issue where system extensions on MacBook were not
updated after the GlobalProtect client was upgraded. |
GPC-19340 | Fixed an issue where the GlobalProtect app failed to send HIP
reports hourly. |
GPC-19337 | Fixed an issue where the Captive Portal functionality of the
GlobalProtect app did not work as expected when the users used
public Wi-Fi hotspots. |
GPC-19331 | Fixed an issue where, when SAML authentication was used to
authenticate to the GlobalProtect app, the app used an unknown
username ‘SAMLUser’ which was not configured instead of the actual
username of the user, which caused an authentication
failure. |
GPC-19314 | Fixed an issue where, when the GlobalProtect app is installed on
devices running macOS, the app displayed the message, ‘Downloading
in progress’ when the GlobalProtect app was upgraded to 6.0.x using
the option ‘Allow Transparently.’ The app should not display the
message when upgraded using the transparent method. |
GPC-19284 | Fixed an issue where GlobalProtect was unable to extend user
session. |
GPC-19280 | Fixed an issue where, when the GlobalProtect app transitioned
from pre-logon to user-logon tunnel, the app did not display the
list of gateways for the users to change the gateway. The gateway
list was displayed only when the app was refreshed. |
GPC-19262 | Fixed an issue where GlobalProtect 6.2.1 tried to connect
automatically after the user restarted their computer even though
the connect method was set to On-Demand. |
GPC-19193 | Fixed an issue where the GlobalProtect app was unable to fetch
Windows firewall and antimalware information correctly. |
GPC-19162 | Fixed an issue where, when the user upgraded the GlobalProtect
version to 5.2.13 or later, the HIP report displayed the DLP
‘Digital Guardian Agent’ as disabled. |
GPC-19107 | Fixed an issue where some log files were missing from the
GlobalProtect bundle when downloaded from the Explore app. |
GPC-19104 | Fixed an issue where the GlobalProtect HIP report failed to
detect the Real Time Protection status for Cortex XDR, which caused
the device to fail the HIP check. |
GPC-19083 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the Connection tab under app Settings did not
display the connection status and refresh connection did not work
when the Settings window was opened. |
GPC-19074 | Fixed an issue where Login Lifetime was incorrectly translated on
the French version of the GlobalProtect 6.2.1 app. |
GPC-19060 | Fixed an issue where the app Settings -> Connection tab did not
display the connection status when the app was changed from a
non-tunneled gateway to a tunneled gateway. |
GPC-19044 | Fixed an issue where, when the GlobalProtect app was installed on
Windows devices and the user changed the network from wired to
wireless within the organization, the device displayed a blue
screen. |
GPC-19023 | Fixed an issue where, when the GlobalProtect app version 5.2.13
was installed on devices running macOS, the users were unable to
connect to the Zoom application. |
GPC-19009 | Fixed an issue where, when SAML authentication was used to
authenticate to the GlobalProtect app and the user changed the
gateway to a manual gateway, the app stayed in the ‘Connecting’
stage. |
GPC-18992 | Fixed an issue where internet via WiFi connection was unavailable
for GlobalProtect users after their computer woke up from sleep
because the client WiFi adapter was unable to obtain a DHCP IP
address. This issue occurred on computers where Enforce
GlobalProtect for Network Access was enabled. |
GPC-18983 | Fixed an issue where the Central Authentication Service (CAS)
authentication did not work when the GlobalProtect app was connected
to an internal gateway and the app repeatedly opened the SAML
authentication page. |
GPC-18913 | Fixed an issue where the GlobalProtect app displayed the
connection status as ‘Not Connected’ even though the app was
connected to the internal gateway. |
GPC-18907 | Fixed an issue where the GlobalProtect app running on macOS
endpoints did not query the secondary DNS (when primary DNS is not
responding) when the domain was part of the exclude domain list
(both network and DNS). |
GPC-18854 | Fixed an issue where users were prompted twice to authenticate
using SAML authentication when used with CAS authentication and
authentication override cookie, the GlobalProtect app got stuck in
the 'Connecting' stage while trying to connect. |
GPC-18845 | Fixed an issue, where the GlobalProtect app was installed
manually and the user clicked the ‘Get Started’ button, the app
displayed the incorrect message, "Oops! Slow or No Network
Connection" instead of the actual message "Not Connected" window
where they can input their portal address. |
GPC-18828 | Fixed an issue where split tunnel CNAME records were created
before the GlobalProtect tunnel was established. |
GPC-18822 | Fixed an issue where, when the GlobalProtect app was installed on
Windows devices and the device was reset using the Microsoft
Recovery tool, the GlobalProtect app was not properly
displayed. |
GPC-18815 | Fixed an issue where the Logon button on the GlobalProtect login
screen stopped working after receiving the Microsoft Edge WebView2
runtime, 117.0.2045.36 update on the devices. |
GPC-18750 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the GlobalProtect HIP check did not detect
the Total Defense antivirus application, which caused the device to
fail the HIP check. |
GPC-18733 | Fixed an issue where when the GlobalProtect app was installed on
devices running macOS, the GlobalProtect HIP check did not detect
the Total Defense antivirus application. This caused the device to
fail the HIP check. |
GPC-18720 | Fixed an issue where the GlobalProtect app became unresponsive
when the user clicked the ESCbutton during authentication using a
hard token. |
GPC-18703 | Fixed an issue where the GlobalProtect HIP check did not detect
the Trellix Endpoint Security application, which caused the device
to fail the HIP check. |
GPC-18598 | Fixed an issue where the GlobalProtect SSO tile was selected
instead of the Windows Password tile in the Windows Login screen
even though the registry key MakeGPCPDefault was set to No. |
GPC-18384 | Fixed an issue where GlobalProtect did not connect while Netskope
was connected and vice-versa. |
GPC-18379 | Fixed an issue where, when the IP address type was set to IPv4
and IPv6, the GlobalProtect app could connect only to the manual
gateway instead of connecting to the best available gateway. |
GPC-18223 | Fixed an issue where GlobalProtect experienced a prolonged
connection time when IPv6 was disabled on Windows devices. |
GPC-18157 | Fixed an issue where the GlobalProtect app displayed the
Credential Provider language in English when the system language was
German. |
GPC-18039 | Fixed an issue where the GlobalProtect HIP check did not detect
the Definition Date correctly for the CrowdStrike application, which
caused the device to fail the HIP check. |
GPC-17640 | Fixed an issue where the GlobalProtect HIP check did not detect
the Definition Date correctly for the CrowdStrike application, which
caused the device to fail the HIP check. |
GPC-17518 | Fixed an issue where the GlobalProtect app displayed the status
as 'Connected-Internal' even when the app was not connected. |
GPC-17436 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the upload speed of the internet was reduced
after a version upgrade. |
GPC-17204 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the certificate information was not
accessible even though the GlobalProtect app had full access to the
certificate store. |
GPC-16975 | Fixed an issue where, when the GlobalProtect app was installed on
devices running macOS, the screen reader did not announce the name
of the GlobalProtect gateway when the gateway was marked with the
star symbol. |
GPC-16584 | Fixed an issue where the GlobalProtect HIP check did not detect
the CrowdStrike antivirus software correctly, causing the device to
fail the HIP check. |
GPC-15123 | Fixed an issue where users were unable to collapse the Change
Portal and Change Gateway menus using the Escape key. |
GlobalProtect App 6.2.2 Addressed Issues
The following table lists the issues that are addressed in GlobalProtect app 6.2.2
Windows and macOS.
Issue ID | Description |
---|---|
GPC-19116 | Fixed an issue where the user faced authentication issues while
the GlobalProtect app was attempting to refresh the explicit
proxy token. |
GPC-19049 | Fixed an issue where, when the GlobalProtect app was configured
in hybrid mode with internal host detection, the app failed to
connect and continued to stay in the
Connecting state when users
tried to connect using SAML authentication. |
GPC-19007 | Fixed an issue where users were unable to connect to the
GlobalProtect portal and gateway after upgrading the app version
to 6.2.1. |
GPC-19002 | Fixed an issue where the GlobalProtect app did not display the
Connect button when the user clicked
the Get Started button after the app
installation through Jamf. |
GPC-18991 | Fixed an issue where the proxy auto-configuration (PAC) files
were not restored as expected after a system reboot or when the
user disconnected the GlobalProtect app. |
GPC-18964 | Fixed an issue where the GlobalProtect tunnel got disconnected
after 10 minutes on the app versions 6.0.8 and 6.2.1, when the
GlobalProtect app was running on macOS devices and SAML
authentication was used to authenticate. |
GPC-18861 | Fixed an issue where the GlobalProtect MSI download was getting
stuck at 27%. |
GPC-18471 | Fixed an issue where, when multiple
wa_3rd_party_host_64.exe
processes persisted even after the HIP check, the GlobalProtect
app stopped working. |
GlobalProtect App 6.2.1 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-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 Settings Connection 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. |
GlobalProtect App 6.2.0 Addressed Issues
There are no addressed issues in the 6.2.0 release.