music library after latest app update

I am amazed at all the suggestions to fix Sonos incompetence. I seriously appreciate the time and effort of everyone trying to fix this.

But this is on Sonos - they either fix it or not. There are hardware and software alternatives and if necessary, goodbye Sonos. And good riddance.

The majority of people who lost their library is because Sonos no longer supports SMB v1 shares due to security reasons.  Since Sonos has no control over what your OS or NAS is using to share, how are they supposed to “fix this” if it is using SMB v1?  

I am on an iMac with Ventura 13.6.7. Should have mentioned that - sorry. Searched for “SMB” in my system files and could not find it. Not going into Terminal. I am guessing that this is a Windows solution. My point stands - time and effort on a customer’s time when this is on Sonos.

Besides a few weeks ago, a Sonos rep informed that until the iMac app is updated, my Music Library on my Mac cannot be accessed as a source. 

Sonos has created a problem that wasn’t here a few weeks ago

The lack of simple communication and reassurance from Sonos to simple questions is surprising and concerning 

Leaves me with little confidence in Sonos and lack of enthusiasm for future products or upgrades until this is resolved if it ever will be. 
 

An own goal by Sonos

I agree dropped SMB1 support likely explains a large proportion of issues experienced by those who added their music folder via a network share. But how abut those who have added their folder using the “my music folder” or “another folder or drive” options (i.e. added windows/mac folder paths)? Quite a lot of people using these options seem to be having issues as well; is it known why?

I believe they got rid of the HTTP sharing used in place of SMB v1 on PC/Macs for the same reason.

Sure did as soon as Sonos forced an upgrade on my hardware. As I said mate, you weren’t affected, that’s nice. But others were and we’ve spent hours over the phone with Sonos because our systems essentially stopped doing what we rely on them to do. Then having to find workarounds to make it work again. 

It’s because of what is mentioned here… in the notification that was sent out to the S2 App before the update to the new App.

Both ‘http’ and SMBv1 shares were removed because of the security risks posed by them.

@jgatie @Ken_Griffiths 

If that’s the reason it means the “my music folder” and “another folder or drive” options are no longer supported. Sonos should certainly do a lot more to communicate that. Whilst they have announced SMB1/HTTP support has been dropped, I doubt many know this has any relation to the above-mentioned options for adding a music folder. I personally thought it only related to the option to add a network drive.

To reduce confusion, Sonos could disable the two non-network-drive options for adding music folder in the desktop app, and they could add a note to the following support article which doesn’t currently mention anything about dropped support for “my music folder” and “another folder or drive”: https://support.sonos.com/en-us/article/add-your-music-library-to-sonos

Nobody has ever accused Sonos of being too clear in explaining anything.  I agree, they should have been ready for the onslaught, but it would appear nothing about Sonos was ready for this release, including the release itself. 

PS - As Ken said, you can still share a local library.  You just can’t share it using those two protocols.  In the case of a PC or Mac, you need to enable sharing and then set that folder to be a share because the HTTP protocol was being used before, which didn’t even require sharing to be on.