New Installer is Stuck?

It’s not clear from your post what it is that is updating. If it is your speakers, it does take some time, especially with older speakers, or bad networks. If it’s your controller, I’d kill the process, delete the file, and then download a new copy and install it. Just make sure to ‘Connect to existing system’ when prompted.

If you want additional help, you’ll need to provide more information, or call Sonos Support directly to discuss it.

One minor detail, while Sonos is still trying to its fix core functionality, it would be a lot less annoying if they changed the “check for updates” message from “no update required” to “no update available”.

Note that since the launch of the new Sonos App on May 7th, the only type of locally held music libraries supported are those shared using the SMBv2 (or higher) protocol. Those libraries that were previously shared using SMBv1 or HTTP are no longer supported due to their widely publicised security vulnerabilities. Ensure your library is shared using SMBv2 (or higher) if you search this community there are various threads on this topic. Here too are three links to help with your research on how to implement the share…

• https://support.sonos.com/en-gb/article/share-your-macos-music-folder-with-sonos
• https://support.sonos.com/en-gb/article/add-your-music-library-to-sonos
• https://youtu.be/kjhKhDuvgDY

Just spent 40 min carefully following all of these instructions, but still haven’t achieved the most basic task of linking to my local iTunes library. Given the many steps, and not entirely consistent instructions, it’s possible I’m still making some mistakes. But, this should not be so hard.

I noticed the Add New Music menu still lists My Music Folder at the top. If that’s broken, and not being fixed, why is it still there? Maybe they are working to fix it, and the best use of my time is to wait for another update?

Sharing a music folder is not really anything to do with Sonos as many Apps can use a shared folder over a network. It can be shared in a variety of ways but for PC’s running Windows 10/11 or MAC PC’s above a certain version they now automatically use SMBv2 or higher by default… which is what most Apps (including the new Sonos App use these days). There is then a case (for security reasons) to add a PC user to the share and to give them ‘read-only’ privileges as the minimum level of access needed for the share… Sonos doesn’t write to the share so that level of access is not required, although it perhaps wouldn’t matter too much if that permission was included. 

Once it’s setup then it’s a case of adding the network UNC path to the share in the Sonos App and adding in the user credentials alongside - that’s the username and password for the assigned user that you added to the shared folder - it’s the same credentials as they would use for logging onto the PC.

Some things to be aware of…

You do need to state either the PC netbios name, or the PC’s IP address, in the path to the library share within the new Sonos App. I would always recommend adding the shared folder via the (mobile) Sonos App, just so that there’s no mistake made in trying to (wrongly) setup an HTTP share, as those type of shares are no longer supported by Sonos aswell. A HTTP share is not possible via the new Sonos App.

Note a netbios name for the PC should not be longer than 15 characters and should not include:

period (.)
backslash (\)
forward slash (/)
colon (:)
asterisk (*)
question mark (?)
quotation mark (“)
less than sign (<)
greater than sign (>)
vertical bar (|)

Note too that PC Hostnames are used by DNS Servers for name resolution on the Internet and on the LAN and for that avoid using these characters in the PC Name too…

comma (,)
tilde (~)
colon (:)
exclamation point (!)
at sign (@)
number sign (#)
dollar sign ($)
percent (%)
caret (^)
ampersand (&)
apostrophe (‘)
period (.)
parentheses (())
braces ({})
underscore (_)
white space (blank)

So just to be sure things will work, I suggest the PC name does not include any of these characters, although some of the PC Hostname characters may work over the LAN as part of the Netbios name.

So a working example might be something like //MY-SERVER/MUSIC 

Where MUSIC is the name of the shared folder.

If using the IP address instead, like this (example only): //192.168.1.120/MUSIC …then I would make the IP address static (usually in the routers DHCP reservation table, but there are other methods to do that too).

Remember that the username and password assigned for access to the shared library folder needs to be a user on the PC that has read-only (ideally) permission on the MUSIC share - check the folder properties on the PC to see which user(s) and what permission they may have to access the share and its sub folders and files.

There are some other things to be aware of too…

• The network security mode for a PC must be set to ‘Private’ and not the default ‘Public’ setting.
• On a Mac, the Sonos app can only share folders on external drives formatted using the Mac OS Extended (or HFS+) file system. If the external drive is formatted in FAT32, NTFS, or ExFAT, Sonos will not be able to add a shared music folder from the drive.

As I say this is very little to do with Sonos, but these are the type of network shared folders that Sonos use.

Thanks. Lots of good info in the posts by Ken. Unfortunately, I don’t see anything in them that differs from what I’ve been doing. But, I’ll investigate further this weekend. I won’t continue with this thread, since it’s no longer on the topic of my original post.

I just tried installing the new v16.5 and got exactly the same result as I posted about last month: On my main computer (Mac w/ Ventura) the installer progress bar goes to completion, but then gets stuck. I forced it to quit and v16.4.2 opens as before and works OK.

Running the v16.5 installer on two secondary computers runs to completion as it should. The difference might be because my main device is what I used to have linked to my local iTunes folder and a directly connected external drive with a large music library as .flac. Getting these two libraries to connect is the critical essential functionality that I lost with the infamous update earlier this year.

The latest info from Sonos isn’t completely clear, but it seems to imply that they are still working on fixing these two things. If so, that might be what causes my update error, and a future update might solve everything.

Unfortunately, I’m no longer confident of that, so I’ve decided to migrate my system to BlueOS if/when they add support for SoundCloud. We’ll see which outfit gets their act together first….