Skip to main content
KRossouw
Contributor I
June 30, 2020
Answered

Sonos S2 Windows app not Launching

  • June 30, 2020
  • 26 replies
  • 3178 views

Hi. I am having trouble getting S2 windows app to work. When I select the installed app icon a orange Sonos logo appears in the middle of the screen ± 500x500 pixels. Then disappears without the controller loading. 
I have tried:

Uninstalling, removing from recycle bin, deleting the downloaded file. Re-downloaded and installed, with restarting the PC inbetween.

Made sure the windows firewall allowed all the Sonos apps and options (private and public)

Switched off my anti virus totally. Uninstalled and reinstalled while off.

 

None of the above seemed to work.

 

Please help guys, this is really frustrating. Am also struggling with support as I am from South Africa and we don't have any proprietary support here. The time difference makes it difficult to contact the US support team.

    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.
    Best answer by controlav

     

    26 replies

    Show previous replies
    Daniel Lamblin
    Daniel Lamblin
    Lyricist II
    December 30, 2020

    @Daniel LamblinI think you have bigger problems than the Sonos app. The fact that your PC blue-screened, and that the service failed to start, are indicates greater system stability problems than the known-but-ignored bitmap crash on start of the Sonos app.

    Thanks for your feedback. Actually before I read it, I also thought there shouldn't be blue screens outside of a driver issue. I had the Nvidia GeForce "gaming" drivers from 2020-12-05, and performed a clean reinstall of those yesterday and was pleased to find the Sonos S2 app also starts up normally now. Oddly it did again ask me to confirm my language, but it might be that it had cleared out some settings after its last crash.

    controlav
    controlav
    Lead Maestro
    December 30, 2020

    By the way this crash has been figured out by another user, it is caused by the color profile you have set. Details in another thread.

    Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
    controlav
    controlavAnswer
    Lead Maestro
    December 30, 2020

     

    Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
    Daniel Lamblin
    Daniel Lamblin
    Lyricist II
    January 8, 2021

    Thanks @controlav, since that's like 3 links away, let's just summarize here: get into your Windows' Color Management. None of the next 3 links mention how.

    Then in the dialog choose the rightmost tab, the advanced tab. In the top section "Windows Color System Defaults" where the top line is a "Device Profile" selection box it should be set to "System Default (the name of the default)". You could also untick the option to use my profile in another tab if the thread linked to the post linked to the thread linked in this thread is to be believed.

    It seems color profile files can get corrupted, though I wonder if there's a new driver or .Net bug in loading some profiles. So if you want to delete the profile that was on before your changed to System Default, look in C:\Windows\System32\spool\drivers\color\

    Until Microsoft updates the control panel in question, it should be able to be opened with Win+R and running "colorcpl". Otherwise in settings (Win+I), choose Appearance and Personalisation, Display then Screen Resolution (or Adjust resolution) and click Advanced Settings then in the ‘Color Management’ tab and press the button ‘Color Management’ (adjust spelling if using British English). I suspect if MS ever removes the color control panel, the UI steps to getting to and changing the color profile will change though.

    controlav
    controlav
    Lead Maestro
    January 8, 2021

    Thanks for the clear instructions. I can repro this crash easily now, on both S1 and S2 apps. I’ll see if anyone at work on the .NET team has an idea why the code crashes in this case. On the good news front, my own app is not affected by this bug.

    Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
      controlav
      controlav
      Lead Maestro
      January 9, 2021

      I dug into his at work, and confirmed this was a regression in Windows, which has been fixed. However it will probably be a long time before that fix makes its way into a shipping version (because reasons). The workaround is correct.

      Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
      Terms & ConditionsAccessibility statement