Skip to main content
Contributor I
June 15, 2024

Error Code 913 Fixed

  • June 15, 2024
  • 22 replies
  • 7512 views

I’m not that computer savvy but I managed to fix my library issue. I don’t think its a Sonos issue I think its a PC issue (Windows 11). Open your music folder, right click and select properties, click on the sharing tab, click on share (not advanced sharing), in the box just type Sonos, click add, in the box below it should have added “Sonos wireless Hi Fi System, highlight that and click share. It takes a while but it finished. go back into the Sonos app and your library should pop up. Go from there. My system is working. 

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

22 replies

press250
Prodigy III
September 2, 2024

How does one get SMBv2?  I did a Google search but it’s not clear at all if one downloads it (or where to).

Hi @User966103, SMBv2 is enabled by default on Windows 11 and you can verify that by opening PowerShell and typing “Get-SmbServerConfiguration | Select EnableSMB2Protocol” (without the quotes). That command should return “True”.

While you have PowerShell open, type “Get-SmbServerConfiguration | Select EnableSMB1Protocol” and see if SMBv1 is enabled. That command should return “False”.

Lyricist III
September 20, 2024

I’m on Windows 11.  Not remotely tech savvy. Tried various things for several months and followed the advice above but still getting the Error 913 message. Finding this VERY frustrating indeed - just want to be able to listen again to the music stored in my music folder. 

Prodigy III
September 20, 2024

I’m on Windows 11.  Not remotely tech savvy. Tried various things for several months and followed the advice above but still getting the Error 913 message. Finding this VERY frustrating indeed - just want to be able to listen again to the music stored in my music folder. 

Hi - open a Windows command prompt and type:

net share 

And then post a screen shot of what you get… 👍🏻

Lyricist III
September 22, 2024

Hello again. This is the screenshot I got 

 

 

Lyricist II
September 23, 2024

I managed to fix the problem by using ChatGPT. It turns out I had an “Unknown Account” in my music folder. I went to Properties/Sharing/Advanced Sharing/Permissions and there was only one (very strange) Group/User - a long string of numbers. ChatGPT told me that was an unknown account, and I should delete it, and add the group “Everyone” and make sure it has “Read” permissions only. I also went to Properties/Sharing/Share and the unknown account was listed in there three times, so I also deleted it from there also. In summary, if you go to Properties/Sharing/Advanced Sharing/Permissions, you only need to have one Group/User, “Everyone” with “Read” permissions, and that should fix any “unsupported sharing protocol” issues associated with error code 913. Presumably, “Everyone” means any group or user or application on your computer, including Sonos.

You also need to make sure that you have SMBv1 disabled as mentioned by others in this thread.

If you still have prooblems, I recommend that you use ChatCPT.  You can provide it with the details of your computer, operating system, etc. and specific problems you experiencing, being sure to mention Sonos error 913, and you’ll get specific instructions tailored to the specific technical information you provded. It worked for me 👍

Prodigy III
September 23, 2024

Hello again. This is the screenshot I got 

 

 

Hi - so what that shows is your music folder is not shared as a network share… hence you cannot access it as Sonos will now only connect to a network share. You need to follow the procedure for making your music folder available as a network share, then do the above again to verify it’s there. 

 

https://support.sonos.com/en-gb/article/share-your-windows-music-folder-with-sonos

Lyricist II
September 23, 2024

I was thinking, how did this unknown account get into my music folder? The actual technical term for the unknown account is Security Identifier (SID) and it consists of a long string of numbers.  As my Sonos system worked fine for years before the May 2024 Sonos update, having no problem connecting with my music folder, and as numerous other Windows users have experienced the same problem with their Sonos systems suddenly not being able to connect to their music folders after the May 2024 update, I have concluded that the Sonos update caused the problem by deleting my previous Group/User and replacing it with this unknown SID.

I asked ChatGPT about this, and I got a very detailed response which describes all the possible scenarios in which the Sonos update could have corrupted our music folders. Here’s a link if you’re interested in reading the details.

https://1drv.ms/b/s!Ar4nejwyxbg2g-wDJK-3dgpXErvnhQ?e=UENokc

If you’re still unable to connect Sonos to your music folder, please check for any unusual group (SID) in your music folder and take corrective action by following the instructions from my previous post.

 

Lyricist III
September 24, 2024

Thanks for your feedback. I need to get someone more tech savvy than me to follow this through in the next few days so hopefully will have a positive outcome to report in the coming week.

 

MoPac
Headliner III
September 24, 2024

 Just tried zombiedropper’s suggestion.  Worked well on Windows 10.  Created a test folder on the desktop.  Put one album in it.  Right clicked on the test folder and chose Properties - Sharing tab - Share button. In the Share screen I typed in Sonos - clicked Add - then clicked the Share button on the bottom of the Share screen.  Back in the Properties - Share  screen I copied the Network path.  In the PC Sonos app I pasted the Network path in Music Library Setings - Add button - 3rd option Network device (ex. NAS drive).  Had to enter my login which is my account name & Password.  Indexed OK.

Thanks zombiedropper.

Lyricist III
September 29, 2024

Hi there 

Thanks for your advice. To my great relief and surprise, my partner has been able to sort this out for me and my music library is now back and working. HURRAH!!!