Sonos Update Stuck or Failing? What to Do (and What Not to Do)

How long should you wait before calling it stuck?

Sonos updates roll out speaker by speaker, and a full system can take twenty to forty minutes — longer on older models. A progress bar that sits still for a while is normal, because it advances in stages rather than continuously. Before you decide it is stuck, give it thirty minutes, and during that window do not quit the app, do not reboot the router, and above all do not unplug anything.

① Network: a download it cannot fetch looks like a hang

The update package is downloaded from Sonos' servers, so anything blocking that path stops it at the same point every time. The usual suspects are router-level ad blocking or DNS filtering that catches the update domains, parental controls, corporate firewalls, and some "secure DNS" services. Temporarily disabling those and retrying is the fastest test in this step.

If your router uses custom DNS, temporarily switch back to the ISP default or a public resolver. A DNS failure rarely surfaces as "resolution failed" in the app; it just shows as a stalled progress bar, which is exactly why it is hard to spot.

② Only one or two failed — what now?

This is almost always a connection problem on that speaker rather than the update itself. Reboot that one first — unplug for ten seconds and plug back in, and only when the update has already stopped, never mid-update — wait for it to reappear in the app, then trigger the update again for it alone. If it sits far from the router, temporarily moving it next to the router to update and moving it back afterwards works well.

While the system sits in a partially-updated state, some features are temporarily unavailable and grouping may fail. That is expected behaviour; bringing the lagging speaker up to date restores it, and no reset is needed for this.

③ Can an older speaker be unable to update at all?

Some early models do not have the storage or memory for newer releases, and Sonos holds them at a particular version. If one speaker fails repeatedly while every other one succeeds, check whether it falls into that group — that is not a fault, there is no fix, and the options are to leave it as is or replace it. Mixing generations also raises system-split questions, which the S1 guide covers.

Confirming this before entertaining any reset saves you an entirely pointless re-setup.

④ Rule out the controller side

Sometimes what is stuck is the device in your hand, not the speaker. Open the Sonos app on a second phone or tablet and look at the same system: if the other device shows the update as complete, the first one simply failed to refresh, and reinstalling the app or clearing its cache is enough. Do not touch the speakers in that case.

It is also worth force-quitting and reopening the app, and confirming the app itself is current — an outdated controller sometimes cannot drive a newer update flow.

The order to work through

1. Wait a full thirty minutes first, doing nothing in the meantime.
2. Open the app on a second device to rule out a stale interface.
3. Temporarily disable router-level ad blocking, DNS filtering and parental controls, then retry.
4. If only some speakers failed, reboot those (the update has already stopped by now) and update them individually.
5. Move the stubborn one next to the router, update it there, then move it back.
6. Confirm it is not an older model held back by storage limits — if it is, stop here.
7. If it still fails, contact Sonos support rather than resetting yourself.

Things broke right after the update — did it cause them?

If the update succeeded and dropouts, grouping failures or a broken music service appeared afterwards, it is rarely that the update "broke" something — more often the new version changed what it needs from the network, or how it behaves on it. The most common case is simple: the speaker rebooted during the update, picked up a different IP, and your existing address reservations did not cover it. Reserve an address for each speaker and observe; that usually settles it.

If one music service stopped working after an update, re-authorising that service in the Sonos app is usually all it needs — not a rebuild of the whole system.

Which two things should you never do?

One: unplugging mid-update. Cutting power while firmware is being written is the action that genuinely leaves a device unable to boot. A stalled update looks alarming but is still a safe state; a power cut is not. Two: factory resetting before you know the cause. A reset wipes groups, favourites and room settings, while none of the actual causes — network, storage, controller — are addressed by it. You will simply have to run the same update again on the same network afterwards.

If you have exhausted every step and it still fails, contacting Sonos support is far safer than resetting on your own — they can see the device-side update logs, and you cannot.

Official references

• Release notes — Sonos system updates
• Sonos app version compatibility
• Reboot Sonos products
• Contact Sonos support