Skip to main content

The Sonos Windows is taking 30 seconds to startup everytime I launch it. It goes through a few screens such as System not available and then finally completes successfully. Any sugestions for what is causing the issue? Sonos App 16.5, Windows 11 Pro 22H2

It does seem to be slowly going downhill, with startup pages claiming no system found, or finding my S1 devices and demanding they get updated to S2 (which they can’t).

I should perhaps recommend my Windows app… (see profile).


Hi ​@jayhamlin 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with the Windows Desktop Controller not opening as quickly as it should.

My first assumption would be that this is due to the controller not getting responses from the speakers as quickly as it should do.

Please reboot your router by switching it off for at least 30 seconds. If that does not help matters, 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.

I hope this helps.


Thanks. I’ll try the router reboot and then follow-up with support if needed.

 

Update: I rebooted the modem and router and it is much more responsive. I’m surprised it was that easy. Thanks again.


You might find a bit more stability if you assign all Sonos a static/reserved IP address from your router’s DHCP Settings page, usually painless to do.

Power down all Sonos once done, reboot the router and then power up Sonos and you will have one potential problem eliminated.

You might look at your WiFi signal levels and try the WiFi FAQ tweaks too.

https://support.sonos.com/en-us/article/improve-your-sonos-products-wifi-connection


Thanks for the IP address suggestion. I’ll keep it in mind.

I have a great wifi setup (Unifi UDMP and 5 AP’s). Wifi has never been an issue, but thanks for the note.


Just because you have good WiFi you shouldn’t assume Sonos is getting a good connection to it.

My good WiFi, also from Ubiquity, wasn’t able to connect well with one of my Sonos, no real fault of either but local non-Sonos interference. In another instance (well twice because I’m a slow learner) it was self-interference where two Sonos were blocking each other.

There are a couple good posts around on using Sonos over Unify that you might want to look into too.


Hi ​@jayhamlin 

Update: I rebooted the modem and router and it is much more responsive. I’m surprised it was that easy. Thanks again.

Glad to hear that helped! Thanks for updating the thread.

I personally recommend that everyone reboot their routers 4 - 6 times a year whether they encounter any issues or not - consider it similar to an oil change, in that it just makes things a bit more reliable. 

@Stanley_4’s sound advice of reserving IP addresses for devices commonly on your network can definitely help with reducing the need to reboot the router, and reduce the issues seen due to that need, but unless you paid a lot of money for the router, it will still need occasional reboots to keep it ticking over nicely.

I hope this helps.


I paid a lot of money for my router and while it needs less reboots than my consumer one it still gets a couple per year with firmware updates.

I’d consider doing one if your up-time is over 6 months. Partly Sonos related and partly just to make sure the router can survive a reboot.


Reply