Palo Alto Networks PA-440: How to rollback to the previous image after a failed upgrade
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Palo Alto Networks |
|---|---|
| Operating system | PAN-OS |
| Category | Upgrade Failure |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Palo Alto TAC + RMA. |
I have run more Palo Alto Networks upgrades than I can count and the only ones that hurt are the ones where I skipped image-integrity verification. PAN-OS either ships a `verify` step or expects you to checksum the file before request system software install version 11.1.2.
On the PA-440 platform the activation phase is where you lose data-plane connectivity. Plan the change window around that window, not the full upgrade duration.
If something goes wrong, the rollback path on PAN-OS is well-trodden, but only if you saved running-config before starting. Do that now, before anything else.
What this guide covers
Rollback to the previous image after a failed upgrade on a Palo Alto Networks PA-440 (PAN-OS).
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: Maint mode
# Verify image
show system info
# Upgrade
request system software install version 11.1.2
# Save / commit
commit
# Rollback
load config from running-config-prev.xml
Recovery options
- Boot loader recovery (Maint mode)
- Rollback to the previous image with
load config from running-config-prev.xml - Force failover to a known-good standby (HA platforms)
Frequently asked questions
Will this work on my specific PAN-OS version?
The procedure reflects current PAN-OS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.
Should I open a Palo Alto TAC 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 Palo Alto Networks official documentation?
https://knowledgebase.paloaltonetworks.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
- All Palo Alto Networks fix guides → /paloalto/
- All vendor guides → /vendors/
Related fixes
Related guides worth a look while you sort this one out:
- Palo Alto Networks PA-220: How to rollback to the previous image after a failed upgrade
- Palo Alto Networks PA-450: How to rollback to the previous image after a failed upgrade
- Palo Alto Networks PA-460: How to rollback to the previous image after a failed upgrade
- Palo Alto Networks PA-440: How to do an emergency image reload from the boot loader
- Palo Alto Networks PA-440: How to perform a controlled upgrade with rollback safety net
- Palo Alto Networks PA-440: How to recover from a corrupted image during upgrade
References
- Palo Alto Networks support portal: https://support.paloaltonetworks.com
- Palo Alto Networks knowledge base: https://knowledgebase.paloaltonetworks.com
- Palo Alto Networks security advisories: https://security.paloaltonetworks.com
- Open a case: https://support.paloaltonetworks.com/Support/Index
Reference material, not professional advice. Validate against your specific PAN-OS version and test in a non-production environment before applying.
What changed recently?
Fault diagnosis on a Palo device goes faster when you map the symptom to a recent change:
- Did firmware update in the last 7 days?
- Did the network (router, ISP, VPN) change?
- Was the device moved physically?
- Did paired devices (phone, hub, app) update?
- Were any accessories swapped in or out?
The answer narrows the root cause to a manageable subset.
Before you start
A few things to confirm so the Palo 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.
Quick verification
Before you walk away from a Palo device fix, run through:
1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.
When to call Palo 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
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).
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.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.