How to Clear GlobalProtect Cache on Windows Quickly
If you rely on Palo Alto Networks’ GlobalProtect VPN, you’ve probably run into the occasional hiccup where the client seems to cling to outdated settings. A stale cache can cause authentication failures, wrong split‑tunnel routes, or even endless “connecting” loops. The good news? Flushing the cache on a Windows machine is a painless, under‑two‑minute task.
Why the Cache Matters
GlobalProtect stores a handful of files locally: recent portal addresses, certificate fingerprints, and session tokens. Those nuggets speed up reconnection, but they also become a liability when the network admin changes a portal URL or tweaks the authentication method. In those moments the client keeps reaching for the old data, and you’re left staring at a stubborn login screen.
Clearing the cache essentially hits the reset button, forcing GlobalProtect to fetch fresh data the next time it starts. It’s not a cure‑all, but it’s the first line of defence before you dive into more invasive troubleshooting.
Where Windows Keeps the Cache
By default, GlobalProtect’s cache lives in the user’s profile folder. The exact path can vary depending on the version, but you’ll typically find it here:
- C:\Users\<YourUserName>\AppData\Local\PaloAltoNetworks\GlobalProtect\Cache
If your machine is part of a domain with roaming profiles, the folder might be redirected, but the “Cache” sub‑directory remains the same.
Quick GUI Method
The simplest way to wipe the cache doesn’t require any admin rights—just a few clicks.
- Right‑click the GlobalProtect icon in the system tray and choose Settings.
- Navigate to the Advanced tab.
- Click Clear Cache and confirm the prompt.
- Restart the GlobalProtect service by selecting Disconnect, then Connect again.
That’s it. The client rebuilds its cache the moment it reconnects to the portal.
Command‑Line Way (For Power Users)
If you’re comfortable with the command prompt, you can script the cleanup—handy for IT admins who need to run it across dozens of machines.
net stop PanGPSrmdir /s /q "%LOCALAPPDATA%\PaloAltoNetworks\GlobalProtect\Cache"
net start PanGPS
The first line stops the GlobalProtect service (named PanGPS), the second deletes the entire Cache folder, and the third brings the service back up. Run the snippet in an elevated command window to avoid “access denied” errors.
One‑Liner for Remote Execution
For a quick remote purge via PowerShell:
Invoke-Command -ComputerName TargetPC -ScriptBlock {Stop-Service -Name PanGPS -Force
Remove-Item "$env:LOCALAPPDATA\PaloAltoNetworks\GlobalProtect\Cache" -Recurse -Force
Start-Service -Name PanGPS
}
Replace TargetPC with the hostname or IP of the machine you’re fixing.
Verifying the Cache Is Gone
After you’ve cleared the folder, open File Explorer and paste the cache path into the address bar. If the folder appears empty, you’re good to go. A quick way to double‑check is to launch GlobalProtect and watch the log panel—there should be a line stating “Cache cleared” or “Cache file not found”.
If you still see old portal URLs in the UI, it might be a separate configuration file under C:\Program Files\PaloAltoNetworks\GlobalProtect\PanGPUI.exe.config. In that case, a full reinstall is the next logical step.
Tips, Tricks, and Common Pitfalls
- Don’t delete the entire GlobalProtect folder. Removing the Cache sub‑directory is safe; wiping the whole tree can erase client certificates.
- Make sure the GlobalProtect service is stopped before you delete files; otherwise Windows may lock the folder and your delete command will fail.
- If the client still misbehaves after clearing the cache, check the DNS resolver settings. Sometimes an outdated DNS entry points the client to a retired portal.
- On laptops with BitLocker enabled, a sudden power loss during the delete operation can trigger a recovery checkpoint. It’s rare, but worth keeping in mind.
In most environments, a fresh cache solves connectivity glitches faster than you can brew a coffee. Keep the steps handy, maybe even pin a shortcut to the batch file on your desktop, and you’ll spend less time troubleshooting and more time getting work done.
