Hi ​@Baltobernie 

Welcome to the Sonos Community!

First, please be aware that if you only now just upgraded to Windows 10, you would soon need to upgrade again, as Windows 10 will not be supported by Microsoft for much longer!

As for the issue you seem to be having, it is most strange - whether the Desktop Sonos app is open or not should make no difference as the speakers will access the files through SMB file sharing, which does not rely upon the Desktop app to work.

I suspect that this SMB setup is where the problem lies, but without seeing the behaviour directly, and without seeing logs from the speakers, I can only guess as to what is happening, and I don’t have any good guesses.

I recommend you get in touch with our technical support team who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports.

The following guide may be of help:

I hope this helps.

Hi ​@Baltobernie 

Another thought occurred to me - as you are on S1, it is possible that the S1 systems still utilise the SonosLibraryService that is installed with the desktop app - something the S2 app no longer does. If this is the case, it is possible that uninstalling the Sonos app from your Windows 10 machine and reinstalling it after, may repair the functionality of the SonosLibraryService background service.

If it does not, please call in as I suggested before.

I hope this helps.

Wonderful.

I uninstalled and reinstalled the desktop app.  Now I can’t play music from anywhere.

“Unable to connect”   “file not found”  I see the libraries and can explore them, but no play.

I will contact tech support.

This is why I never upgrade software

Did you turn on SMBv1 in Windows 10?

Yes, and then the entire library became “unable to connect”; desktop as well as tablets.

I phoned tech support, and Charles was able to resolve the issue entirely.

Thank you.