Skip to main content
Contributor I
June 16, 2017
Answered

Windows Desktop Controller Problem

  • June 16, 2017
  • 22 replies
  • 2690 views
I have been using the Sonos Desktop Controller on my PC for a long time and it has always worked. Three days ago it suddenly stopped working. I have tried uninstalling the controller and re-installing new one. It continues to give me the same Windows error message. Is anyone else experiencing something similar? Solutions?
    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 Cinn
    It says "Sonos Desktop Controller has stopped working" and then says "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I have been using the Sonos Desktop Controller for a very long time and have never had this happen.

    I had the exact same issue this week as well. Windows 7 x64 with the latest version of the desktop controller (7.2).

    It looks like some incompatibility with the latest version of .NET Framework.

    The problem started after Windows Update installed the important update:
    "Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for x64 (KB3186497)"

    I just uninstalled Microsoft .NET Framework 4.7 manually (through Control Panel > Programs and Features), then reinstalled the previous version of .NET Framework (4.6.2) that I got from Microsoft's website (just google "Microsoft .NET Framework 4.6.2 (Offline Installer)").

    My Sonos Desktop Controller Program now starts up again.

    Obviously, this is not a long-term solution - after all Microsoft made it an 'important' for a reason - but until Sonos fix the desktop controller so it plays nicely with .NET 4.7 it looks like the best option to get the desktop controller running again is to revert to .NET 4.6.2.

    22 replies

    June 16, 2017
    It continues to give me the same Windows error message. Is anyone else experiencing something similar? Solutions?
    Go on, give us a clue - or would you like us to guess what the error message is?
    MWLauriaAuthor
    Contributor I
    June 16, 2017
    It says "Sonos Desktop Controller has stopped working" and then says "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I have been using the Sonos Desktop Controller for a very long time and have never had this happen.
    CinnAnswer
    Lyricist I
    June 19, 2017
    It says "Sonos Desktop Controller has stopped working" and then says "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I have been using the Sonos Desktop Controller for a very long time and have never had this happen.

    I had the exact same issue this week as well. Windows 7 x64 with the latest version of the desktop controller (7.2).

    It looks like some incompatibility with the latest version of .NET Framework.

    The problem started after Windows Update installed the important update:
    "Microsoft .NET Framework 4.7 for Windows 7 and Windows Server 2008 R2 for x64 (KB3186497)"

    I just uninstalled Microsoft .NET Framework 4.7 manually (through Control Panel > Programs and Features), then reinstalled the previous version of .NET Framework (4.6.2) that I got from Microsoft's website (just google "Microsoft .NET Framework 4.6.2 (Offline Installer)").

    My Sonos Desktop Controller Program now starts up again.

    Obviously, this is not a long-term solution - after all Microsoft made it an 'important' for a reason - but until Sonos fix the desktop controller so it plays nicely with .NET 4.7 it looks like the best option to get the desktop controller running again is to revert to .NET 4.6.2.
    MWLauriaAuthor
    Contributor I
    June 19, 2017
    Thank you VERY much! I tried your solution and it WORKED! I had about 4 emails from Sonos Support and they did not seem to be aware of this problem or this fix. I am going to forward to them your email so that they can help out others with the same problem. I am now once again happily using my Sonos Controller from my PC (as well as my iPhone and iPad). Have a terrific day!
    Lyricist I
    June 19, 2017
    Glad I could help.

    Be aware that because it's listed as an important update, Windows might try to get you to update to .NET 4.7 again whenever Windows Updates checks for updates.

    If this turns out to be the case, you may want to hide the .NET 4.7 update until Sonos fixes the desktop controller.
    There's info on how to hide and unhide updates over at Microsoft's technet site:
    https://technet.microsoft.com/en-us/library/ff382716.aspx
    MWLauriaAuthor
    Contributor I
    June 19, 2017
    Thanks! I have forwarded your analysis to Sonos tech support in the hopes that they will work on a permanent fix to this problem. As you noted, .NET 4.7 probably has some important updates that I would prefer my PC to have but I also like using my Sonos Desktop Controller.
    ratty
    June 19, 2017
    Interesting.

    After Microsoft .NET Framework 4.7 installed on my Win8.1 box, the first time the controller was started it took quite a while to get going, sitting there displaying the logo/splash screen. Presumably some (re)compilation was going on behind the scenes. Since then the controller has started up as normal.

    It does however suggest that the move to .NET 4.7 was not quite as smooth as usual for .NET upgrades.
    MWLauriaAuthor
    Contributor I
    June 19, 2017
    Agreed 🙂
    Lyricist I
    June 20, 2017
    Just to add my voice to this. I have Windows 10 and the controller was sluggish so I reinstalled it and now I just jet the logo and nothing else happens. Are sonos seeking to solve this? Phone and table controllers work well
    Enthusiast II
    June 20, 2017
    There is a new version of the desktop controller (i.e. 7.3) which I installed today but the problem with the desktop controller remains the same. I applied Cinn's solution, which works for me (thanks Cinn) but obviously that problem must be solved before our PCs get into some kind of (bigger) trouble....