Issue ID | Description
--- | ---
GPC-25300 | Fixed an issue where GlobalProtect clients experienced frequent disconnections from GlobalProtect gateways. After being disconnected, users were often unable to reconnect for extended periods, and connection attempts to designated gateways, including those manually selected or identified as 'Best Available', would incorrectly redirect to other gateways.

GPC-25222

Fixed an issue where GlobalProtect clients failed to detect captive portals on public Wi-Fi networks, even when the captive portal responded with an HTTP 302 Redirect. This occurred because the GlobalProtect agent expected the HTTP response to be terminated by `\r\n\r\n` as per RFC, but some captive portals did not adhere to this, causing the agent to incorrectly report that no data was received from the captive portal server and thus fail to detect the portal.

GPC-25173 | Fixed an issue where GlobalProtect clients on macOS devices, when configured in tunnel-proxy mode, intermittently displayed an "A valid PAC file is required" notification after waking up from modern standby, particularly when the PAC file contained a placeholder statement instead of the actual EP-FQDN.
GPC-24992 | Fixed an issue where GlobalProtect users experienced significant login delays after a system reboot or shutdown, such as after a weekend. This delay was caused by a shared memory issue that disrupted communication between the GlobalProtect agent and GlobalProtect service.
GPC-23301 | Fixed an issue where, when the GlobalProtect app 6.2.7 and later, was installed on Windows 10 devices, the app deleted the predefined proxy PAC file configuration whenever the app got disconnected regardless of whether the disconnection was initiated manually or occurred automatically due to a timeout.