Fixed an issue where GlobalProtect disable agent messages were not reported to firewall when machine certificate authentication with full chain certificate validation was enabled.

Fixed an issue where GlobalProtect app got stuck in a connecting state when using GlobalProtect version 6.2.8-h4. The issue was seen when saml-logout and enforcer was enabled.

Fixed an issue where the GlobalProtect app experienced a continuous connect-disconnect loop when used on flights. This issue occurred because rapid network wake-ups left network interfaces in an inconsistent state, causing GlobalProtect to attempt tunnel establishment on an unstable network foundation.

Fixed an issue where the GlobalProtect app running on macOS allowed users to modify or add a new portal address after each device reboot, even when the Allow users to change portal setting was configured as No in the GlobalProtect app.

Fixed an issue where GlobalProtect apps installed on on Dell Vostro 15 3515 laptops were unable to connect to the GlobalProtect service with the following error: Could not connect to the GlobalProtect service. If the issue persists, contact your administrator.

Fixed an issue where GlobalProtect app prompted users to log in with SAML through the embedded browser even when the GlobalProtect app was already connected. This occurred when users logged off and then back onto their Cloud PC (Windows Azure PC), and closing the prompt disconnected and reconnected the VPN session.

Fixed an issue where the HIP check did not correctly detect the status of the ESET firewall on Windows hosts.

Fixed an issue where the captive portal opened in the embedded browser, but when the user tried to connect to the internet, it redirected to the default browser and was blocked.

Fixed an issue where, when GlobalProtect app was configured with Enforcer, users could bypass Enforcer restrictions by repeatedly canceling authentication prompts after logging into Windows. This occurred because the cached portal configuration, which contains Enforcer settings, was not loaded when a pre-logon tunnel failed to establish due to a quick user login. This fix ensures that the cached portal configuration is loaded as soon as PanGPA starts and PanGPS learns the username, preventing unrestricted access in scenarios where Enforcer is intended to lockdown the endpoint.

Fixed an issue where IPv6 traffic on Windows 11 24H2 did not work as expected with GlobalProtect app.

Fixed an issue where the GlobalProtect app running on macOS devices would stuck in a connecting loop indefinitely if the user did not complete authentication, requiring manual cancellation of the connection.

Fixed an issue where the GlobalProtect enforcer blocked network traffic on Windows endpoints even after the tunnel was successfully connected.

Fixed an issue where on macOS Ventura and Sequoia, GlobalProtect app versions 6.2.6-838, 6.2.7-1047, 6.2.8, and 6.3.3, manually changing the portal address using the GlobalProtect app UI would fail and revert back to the last connected portal. This issue occurred even when Allow User to Change Portal Address was enabled in the agent configuration.

Fixed an issue where GlobalProtect app version 6.2.8-183. running on macOS 15.5 was unable to accurately report the disk encryption status of FileVault, resulting in an Unknown status in HIP checks.

Fixed an issue where agent disable logs were not being logged to Gateway System Logs on the firewall. The GlobalProtect agent reset the authentication code, which falsely indicated that the gateway was not fully authenticated, and the agent did not send the message.

Fixed an issue where tool tips were not available for the Add, Edit, and Delete buttons on the GlobalProtect application's settings page on Windows devices.

Fixed an issue where the hamburger menu button was disabled in the Refresh connection screen, which made it inaccessible when using a keyboard.

Fixed an issue where, when using conditional-connect on macOS Sequoia with GlobalProtect app version 6.2.6, manually switching gateways caused the app to display a Not Connected status for approximately 10 seconds while establishing a connection to the second gateway.

Fixed an issue where loopback connection did not work when Endpoint Traffic Policy Enforcement was enabled.