Very similar post to those on this thread @drewguitar: the Music Library “fix” | Sonos Community.
I’m going through exactly what you are and I also tried creating the new folder.

Note the ‘old’ Windows desktop controller App may well work if you’re using a share setup by the SonosLibraryService, but that ‘http’ method is not supported by the new Sonos App. Nor are SMBv1 shares.

The only way for a library to work successfully in the new Sonos App is to share the library using SMBv2 (or higher) - that protocol is supported by Windows 10 or higher. Maybe see the below links, which may assist to resolve the matter.

• https://support.sonos.com/en-us/article/add-your-music-library-to-sonos
• https://en.community.sonos.com/controllers%2Dand%2Dmusic%2Dservices%2D229131/adding%2Da%2Dwindows%2Dsmb%2Dshare%2Dstep%2Dby%2Dstep%2D6892060?postid=16717584#post16717584

I suggest after the share is created that the library setup is done via the new Sonos (mobile) App… note the index-scan make take a while. In my own case I have 25,697 tracks and that took a good 40 minutes to build the library index, YMMV.

@Ken_Griffiths thanks for the message, but I've been there & it doesn't work for me.

It works here with Windows 10 - make sure your PC’s network access mode is set to ‘Private’ and not ‘Public’ aswell, as mentioned in this link…

https://support.sonos.com/en-us/article/configure-windows-10-network-and-security-settings

Also make sure you’re using SMBv2 (or higher) and if necessary remove SMBv1 in the Windows control panel. See further information here… 

https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server

@Ken_Griffiths thanks again for those posts, they're much appreciated. My music is on a Synology NAS running DSM 7 and configured to use SMB 2 or 3.

I can't see that Windows settings should have any influence or am I wrong there?

No sorry I thought you were referring to a Windows shared folder as mentioned in the opening post  - or at least Windows was mentioned in that post. 

It should work with your NAS, if the SMB is anything other than version 1 - maybe try setting the min/max versions to use SMBv2 only and see if that perhaps resolves your issue.

Sorry for the misunderstanding with the Windows share.

@marner,

Maybe something in this old forum thread might prove useful too..

Hi @marner, some users have experienced issues if their NAS supports both SMBv1 and SMBv2. Try disabling SMBv1 on your NAS and see if that helps.

Thanks @Ken_Griffiths (again), @press250  I’ll take a look at the SMB permissions on the NAS.  As said, the NAS is configured for SMB 2/3 only.  Also, I keep the Windows Sonos application up to date and that has no issues playing from the music library on my NAS at all.  It’s a weird issue this one.

I understand that the music library information is held on the Sonos system and not the app or Windows desktop.  I can’t tell for sure, but it seems to me the app is having problems communicating with the Sonos system when trying to access anything in my music library.

Thanks Ken - I appreciate you response here.  I’ve tried all this multiple times - no luck.  It DOES detect my music library and will show it in the app.  Half the time, it will appear under the app in the manage music library area; however, it will not appear under the “Your Sources” part of the app.  When my music library does appear there, I can click it and see the categories such as artist, albums, etc… but when I click on any I get the “something went wrong error.” 

I’ve spent hours playing around with this, trying different things, removing it all and starting again - no luck.  So frustrated with sonos - it was SO easy to set it up and get it working properly when I purchased the system, and super easy to add new speakers.  Now, it’s a nightmare.  Went from recommending sonos to everyone who came over to actively telling people to avoid it, so disappointed!

If anyone from Sonos reads this, PLEASE bring back the old app - it worked great and I was a happy sonos customer at that time.  I feel like I purchased a car, and after a few years, the dealership came out and took my tires, leaving me with a barely functioning product. 

@drewguitar yes, that's so similar to my experience.

So are you using a Windows PC share? If so, what version of Windows are you using. Which version(s) of SMB do you have installed (add/remove Windows features in control panel) and where is the share - local hard-drive or on a connected device?

Have you setup a user on the PC and used that account with read-only permissions on the share and its subfolders/files?

Is the local network connection profile set to ‘Private’ rather than the default ‘Public’ and have you tried things with the firewall switched off temporarily, as a test?

@Ken_Griffiths - I’m using Windows 10, a folder shared on my local hard drive.  SMB 1.0 is not enabled.  SMB Direct is enabled.  I created a user called “MusicShare” with a password.  It is shared exactly as per the guides you posted above (I had previously seen those guides, but went through and did it again).  I removed my music library, then re-added it.  I have a new music library folder with only two songs in it (hoping to speed up the detection process).  I removed the music library from the desktop app as well and added it via the app. 

The network is set to private.  I did have the firewall on, so I switched that off - no changes.  Happy to post screen shots if you think that may be of help?

Let me go fire up my Windows 10 PC and I will look and see if there’s anything that might assist you. Give me a few minutes and I’ll come back to you.

@drewguitar 

Sorry for the delay. I had to wait for my PC to install an update… it’s still doing it as I type this from my tablet…

Anyhow…

In Windows powershell if you type the following to check the SMB v2 protocol is running … do you see it return ‘TRUE’ when you do that?

Get-SmbServerConfiguration | Select EnableSMB2Protocol

With the PC’s  firewall disabled (temporarily)…

When you add the path to the share are you using the computers Netbios name, or its IP address? If you’ve not tried the IP address instead (ie: Just as an example here.. //192.168.0.230/Music, or whatever the path is to your share), then perhaps give that a go. 

Also, what happens if you try with your own PC login credentials instead of MusicShare?

@drewguitar 

So on a Windows 10 PC here (all upto date) called “Ken-Com” I created a shared folder in the root of its  E:/ drive and calked it “TestShareDrewGuitar” and dropped in a couple of 10CC 320AAC tracks from my NAS box.. just as a quick test.

i just used my own PC login credentials, rather than creating a separate user account and shared the folder as ‘read only’.

I then used my Wife’s iPad and the new Sonos App (latest version). I first deleted the existing NAS local library that we use and added the path to the new share as below…

//Ken-Com/TestShareDrewGuitar

i added my login credentials alongside …and the library indexed the 10CC tracks and works fine. Screenshots attached.

So it definitely should work with Windows 10 - note I didn’t even switch off the Windows Firewall during the test here.

Just to confirm @drewguitar that the 10CC tracks I shared do play aswell. 

So it’s the speakers that access the NAS to play the files. The fact that this works when you use the desktop controller means there is no issue with SMB versions as it’s the speakers that have removed SMB1 support in their firmware. 

The issue you have with the app is communication between it and the speakers which hold the index it is trying to navigate. The NAS is not involved until the speaker is told to play a file from the index via a controller. 

If you haven’t done so already I’d avoid updating the speaker firmware as 16.3/16.3.1 have a bug with compilation albums that causes incorrect indexing (as if there weren’t enough other issues!!). If you have installed the firmware but not updated your index recently, leave it alone ...

It does say True in powershell when I do that.  I have it setup with the PC name.  I’ve had it 3 or 4 times where it was suddenly working, only to stop working within a few minutes. 

I suspect it’s a communication with the sonos server issues.  Here’s how my app often looks (screen shots below).

I’ll give a try with changing the user name / password to my PC login credentials.  As you see below, on the positive is plays sonos radio fine.  Downside is, it often has issues unless I want to just resume playing the same

A few more images here:

Ken_Griffiths:

 So a Local Account is unnecessary?  I created one anyway which changed the path to //PC Name/LocalAccountName.  Folder name was different than the Local Account name.  Makes me wonder if multiple PC folders shared to the same Local Account could all be indexed using just the above path.  Obviously no need for this, but sounds like it could work.  I’ll have to test it when I have nothing else to do.

The folder share will not change its name - the UNC path remains the same whichever user account is used - the login is anyone that has been given (at least) read-only access to the share - you can even use the ‘everyone’ option without a password, but it’s just less secure than using a user account.

Also ‘Yes’ you can add more than one shared folder to Sonos too - I’m not sure if there is a limit to how many shares can be added. 

@drewguitar,

Why is your App not displaying its Home Screen correctly in the image below? Are you using some kind of blocker, security software or VPN client that’s perhaps getting in the way of the cloud connection? Might that be a part of the issues you’re experiencing, perhaps?

@Ken_Griffiths Nope, no VPN or app blocker or anything.  Sometimes the app displays fine, other times it’s like the image above.  Example - had to close and reopen the app a few times, but here’s what it looks like now.  Has my last two radio stations and then two playlist I’ve recently done (played through the desktop app). 

The whole app is super buggy and glitchy.  Currently, under “Your Sources” it doesn’t even list my Music Library.  Before, it showed my music library but I was unable to browse past the first screen (that lists artists, albums, etc).

In all, I think I’m stuck waiting to see if sonos fixes this.  If not, I’ll eventually have to upgrade to a different eco-system.  Unfortunate as I really loved my sonos system prior to this app debacle.