Upgrade Failure

Sophos XGS 107: How to verify image integrity before activating

Q: Where can I find the Sophos official documentation?

https://support.sophos.com/support/s/ — 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	Sophos
Operating system	SFOS (Sophos Firewall OS)
Category	Upgrade Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Sophos Support + RMA.

Image upgrades on Sophos platforms have one cardinal rule: verify the running image first. `system version (CLI)` on SFOS (Sophos Firewall OS) is the single most useful command in a change window because it tells you exactly what you are rolling back to if something breaks.

Across the XGS 87 family the upgrade syntax is `system firmware-upload type=usb`: pay attention to the activation step because SFOS (Sophos Firewall OS) treats download and activate as separate transactions. Forgetting the activation step is the single most common reason an 'upgrade' silently does nothing.

Sophos Support expects you to capture pre-upgrade state and have a console session open during the change window. Anything less is a support-case waste of time if it goes sideways.

What this guide covers

Verify image integrity before activating on a Sophos XGS 107 (SFOS (Sophos Firewall OS)).

Step-by-step

Copy the image to local flash.
Run the vendor checksum / md5 command.
Compare against the checksum published on the vendor portal.
If mismatched, the image is corrupt, re-download.

CLI / commands

# Boot recovery prompt: Recovery console (USB)

# Verify image
system version (CLI)

# Upgrade
system firmware-upload type=usb

# Save / commit
(auto-saves in Web UI; CLI changes persist)

# Rollback
system backup-restore restore

Recovery options

Boot loader recovery (Recovery console (USB))
Rollback to the previous image with system backup-restore restore
Force failover to a known-good standby (HA platforms)

Frequently asked questions

Will this work on my specific SFOS (Sophos Firewall OS) version?

The procedure reflects current SFOS (Sophos Firewall OS) behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.

Should I open a Sophos 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 Sophos official documentation?

https://support.sophos.com/support/s/, 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 Sophos fix guides → /sophos/
All vendor guides → /vendors/

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

References

Sophos support portal: https://support.sophos.com
Sophos knowledge base: https://support.sophos.com/support/s/
Sophos security advisories: https://www.sophos.com/en-us/security-advisories
Open a case: https://secure2.sophos.com/en-us/support.aspx

Reference material, not professional advice. Validate against your specific SFOS (Sophos Firewall OS) version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a Sophos 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.

Safety + preconditions

Before any work on a Sophos 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.

Quick verification

Before you walk away from a Sophos 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 Sophos 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.