Sonos Desktop does not launch Windows 2004

A recent update to Windows (on v2004) appears to have expanded the reserved ports.

Running `netsh interface ipv4 show excludedportrange protocol=tcp` on my system shows a long list of reserved  ports, including 3390-3489 and 3490-3589.

When I try to launch the Desktop controller (just downloaded v2) I get an error in the logs:

@Module:module @Message:Can't bind (port 3410)


The controller software hangs on the splash screen.

I have tried to adjust the “excluded port ranges” but these appear to be locked by Windows now.  Also I assume that there is no way to alter the ports that Sonos runs on.

Presuming this issue will shortly affect all Windows 10 users globally, does anyone know of any way around this or are we going to need a Controller software update?

TBH using a port in the 3400 range was pretty ambitious anyway since none of these ports are registered to Sonos by the looks of it:

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.

2 replies

Uninstalling the desktop controller, rebooting the PC, subsequently re-installing the desktop controller might help.


Otherwise try and update the net.framework

Userlevel 7
Badge +22

I still can’t get 2004 on any of my machines to check this myself.

Can you try my app from the Store (see profile)? If that fails I can get more diagnostics.