Skip to main content
Answered

readding a shared folder

  • December 27, 2025
  • 9 replies
  • 68 views

I downloaded the Sonos app on my desktop Windows 11 PC, and successfully added a music folder, which is on a secondary internal hard disk of the computer. Windows sees the disk as D:

I then noticed that the Sonos app was offering an update, and I installed it.

After that, the shared folders on both my Windows PCs were showing as inaccessable. 

I removed the shared folder on my desktop, and then I was unable to re-add it. I tried various ways, and got various errors. Sometimes it would re-add, but then it became inaccessable during the indexing process.

What to do?

Best answer by buzz

You could have issues with the size of the meta data, file count, or odd characters in the metadata. A fixed amount of space is allocated for the library index, along with a 65K absolute track limit. If either limit is reached or a stray character is encountered, the index is terminated at that point.

File size shouldn’t be an issue unless a share size limit has been reached. For example it would be acceptable to the indexer if a whole CD or multi-CD library is ripped as a single file.

9 replies

Stanley_4
  • Lead Maestro
  • December 27, 2025

As the update process may confuse Sonos, my first troubleshooting step would be a network refresh. Power down all Sonos, reboot router, controller and just to be safe the sharing computer. Power up the router and let it stabilize, then the computer and your controller followed by the Sonos devices.


  • Author
  • Contributor I
  • December 27, 2025

I added it, but after a few minutes of indexing, I get the error: “MYFOLDERNAME is no longer available”


buzz
  • December 27, 2025

Have you recently also updated W11? I suspect a SONOS issue. In the last few days there have been a few similar complaints. I suggest that you submit a diagnostic and contact SONOS phone support. This will move the issue higher in the resolution queue at SONOS.

You might try uninstalling and reinstalling the SONOS controller. Don’t Factory Reset any SONOS units.


  • Author
  • Contributor I
  • December 27, 2025

After experimenting a little, I think the problem is when the folder to be added has too many GBs, or the files in it are very heavy, or it just has a lot of files.


Forum|alt.badge.img+4
  • Prodigy I
  • December 27, 2025

@shmu26 Have a read through this thread, the specific thread issue and the problem outlined in my comment, although not identical to yours, I would say are definitely similar/related and relevant... In short, it may well just solve itself!

https://en.community.sonos.com/ask-a-question-228987/failure-reading-files-from-nas-6932473


buzz
  • Answer
  • December 27, 2025

You could have issues with the size of the meta data, file count, or odd characters in the metadata. A fixed amount of space is allocated for the library index, along with a 65K absolute track limit. If either limit is reached or a stray character is encountered, the index is terminated at that point.

File size shouldn’t be an issue unless a share size limit has been reached. For example it would be acceptable to the indexer if a whole CD or multi-CD library is ripped as a single file.


Stanley_4
  • Lead Maestro
  • December 27, 2025

If you submit a diagnostic within a few minutes of the error the Sonos folks can pull it up if you call them, and tell you what is going wrong.


  • Author
  • Contributor I
  • December 28, 2025

I downgraded to version 17.2.1

and it’s going a lot better. 

As long as the file names don’t have special characters, it works.


Stanley_4
  • Lead Maestro
  • December 28, 2025

Special character issues are common when using SMB, there is an add-on to your server to alter them (when shared) to something acceptable.

Drawing a blank, I'll post this and go look and then add an a link.

And found it.

Scroll down to the Oct 23 update.

https://stan-miller.livejournal.com/650.html