Zscaler ZPA (Private Access): How to do an emergency image reload from the boot loader
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Zscaler |
|---|---|
| Operating system | Zscaler Cloud (ZIA / ZPA / ZDX) |
| Category | Upgrade Failure |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Zscaler Support + RMA. |
An upgrade on Zscaler ZPA (Private Access) is really three jobs: stage the image, verify integrity, activate. Skipping verify is how you end up with a half-bricked unit at 2am, I have done it exactly once and learned for life.
Zscaler Cloud (ZIA / ZPA / ZDX) provides clear pre- and post-checks. `Admin Portal → Activation` before and after is the bare minimum; ideally also `Client Connector → Help → Export Logs` so Zscaler Support has a clean before/after diff.
The procedure below assumes you can take a maintenance window. If you cannot, ISSU / hitless options exist on some platforms but vary by code train. check Zscaler Cloud (ZIA / ZPA / ZDX) release notes first.
What this guide covers
Do an emergency image reload from the boot loader on a Zscaler ZPA (Private Access) (Zscaler Cloud (ZIA / ZPA / ZDX)).
Step-by-step
- At the boot loader, configure IP, gateway, TFTP server.
- Download the image.
- Set the boot variable to the new image.
- Reset to boot.
CLI / commands
# Boot recovery prompt: Client Connector logs / App Connector service
# Verify image
Admin Portal → Activation
# Upgrade
Cloud-managed; clients (Client Connector / App Connector) update via the cloud
# Save / commit
Activate (Admin Portal upper-right)
# Rollback
Admin Portal → Activation → Revert
Recovery options
- Boot loader recovery (Client Connector logs / App Connector service)
- Rollback to the previous image with
Admin Portal → Activation → Revert - Force failover to a known-good standby (HA platforms)
Frequently asked questions
Will this work on my specific Zscaler Cloud (ZIA / ZPA / ZDX) version?
The procedure reflects current Zscaler Cloud (ZIA / ZPA / ZDX) behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.
Should I open a Zscaler Support case immediately?
Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.
Where can I find the Zscaler official documentation?
https://help.zscaler.com: search the product family + feature name.
Is this procedure safe in production?
Test in a lab or maintenance window first. Capture pre-change state so you can roll back.
Related guides
Related fixes
Related guides worth a look while you sort this one out:
- Zscaler Cloud Firewall: How to do an emergency image reload from the boot loader
- Zscaler ZDX (Digital Experience): How to do an emergency image reload from the boot loader
- Zscaler ZIA (SWG/CASB/FWaaS): How to do an emergency image reload from the boot loader
- Zscaler ZPA (Private Access) partial boot then reload loop: Diagnose & Fix
- Zscaler ZPA (Private Access) stuck at boot loader prompt: Diagnose & Fix
- Zscaler ZPA (Private Access): How to recover from a corrupted image during upgrade
References
- Zscaler support portal: https://help.zscaler.com
- Zscaler knowledge base: https://help.zscaler.com
- Zscaler security advisories: https://trust.zscaler.com
- Open a case: https://help.zscaler.com/submit-ticket
Reference material, not professional advice. Validate against your specific Zscaler Cloud (ZIA / ZPA / ZDX) version and test in a non-production environment before applying.
Why this matters for your day-to-day
A Zscaler device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.
Safety + preconditions
Before any work on a Zscaler device:
- Unplug from mains for any internal-access procedure.
- Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
- Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
- Avoid moisture; never apply liquids near vents or connectors.
- If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.
How to confirm it's actually fixed
On a Zscaler device, the test is rarely "reboot and see". Use this list:
- Active reproduction: trigger the original failure path on purpose.
- Indirect reproduction: do an activity that would expose the same subsystem.
- Status indicator review: every LED / display / app status should be green.
- 24-hour soak: leave the device under normal load overnight; check the next morning.
- Telemetry check: review the device or app's diagnostic log for new error entries.
When to call Zscaler support instead
Escalate if:
- The same symptom returns within 24 hours of a clean fix.
- You see physical damage (burn marks, swollen battery, cracked PCB).
- The device is in warranty and a hardware replacement is the cheaper outcome.
- Repair requires specialised tools you don't own (alignment jigs, calibration software).
- Following the official path keeps the warranty intact, which matters more than the time spent.
More frequently asked questions
How often should I run preventive checks?
Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.
Are there safer alternatives for non-technical users?
Yes. the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.
Does this affect other devices on my network?
Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.
What if the fix returns after a reboot?
Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).
What if my model isn't exactly the same revision?
Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.