GlobalProtect App 4.1 Known Issues

See a list of the Known Issues in GlobalProtect™ app 4.1.

The following table includes known issues in GlobalProtect™ app 4.1.

Issue ID	Description
GPC-7765 `This issue is now resolved. See GlobalProtect App 4.1.8 Addressed Issues.`	When you configure a split tunnel to include or exclude a destination domain, the GlobalProtect app for Windows endpoints disconnects every time users establish the GlobalProtect connection and attempt to access the specified domain.
GPC-7485 `This issue is now resolved. See GlobalProtect App 4.1.10 Addressed Issues.`	Windows users receive a script error when authenticating to the GlobalProtect portal or gateway using SAML authentication.
GPC-7388	On endpoints running Android 8.0 and later releases, GlobalProtect does not reconnect automatically when switching from internal mode (corporate Wi-Fi) to external mode (LTE).
GPC-7130	On Windows endpoints, the GlobalProtect app icon intermittently disappears from the notification area (system tray) and reappears only when you halt the GlobalProtect process. Workaround : Launch the GlobalProtect app from the Start menu.
GPC-6951 `This issue is now resolved. See GlobalProtect App 4.1.6 Addressed Issues.`	GlobalProtect cannot identify and display Last Full Scan Time HIP data for Bitdefender Antivirus on macOS endpoints.
GPC-6530 `This issue is now resolved. See GlobalProtect App 4.1.5 Addressed Issues.`	The GlobalProtect app for Linux endpoints prompts end users to enter their credentials in succession despite entering correct credentials. This issue occurs after the end user attempts to connect to an alternate manual gateway configured with the User-logon (Always On) connect method.
GPC-6216	GlobalProtect cannot identify and display the Last Full Scan Time HIP data for the 360 Total Security antivirus app.
GPC-6172 `This issue is now resolved. See GlobalProtect App 4.1.2 Addressed Issues.`	Endpoints can't connect to GlobalProtect after you set the Windows System Display to Chinese and specify Chinese characters for the Username Label in the GlobalProtect app login page ( Network GlobalProtect Portals `<portal>` Agent `<agent>` Authentication ). Workaround: Specify English characters for the Username Label .
GPC-5909 `This issue is now resolved. See GlobalProtect App 4.1.1 Addressed Issues.`	If you Allow User to Disable GlobalProtect and then specify a Disable Timeout value to restrict the amount of time for which users can disable the app ( Network GlobalProtect Portals `<portal>` Agent `<agent>` App ), the GlobalProtect app for macOS endpoints does not automatically enable after reaching the Disable Timeout value. Workaround : Users must manually enable the GlobalProtect app.
GPC-5879 `This issue is now resolved. See GlobalProtect App 4.1.1 Addressed Issues.`	Endpoints running iOS 10.12 and later iOS releases on the T-Mobile LTE network cannot connect to GlobalProtect gateways that are configured with only IPv4 addresses because T-Mobile now assigns only IPv6 addresses to endpoints running iOS 10.12 and later releases. Workaround : Configure your GlobalProtect gateway with FQDNs instead of IPv4 addresses.
GPC-5416 `This issue is now resolved. See GlobalProtect App 4.1.1 Addressed Issues.`	On Windows 10 endpoints, the GlobalProtect app removes DNS suffixes due to an error in the read/rewrite function that directly modifies the DNS suffix search list in the Windows registry key.
GPC-4856	On macOS endpoints, the GlobalProtect app can’t detect the following Anti-Malware information for the HIP Match log details of the Gatekeeper security feature ( Monitor Logs HIP Match `<hip-match-log>` ): Engine Version Definition Version Date Last Scanned
GPC-3962	Proxies are disabled after you establish the GlobalProtect connection on macOS endpoints because proxy settings are not copied from the physical network adapter of the endpoint to the virtual network adapter of the endpoint, and the virtual network adapter becomes the primary adapter from which the macOS endpoint receives proxy settings.
GPC-3794	When a user first logs in to a GlobalProtect VPN that uses SAML authentication with pre-logon enabled, the tunnel rename (from pre-logon to user logon) fails, the pre-logon tunnel is disconnected, and the user is prompted to re-authenticate.