Sonos Can't Add Your Music Library: Error 913, 900, 1001 and the Rest

What does Sonos error 913 mean?

This is the one people hit most. The official definition is precise: Sonos only accepts SMBv2 or SMBv3, so a share still running SMBv1 produces a 913.

• 913 from a NAS — change the SMB setting on the NAS to v2 or v3. Where that lives differs by brand, so check its own manual.
• 913 from a Mac or PC — usually because you picked "Music folder" or "Another folder or drive connected to my computer" in the desktop Sonos app. Those two options are no longer supported. Share the folder on the network yourself, then add it by its network path instead.

A network path looks like this: if the host is called MyComputer and the shared folder is Music Folder, the path is \\MyComputer\Music Folder.

Found / responding / refused — three different layers

These three get conflated constantly, and they are saying entirely different things:

• "Computer could not be found" / "Unable to connect" — Sonos cannot see the host at all. Nine times out of ten it is powered off or asleep. On Windows: Settings → System → Power & battery. On macOS: System Settings → Battery or Energy. Turn sleep off.
• "Not responding" — Sonos can see the host but the host is ignoring the request. This is almost always a firewall: security software on that machine is blocking file sharing. Go straight to the firewall; the network itself is fine.
• "Computer refused the connection" — this one has an unusual cause: two machines on the network share a hostname, and the router is sending Sonos to the wrong one. Reboot the router first; if it persists, rename one of them.
• "Access denied" — Sonos got there but permissions turned it away. Remove and re-add the library so permissions are renegotiated, check the firewall, and on a work machine ask your IT team.

What do errors 1001 and 1002 mean?

These two usually show up as "it worked and then stopped" rather than "it won't add". Sonos describes them as the host being offline or unable to hold a reliable connection. Three things to check: the host is awake, its Wi-Fi signal is strong if it is not wired, and the firewall is not interfering.

Whatever hosts the library is best on a wired connection to the router. Local library playback pulls whole files and is far less forgiving of a flaky link than streaming is.

What is error 900, and why Windows only?

A 900 points at the Windows Server service: it is trying to create the share but does not have enough stack space. The official fix is to raise IRPStackSize in the Windows Registry.

Editing the registry carries real risk and a wrong edit can damage the machine. If you are not comfortable there, don't follow a tutorial you found — contact Sonos support and let them walk you through it. This is the one fix on this page we suggest you don't do yourself.

It's added but new music doesn't show — is it broken?

This is not a fault. Sonos reads an index rather than scanning the folder live, so new tracks, changed artwork and new playlists only appear once you rebuild it.

• iOS / Android app — Settings → Music Library → Scan for New Content.
• S1 Controller — Settings → System → Music Library → Update Music Index Now.
• macOS / Windows app — the Manage menu → Update Music Library Now.

On a large library the rebuild takes several minutes. If you change things often, schedule automatic index updates and skip the manual step.

The whole thing as one table

• Error 913 → the share is on SMBv1, or you used one of the two retired desktop-app options → change the SMB version, or add by network path
• Error 900 → not enough stack for the Windows Server service → a registry edit (better left to support)
• Errors 1001 / 1002 → host offline or unstable → wake it, wire it, check the firewall
• Computer could not be found → host off or asleep → disable sleep
• Not responding → firewall blocking file sharing → configure the firewall
• Refused the connection → duplicate hostname on the network → reboot the router, or rename one host
• Access denied → sharing permissions wrong → remove and re-add, check the firewall, ask IT

Three things that prevent most of this

• Host it on a NAS, not a laptop. Laptops sleep, get carried off and switch networks; a NAS stays awake and wired. Half the errors above come down to "the host wasn't there".
• Give the host a unique name when you set it up. "Refused the connection" is nearly impossible to reason your way to, and preventing it costs one rename.
• Add by network path from the start rather than the two desktop-app shortcuts. They are no longer supported, and when they fail they report a 913 — an error code that gives no hint you picked a retired route.

One closing reminder: your local library and your streaming services are entirely separate paths. Streaming working while the library fails does not implicate the network, and the reverse holds too. Deciding which side a problem sits on saves you most of the work.

Official references

• Add your music library to Sonos (official)
• Error 913
• Error 1001 and 1002
• Use a NAS drive with Sonos
• Update your music library