I was alerted that a new update was available. I upgraded the the system as such, and then my Windows controller prompted to be updated, so I went a long. As the update was running I was reading a mail, when all of a sudden I'm looking at a monochrome screen with some rotating dots and the text "Restarting". Checking Windows event log I did indeed find this:
The process msiexec.exe has initiated the restart of computer SOMMERWALD on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80030002
Shutdown Type: restart
Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'Sonos Controller'.
So there can be reasons to reboot when installing. Not that I see why it would be required with a simple desktop application, but OK. However, rebooting without asking me is highly insincere!
Installation of Sonos Controller 10.1 restarted Windows
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.
Huh, while I haven't experienced this when updating my desktop controller to 10.1, I've seen this remark made on the Dutch forum as well...
When I think of it, I think this has happened to me once before, so I don't think it is tied to this version. Some file cannot be replace because it is locked - could be the anti-virus. A normal application will inform the user that a restart is needed to complete the installation and give the user two choices "Restart now" or "I do it myself later". What Sonos does is completely unacceptable.
Yes, so why is it Sonos' fault then? I have never been required to reboot my PC after installing/updating the Windows Controller.
https://support.sonos.com/s/article/688?language=en_US
It may not be Sonos's fault that the installation cannot be completed without reboot. I submit however that it is Sonos's fault that when a reboot is needed, the behaviour is unacceptable.
I looked in the installer log, but I was not able to tell why a reboot was considered to be needed, but writing MSI install packages and reading the logs is not within my area of expertise. I did however note that there is a message in the log that apparently was intended to be displayed to the user, saying that a restart is needed, and that I should click Yes to restart now and No to restart later.
In case anyone understands these logs better, I have uploaded the installation log on http://www.sommarskog.se/temp/Installer.log, For reference, the log from the previous installation (which did not cause a reboot) is in http://www.sommarskog.se/temp/Installer_old.log. The reboot message is in Swedish and appears at 23:57:48:578.
I looked in the installer log, but I was not able to tell why a reboot was considered to be needed, but writing MSI install packages and reading the logs is not within my area of expertise. I did however note that there is a message in the log that apparently was intended to be displayed to the user, saying that a restart is needed, and that I should click Yes to restart now and No to restart later.
In case anyone understands these logs better, I have uploaded the installation log on http://www.sommarskog.se/temp/Installer.log, For reference, the log from the previous installation (which did not cause a reboot) is in http://www.sommarskog.se/temp/Installer_old.log. The reboot message is in Swedish and appears at 23:57:48:578.
Try re-installing the DotNet Framework. Or you turn off the Anti-Virus during the controller update. Or you may want to try Windows Defender instead of your currently installed Internet-Security-Suite.
https://dotnet.microsoft.com/download/dotnet-framework/net472
https://dotnet.microsoft.com/download/dotnet-framework/net472
Sonos Controller 10.6 did the same thing. This is a dilletante impertinence! Stop implementing reboots without request!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.