Skip to main content
Question

Subject: Unable to add Windows 11 Music Library share — "computer could not be found" error persists after extensive troubleshooting

  • August 31, 2026
  • 3 replies
  • 15 views

I'm trying to add a shared music folder from my Windows 11 PC (hostname: DESKTOP-I92FCEI) as a Music Library source in the Sonos app, so I can play it through my Sonos Port. I consistently get an error stating the computer/path cannot be found, regardless of the exact path format used.

What I've already tried, with no success:

  • Verified the folder is properly shared on the network (share name "d", full path D:\Ma musique), with correct read permissions.
  • Confirmed my computer's network profile is set to Private (not Public).
  • Enabled Network Discovery and File/Printer Sharing under Advanced Sharing Settings.
  • Checked Windows Firewall rules — allowed "Sonos Desktop Controller" and "Sonos Library Service" for both Private and Public profiles.
  • Confirmed no third-party firewall is active (only Malwarebytes, which has no firewall component).
  • Tried both the computer name path (\DESKTOP-I92FCEI\d\Ma musique) and the direct IP path (\192.168.2.16\d\Ma musique).
  • Confirmed my Sonos Port (IP 192.168.2.13, wired via Ethernet directly to my Bell Gigahub router) is on the same subnet as my PC (192.168.2.16, connected via Wi-Fi).
  • Disabled "Allow Bell to optimize Wi-Fi throughout your home" (Whole Home Wi-Fi feature) on my Bell Gigahub, in case it was isolating wired and wireless clients.
  • Restarted both the PC and the Sonos Port multiple times after each change.
  • Enabled SMB 1.0/CIFS File Sharing Support in Windows Features and restarted.
  • Confirmed my computer's hostname is 15 characters (within Sonos's documented limit).
  • Critically: I confirmed the network share itself works perfectly — a separate computer in my living room running JRiver Media Center accesses this exact same shared folder over the network without any issue, proving the file share, permissions, and network path are all functioning correctly.

Given that every other device on my network can access the share without problems, this appears to be an issue specific to how the Sonos app/Sonos Port connects to Windows SMB shares (possibly related to SMB protocol version negotiation or signing requirements introduced in recent Windows 11 updates). I've seen similar reports from other users in the Sonos Community forum describing the same symptoms.

Could you please help investigate, or let me know if there's a known fix or workaround for this specific issue?

Thank you.

3 replies

buzz
  • August 31, 2026

Which SONOS system are you using? S1 needs SMBv:1 S2 needs SMBv:2 or 3.

The space in your folder name makes me nervous.


  • Author
  • Contributor I
  • August 31, 2026

Hi.

Thanks for this quick reply
I’m on S2. I desabled the SMBv:1, and restart. I should be on SMBv:2 or 3 now.
I also renamed my folder : \\DESKTOP-I92FCEI\d\Musique
It still doesn’t work.
Please help.

Thanks again

Alain


  • September 1, 2026

I don’t know if reviewing these will help or not:

Share your Windows music folder with Sonos

Add your music library to Sonos

If they don’t help, Sonos Support may be able to. Try submitting a diagnostic (Submit Diagnostics) within 10 minutes of getting the error. Then call Sonos Support (Sonos Support) to discuss it. They may be able to see why sonos can’t access the share. Don’t post the diagnostic number here.