GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by downgr

a0983704304 — Tue, 22 Sep 2026 09:55:32 GMT

Summary
After installing GlobalProtect App 6.3.3-h14 (6.3.3-c1121) on Windows 11 25H2, the client crashes immediately and cannot be used to log in. Reverting to the previously installed version resolves the issue. This is not isolated to one machine — it has been reproduced on multiple independent Windows 11 25H2 endpoints.

Error observed
1. GlobalProtect warning dialog (yellow triangle)
2. Followed immediately by: GlobalProtect: PanGPA.exe - Application Error
"The instruction at 0x00007FF6A567AE06 referenced memory at 0x0000000000000040. The memory could not be read."

Environment
- OS: Windows 11 25H2
- GlobalProtect version: 6.3.3-h14 (6.3.3-c1121)
- Third-party AV: None (Windows Defender only)
- Domain/MDM managed: No (standalone/customer-side endpoints)

Troubleshooting performed
1. Full uninstall of GlobalProtect App via Control Panel
2. In Device Manager, the GlobalProtect Virtual Ethernet Adapter showed "Device is disabled (Code 22)"
3. Attempted to manually enable the device — doing so immediately triggered the same PanGPA.exe crash notification, and the adapter reverted back to a disabled state
4. Uninstalled the adapter with "Delete the driver software for this device" checked
5. Enabled "Show hidden devices" and confirmed no leftover entries under Network adapters or Non-Plug and Play Drivers
6. Rebooted
7. Performed a fresh reinstall of the 6.3.3-h14 MSI
8. Crash reproduced immediately on first launch after a clean install, with the virtual adapter again left in a disabled state — ruling out leftover/corrupted files from a prior install

Reproduction scope
Confirmed on at least two independent Windows 11 25H2 machines (internal test machine and a customer endpoint).

Working workaround
Downgrading GlobalProtect to the previously installed version restores normal function (login and connection both work).

Upgrade context
The upgrade to 6.3.3-h14 was performed in response to a Palo Alto security advisory.

Requesting
1. Confirmation on whether this is a known compatibility issue between GlobalProtect 6.3.3-h14 and Windows 11 25H2
2. A recommended fixed version or ETA
3. If no fix is currently available, guidance on whether staying on the downgraded version is safe from a security standpoint, and whether it leaves the endpoint exposed to the vulnerability the upgrade was meant to address

Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do

JayGolf — Thu, 24 Sep 2026 18:54:12 GMT

Hi @a0983704304 ,

Is this for CVE-2026-0307 ?

Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do

M.Falk310364 — Tue, 29 Sep 2026 04:16:38 GMT

yes, but the version 1121 hab issues like versions before 1016. I think there are different contribution trees and the old bugs will always pop up in later versions 😞

Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do

a0983704304 — Tue, 29 Sep 2026 06:20:12 GMT

Hi, Is this for CVE-2026-0299

topic Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do in GlobalProtect Discussions

GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by downgr

Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do

Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do

Re: GlobalProtect 6.3.3-h14 (6.3.3-c1121) causes immediate PanGPA.exe crash (access violation) on Windows 11 25H2 after clean install — resolved by do