The Sonos app will not start in Windows 10 version 2004

FWIW the desktop controller can only connect to an existing system. 

Make sure your network is set to private

https://www.catenalogic.com/products/zonos/set-network-private/

did the trick for me

The Library service is shared between both versions (though it lives in the V2 directory), so I would suggest:

1. uninstall both apps
2. Reboot the PC
3. Install S2 and see if that starts up at least

I don’t have 2004 on any of my machines yet. One only just got 1909 for some reason.

Or you could use a third-party app Darryl :-)

I just took the final update (...745) and both apps still work fine for me. Sonos need to debug this on someone’s machine that isn’t so happy.

I had a recent .net update from microsoft but that does not change my problem.  I have done some further reading of the error log and I notice that in addition to the exception message on the image data I also get this failure message.

<ApplicationData>@Module:svcmanifest @Message:Failed to read service manifest file C:\ProgramData\SonosV2,_Inc\jffs/manifests/9-manifest_8.json. Read 370 out of 386 bytes

Looking at this json file and it is.

{
    "schemaVersion": "1.0",
    "endpoints": [{
        "type": "browse",
        "uri": "https://spotify-v5.ws.sonos.com/v1/browse"
    }],
    "presentationMap": {
        "uri": "https://sonos-pmap.ws.sonos.com/spotify_pmap.24.xml",
        "version": 29
    },
    "strings": {
        "uri": "https://spotify-static.ws.sonos.com/strings.27.xml",
        "version": 29
    },
    "accountTiers": [ "free", "paidPremium" ]
}

The manifest failure is unrelated to your problem. If you have trouble browsing Spotify then you can blame the manifest. However it could indicate a more general networking problem I guess.

That callstack is very interesting, it is crashing trying to load the icon on one of your music services, while it is building the Search popup menu. Reproducing this might not depend on the .NET version at all, it probably depends on which music services you are subscribed to.

So, can you remember which music services you are subscribed to? Run my app (see profile) if you need to refresh your memory (though mine might crash also as it reads those same icons for the same reason).

Using the iOS app I can see the following services

Amazon Music
Bandcamp
SoundCloud
Spotify

Sonos Radio

TuneIn

Nothing unusual.

Thanks for your response Jean, all of these settings were correct but the problem persisted. I have resorted to uninstalling the Windows Update and the controller works fine. Hopefully future updates from Microsoft will not replicate the issue.

Thanks for the suggestion tried this.  Unfortunately no change.

Name="Sonos" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="Sonos" ProcessID="20976" ThreadID="3" /><Channel/><Computer>TIM-HP</Computer></System><ApplicationData><TraceData><DataItem>Unhandled exception caught at the dispatcher. Dispatcher:</DataItem><DataItem>System.OverflowException: The image data generated an overflow during processing. ---&gt; System.ArithmeticException: Overflow or underflow in the arithmetic operation.&#xD;&#xA;   --- End of inner exception stack trace ---&#xD;&#xA;   at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()&#xD;&#xA;   at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(BitmapSource source, ColorContext sourceColorContext, ColorContext destinationColorContext, PixelFormat format)&#xD;&#xA;   at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()&#xD;&#xA;   at System.Windows.Media.Imaging.BitmapImage.EndInit()&#xD;&#xA;   at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.ArtworkDataEventSink.GenerateEventArgs(SCIArtworkData sender)&#xD;&#xA;   at Sonos.Controller.Desktop.SCLib.EventWrapper`2.OnEvent(TSender sender)&#xD;&#xA;   at Sonos.Controller.Desktop.SCLib.EventSink`1.dispatchEvent(SCIObj pSender, String sEventID)&#xD;&#xA;   at Sonos.SCLib.Interop.SCIEventSinkSwigBase.SwigDirectordispatchEvent(IntPtr pSender, String sEventID)&#xD;&#xA;   at Sonos.SCLib.Interop.sclibPINVOKE.SCILibrary_SCLibUIThreadCallback(HandleRef jarg1)&#xD;&#xA;   at Sonos.SCLib.Interop.SCILibrary.SCLibUIThreadCallback()&#xD;&#xA;   at Sonos.Controller.Desktop.SCLib.LibraryManager.&lt;CallUIThread&gt;b__c()&#xD;&#xA;   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)&#xD;&#xA;   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)</DataItem></TraceData></ApplicationData></E2ETraceEvent><E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent"><System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system"><EventID>0</EventID><Type>3</Type><SubType Name="Critical">0</SubType><Level>1</Level><TimeCreated SystemTime="2020-08-18T13:07:34.4166252Z" /><Source Name="Sonos" /><Correlation

It appears that this Windows Update solves the above issue:

Sonos, you are off the hook. :-)

Just to add +1 to this - I updated to v2004 Windows (which is, after all, a feature update so gets forced out to all W10 PCs) and the Sonos S1 application now won’t work. I added the reg keys for TLS1.1 and still had no luck. 

I did however download the latest Sonos S1 application (v1122) and it appears to work. 

I may have stumbled upon the solution. While searching the Windows System Event logs for anything related to Sonos, I noticed a lot of SCHANNEL errors that mentioned TLS credential failure. So, I went off to check the registry for SCHANNEL protocol settings. Here, I bolstered things a bit, as is recommended practice. However, there was a bit of twist.

First, I explicitly opened TLS 1.1 by adding some registry DWORDS.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client

For TLS 1.2, I configured the following:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client

Originally, for TLS 1.1, I had Enabled=0x00000001. However, upon rebooting my machine (for these protocols to take effect), my Sonos agains stalled at startup of the app. Bloody hell. BTW, I unstalled it, deleted the cache folder and reinstalled. No joy.

Then I recalled that Windows 10 had started blocking TLS 1.1 and older from about end of March 2020 - exactly when 2004 began its roll-out. So, I blocked TLS 1.1 (as shown in the above snippet) and rebooted. What do you know! Sonos resumed working again.

TLS = Transport Layer Security, and 1.2 is the latest broadly adopted version of the protocol (there is a 1.3 version, but .NET 4.8 in Windows 10 2004 and apps have not broadly adopted it yet). All internet comms over HTTP/1.1 and HTTP/2 do encryption of secure network data transfer using TLS protocols 1.0, 1.1, or 1.2, with the help of compatible encryption cypher suites. Sonos, too. I suspect, if TLS 1.1 is left open, Sonos tries it and somewhere in the Windows layers it gets wacked. Block TLS 1.1, and Sonos uses 1.2, which glides through. At least, that is my impression based on my observations.

I’ll keep an eye on my Sonos app following further reboots of my OS, since in the past Sonos S2 would work initially, then stop working after a reboot or two.

BTW, the SCHANNEL error events still appear in my Windows Event log, so they per sé are not connected to the above Sonos issue and my resolution. But their presence have led me onto the above TLS experiment and outcomes.