Disclosure: this is a troubleshooting guide. It contains no product recommendations and no affiliate links — it exists to fix your problem, not to sell you anything.
Sonos updates have a reputation, and it’s not an unfair one. The redesigned Sonos app (v80.x) arrived with missing features and broken flows — surround removal failing, speaker setup crashing mid-wizard, queue management gutted — and generated “DO NOT UPDATE” threads across the community. Sonos has acknowledged the gaps publicly and shipped fixes since, but update anxiety is now a permanent part of Sonos ownership. This guide gives you the safe update protocol, the recovery steps when an update fails, and the honest triage for deciding whether to wait or act.
Last verified: October 2026. No lab testing was performed for this article. The update history is drawn from Sonos’s public statements and community reporting (r/sonos, Sonos Community forum); recovery steps come from Sonos’s support documentation.
Why Sonos updates fail
It helps to know what’s actually going wrong, because “the update failed” covers several different failures:
- Network interruption mid-update. The most common cause. A speaker downloading firmware over a flaky WiFi connection — the same dropouts covered in our app problems guide — can stall or corrupt the download. The speaker usually recovers on its own, but not always cleanly.
- App and speaker firmware out of sync. The Sonos app and the speaker firmware are separate updates. Updating one without the other — or the app auto-updating while the speakers sit on old firmware — produces the classic “everything was fine until the app updated” symptom set: features missing, settings unreachable, Trueplay gone from the menu.
- Staged rollouts. Sonos rolls updates out gradually. Your phone’s app store may offer the new app days before your speakers are offered the matching firmware, or vice versa. During the gap, things break in confusing ways that look like bugs but are really version skew.
- Genuine bad releases. It happens. The v80.x app launch is the canonical example: a rewrite that shipped with real regressions, acknowledged by Sonos in a public AMA, with feature parity still being restored update by update. Sometimes the correct action is genuinely to wait.
The safe update protocol (before you tap “update”)
Adopt this and most update pain disappears:
- Don’t update before you need the system. Hosting a movie night tonight? Updating this afternoon is how horror stories start. Update when you have an hour of slack, not an hour before guests arrive.
- Update the app first, then the speakers — or at minimum, check that both are on compatible versions afterward. If the app store offers a Sonos update, open the Sonos app after installing it and check for speaker firmware updates (Settings → System → System Updates → Check for Updates).
- Do it on stable network. Phone on the same WiFi as the speakers, speakers not mid-dropout. If your system has been flaky, fix the network first — an update over a bad connection is the top cause of failed updates.
- Don’t interrupt it. Once a speaker starts updating, leave it alone: don’t unplug it, don’t reboot the router, don’t force-close the app. Most “bricked” reports are interrupted updates, not bad firmware.
- One speaker at a time, mentally. The system updates speakers sequentially. A speaker that looks “stuck” may just be waiting its turn. Give it 15–20 minutes before declaring failure.
- Wait a few days on major app rewrites. Point releases (bug fixes) are safe to take promptly. Major redesigns — the v80.x lesson — are worth watching for a few days while the community reports back. There is no prize for updating first.
Failed-update recovery, in order
If an update fails or a speaker misbehaves afterward, work through these before anything drastic:
Step 1: Check what actually updated
Open the Sonos app → Settings → System → System Updates, and check each speaker’s firmware version against what Sonos lists as current. Often the “failure” is one speaker that didn’t get the update while the rest did — and the fix is simply running the update again for that speaker, not troubleshooting the whole system.
Step 2: Reboot the affected speaker (not a factory reset)
Unplug the speaker for 10 seconds, plug it back in, and let it fully rejoin the system (solid white light, visible in the app). Then check for updates again. This resolves the large class of “update downloaded but didn’t apply cleanly” issues. Note: this is a reboot, not a factory reset — your settings, groups, and Trueplay tuning survive it.
Step 3: Reboot the network, then retry
If the speaker can’t reach the update servers reliably, the download keeps failing. Reboot the router, wait for it to come fully online, reboot the speaker, then retry the update. If your system has chronic WiFi issues, temporarily wire the updating speaker to the router with ethernet for the duration of the update — the most reliable download path there is.
Step 4: The app reset (for app-side breakage)
When the app misbehaves after updating — missing features, crashing wizards, speakers not appearing — the community’s most-reported fix is resetting the app itself: Account → App Preferences → Reset App, then sign back in and let it rediscover the system. This is different from resetting speakers, and far less destructive. Our app problems guide covers this in full, including when a phone reboot needs to come first.
Step 5: Re-add the speaker (the last resort before support)
If a single speaker is stuck — won’t update, won’t play, shows errors — remove it from the system and add it back as new. This is disruptive (you’ll redo its room settings and Trueplay tuning — see our Trueplay fix guide if tuning misbehaves afterward), so it’s genuinely the last self-help step. After re-adding, run the update immediately before reconfiguring anything else.
“The update bricked my speaker” — the triage
True bricking — a speaker permanently dead from firmware — is extremely rare. What’s usually reported as bricking is one of these:
- Interrupted update: power cut or unplug mid-update. Often recoverable: leave the speaker plugged in and powered for 30+ minutes (some units resume the update on their own), then try the reboot-and-retry sequence above.
- Speaker stuck in setup mode: flashing green light, app can’t find it. This is a network discovery failure, not a dead speaker — check that the phone is on the same network and work through the discovery steps in the app problems guide.
- Features missing after an app update: not bricking at all — it’s the app/speaker version skew described above, or a genuine regression in a new app version. Check for a follow-up app update; Sonos has been shipping catch-up releases steadily.
- Actually dead hardware: no lights, no response to power, after 30 minutes plugged in and a known-good outlet/cable. That’s the one case for Sonos support or a warranty claim — and it’s a hardware failure that happened to coincide with an update, not firmware damage.
When to wait vs when to act
Wait when: a major app redesign just dropped and the community is reporting missing features; Sonos has acknowledged issues and promised a fix; your system works fine on the current version and nothing you need requires the update. There is no security emergency in delaying a Sonos feature update by a week.
Act when: the update fixes something you need (a feature you use, a bug you’re hitting); a speaker is genuinely stuck mid-update; version skew is breaking functionality between your app and speakers. And always act on speaker firmware updates eventually — unlike the app, speaker firmware occasionally carries genuine fixes for audio behavior.
The v80.x saga taught the community a durable lesson: Sonos updates are not iPhone updates. The ecosystem is a phone app plus a dozen embedded devices plus your network, and all three have to agree. A little patience at update time is the cheapest troubleshooting there is.
Frequently asked questions
Should I enable automatic updates?
For speaker firmware, generally yes — unattended overnight updates avoid the version-skew problem. For the phone app, consider manual updates so a major redesign doesn’t land the morning of your dinner party. You can always update manually when you’re ready.
The app updated and now Trueplay is gone. What happened?
Usually one of two things: the speakers haven’t received the matching firmware yet (check for speaker updates), or the new app moved the setting. Trueplay issues have their own guide — Sonos Trueplay not working — including the microphone-permission gotcha the new app stopped warning about.
How long should a speaker update take?
Typically 5–15 minutes per speaker, sequential across the system. A full multi-speaker system can take the better part of an hour. If a single speaker shows no progress for 30+ minutes, that’s stuck — reboot it and retry.
Can I roll back a Sonos update?
Officially, no — Sonos doesn’t offer firmware downgrades for speakers, and app downgrades via sideloading are unsupported and risky. This is why the “wait a few days on major releases” rule exists: the only safe rollback is not updating in the first place.
My old speaker can’t update anymore. Is it obsolete?
Possibly — this is the S1/S2 split. S1-only products (Play:5 Gen 1, Playbar, original Play:1 era hardware) can’t run the S2 firmware that newer products require. Our compatibility matrix covers exactly which products work together and what the S1/S2 wall means for mixed systems.
Honest limits
We don’t have insider access to Sonos’s release process — the history here is reconstructed from Sonos’s public statements and community reporting, and any individual update may behave differently than the pattern. If you’ve worked through the recovery steps and a speaker is still stuck, submit a diagnostic and contact Sonos support rather than repeating the same steps louder. Building out a system? The system planning guide covers update-friendly network setups from the start. Last verified: October 2026.
