Upgrade Failure

Zscaler ZPA (Private Access): How to rollback to the previous image after a failed upgrade

Q: Where can I find the Zscaler official documentation?

https://help.zscaler.com — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

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

Rollback to the previous image after a failed upgrade on a Zscaler ZPA (Private Access) (Zscaler Cloud (ZIA / ZPA / ZDX)).

Step-by-step

Confirm there's a previous image still on flash.
Set the boot variable to that previous image.
Reboot.
Verify the version is back to the prior release.
Investigate the upgrade failure separately: do not re-attempt without root cause.

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.

All Zscaler fix guides → /zscaler/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

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.

Before you start

A few things to confirm so the Zscaler device fix goes cleanly:

Latest firmware downloaded if you're going to update.
Warranty + support contract status checked, opening sealed parts may void it.
Backup of current configuration (where applicable) taken.
Spare parts on hand if you anticipate replacement.
Adequate workspace, lighting, and time: rushing causes regressions.

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.