The Sonos app will not start in Windows 10 version 2004. The banner appears and the Sonos.exe process is listed in TaskManager. I’m not sure but I don’t think it worked since installing Windows 2004. I uninstalled the app and then installed the new S1 Sonos app but it does the same thing. Other Windows 10 version 2004 computers are able to run the app.
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.
Page 1 / 2
The network is set to private.
The app starts and shows the screen and what is currently playing (I have to use my iPhone to play anything on Sonos) and then it dies.
Oh - that was not my problem. I installed S1 on a newly setup Win 10 - 2004 computer and it said it was connected to my system, but then it failed. My network was set to public. Changing it on one pc fixed it on another one too! Have used my Pixel to mange Sonos until now.
The network is set to private.
The app starts and shows the screen and what is currently playing (I have to use my iPhone to play anything on Sonos) and then it dies.
Make sure your network is set to private
https://www.catenalogic.com/products/zonos/set-network-private/
did the trick for me
Userlevel 7
+23
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.
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" ]
}
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 must admit when it gets to the Registry I am a little lost.
I do not seem to have the same set up as you have in Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols - see my set up below.
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. ---> System.ArithmeticException: Overflow or underflow in the arithmetic operation.
 --- End of inner exception stack trace ---
 at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()
 at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(BitmapSource source, ColorContext sourceColorContext, ColorContext destinationColorContext, PixelFormat format)
 at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
 at System.Windows.Media.Imaging.BitmapImage.EndInit()
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.ArtworkDataEventSink.GenerateEventArgs(SCIArtworkData sender)
 at Sonos.Controller.Desktop.SCLib.EventWrapper`2.OnEvent(TSender sender)
 at Sonos.Controller.Desktop.SCLib.EventSink`1.dispatchEvent(SCIObj pSender, String sEventID)
 at Sonos.SCLib.Interop.SCIEventSinkSwigBase.SwigDirectordispatchEvent(IntPtr pSender, String sEventID)
 at Sonos.SCLib.Interop.sclibPINVOKE.SCILibrary_SCLibUIThreadCallback(HandleRef jarg1)
 at Sonos.SCLib.Interop.SCILibrary.SCLibUIThreadCallback()
 at Sonos.Controller.Desktop.SCLib.LibraryManager.<CallUIThread>b__c()
 at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
 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
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.
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. ---> System.ArithmeticException: Overflow or underflow in the arithmetic operation.
 --- End of inner exception stack trace ---
 at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()
 at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(BitmapSource source, ColorContext sourceColorContext, ColorContext destinationColorContext, PixelFormat format)
 at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
 at System.Windows.Media.Imaging.BitmapImage.EndInit()
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.ArtworkDataEventSink.GenerateEventArgs(SCIArtworkData sender)
 at Sonos.Controller.Desktop.SCLib.EventWrapper`2.OnEvent(TSender sender)
 at Sonos.Controller.Desktop.SCLib.EventSink`1.dispatchEvent(SCIObj pSender, String sEventID)
 at Sonos.SCLib.Interop.SCIEventSinkSwigBase.SwigDirectordispatchEvent(IntPtr pSender, String sEventID)
 at Sonos.SCLib.Interop.sclibPINVOKE.SCILibrary_SCLibUIThreadCallback(HandleRef jarg1)
 at Sonos.SCLib.Interop.SCILibrary.SCLibUIThreadCallback()
 at Sonos.Controller.Desktop.SCLib.LibraryManager.<CallUIThread>b__c()
 at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
 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
Userlevel 7
+23
Might be a corrupt bitmap in your cache I guess - delete the contents of C:\ProgramData\Sonos,_Inc\cache
Using the iOS app I can see the following services
Amazon Music
Bandcamp
SoundCloud
Spotify
Sonos Radio
TuneIn
Nothing unusual.
Userlevel 7
+23
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).
I have both of those installed, I have deleted the app, restarted and reinstalled the app but I am still getting this message in the XML log.
/><Execution ProcessName="Sonos" ProcessID="19564" 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. ---> System.ArithmeticException: Overflow or underflow in the arithmetic operation.
 --- End of inner exception stack trace ---
 at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()
 at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(BitmapSource source, ColorContext sourceColorContext, ColorContext destinationColorContext, PixelFormat format)
 at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
 at System.Windows.Media.Imaging.BitmapImage.EndInit()
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.ArtworkDataEventSink.GenerateEventArgs(SCIArtworkData sender)
 at Sonos.Controller.Desktop.SCLib.EventWrapper`2.OnEvent(TSender sender, EventHandler`1 handler)
 at Sonos.Controller.Desktop.SCLib.EventWrapper`2.add_Event(EventHandler`1 value)
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.AbstractArtItem.Initialize(ArtworkDataEventSink artworkData, ImageSource initialArtwork, SCAlbumArtType artType, String artUrl)
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.BrowseArtItem.Initialize(ArtworkDataEventSink artworkData, ImageSource placeholderArtwork, String trackNumber, Boolean holdSpace, Boolean useSmallerSize, SCAlbumArtType artType, String artUrl)
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.ArtworkFinder.GetBrowseArtItem(ArtworkDataEventSink artworkData, ImageSource placeholderArtwork, String trackNumber, Boolean holdSpace, Boolean useSmallerSize, SCAlbumArtType artType, String artUrl)
 at Sonos.Controller.Desktop.SCLib.ViewModel.Artwork.ArtworkFinder.GenerateBrowseArtItem(FrameworkElement resourceFinder, String url, SCAlbumArtType artType, SCLogoArtSize logoSize, Boolean isInfoView)
 at Sonos.Controller.Desktop.SCLib.ViewModel.SearchProvider..ctor(SCISearchable searchProvider, FrameworkElement artworkFinder)
 at Sonos.Controller.Desktop.SCLib.ViewModel.SearchViewModel.SearchProvidersChanged_Event(Object sender, HouseholdSearchProviderEventArgs e)
 at Sonos.Controller.Desktop.SCLib.EventWrapper`2.OnEvent(TSender sender)
 at Sonos.Controller.Desktop.SCLib.EventSink`1.dispatchEvent(SCIObj pSender, String sEventID)
 at Sonos.SCLib.Interop.SCIEventSinkSwigBase.SwigDirectordispatchEvent(IntPtr pSender, String sEventID)
 at Sonos.SCLib.Interop.sclibPINVOKE.SCILibrary_SCLibUIThreadCallback(HandleRef jarg1)
 at Sonos.SCLib.Interop.SCILibrary.SCLibUIThreadCallback()
 at Sonos.Controller.Desktop.SCLib.LibraryManager.<CallUIThread>b__c()
 at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
 at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object
Unfortunately it isn’t working for me - I still get the same arithmetic overflow processing image data.
Hello
I do not understand - processing image data? What image data? Explain your issue reproduction steps, please.
Anyway, there were two Windows Updates on the same date stamp:
https://support.microsoft.com/en-us/help/4569745/kb4569745-cumulative-update-for-net-framework
https://support.microsoft.com/en-us/help/4566782/windows-10-update-kb4566782
Have you received and installed both of the above?
Regards
JP
Unfortunately it isn’t working for me - I still get the same arithmetic overflow processing image data.
The Library service is shared between both versions (though it lives in the V2 directory), so I would suggest:
- uninstall both apps
- Reboot the PC
- 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 can confirm that the above recipe resolves the issue at hand. I run Windows 10 2004. I used to have Sonos S1 app and added S2 before the upgrade to Windows 10 2004.
Some time ago, I uninstalled S1 and wondered whether there might be fall-out. There has been. S2 has refused to start. Repairing the S2 installation has not helped. Finally, I have uninstalled S2, rebooted my laptop, installed S2 (installer SonosDesktopController1203). I have checked the Windows Firewall for presence of Sonos and Sonos library executables allowed on the private network (my home network). All good.
Now, peace and decorum have been restored. Sonos S2 launches again in my Windows 10 2004.
Update: I am afraid, the above solution that I have commented on only works the first time after fresh installation. Upon further start attempts, Sonos S2 only pops the start banner and gets no further.
Sonos, please, fix. Windows 10 2004 does not like S2.
It appears that this Windows Update solves the above issue:
Sonos, you are off the hook. :-)
I wonder what changed in 2004 to create this issue.
Also mine crashes as it is trying to populate the app window with data. But which image is causing this or is it all images on my device?
This is something SONOS needs to debug and solve.
Check Windows Update, do you have any .NET Framework updates pending? I do right now actually.
I’m not saying this fixes it, but a bug in .NET introduced in 2004 could cause this.
I am cautiously optimistic that
Do SONOS support read this or do I need to raise a separate bug report?
Userlevel 7
+23
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.
My issues could well have started after the installation of KB565627 or even earlier. Unfortunately I did not take a note of when S1 stopped working.
Userlevel 7
+23
I wonder what changed in 2004 to create this issue.
Also mine crashes as it is trying to populate the app window with data. But which image is causing this or is it all images on my device?
This is something SONOS needs to debug and solve.
Check Windows Update, do you have any .NET Framework updates pending? I do right now actually.
I’m not saying this fixes it, but a bug in .NET introduced in 2004 could cause this.
I wonder what changed in 2004 to create this issue.
Also mine crashes as it is trying to populate the app window with data. But which image is causing this or is it all images on my device?
This is something SONOS needs to debug and solve.
Userlevel 7
+23
Interesting, this exactly matches another Windows 2004 crash thread which included a full callstack. The app is crashing trying to decode an image. I wonder why some 2004-updates crash here, and others (like mine) are fine?
Page 1 / 2
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.