Sonos Controller S1 update still reboots Windows 10 without a prompt.

I can’t remember the last time a Sonos PC update for S1 or S2 required a Windows reboot of any of my devices, and certainly not without a prompt. Bizarre.

Same here - no reboot of the PC on any Sonos update S1 or S2. Might it have been a Windows background update and purelyby coincidence, perhaps?

Take a look at C:\ProgramData\Sonos,_Inc\runtime\Installer.log to see if there any clues in there as to why it decided to reboot.

Thanks controlav. I have had this issue for well over a year (maybe two) and I am not the only one who has experienced this. I found this in the log:

MSI (s) (E8:CC) [11:13:13:497]: Windows Installer reconfigured the product. Product Name: Sonos Controller. Product Version: 57.7.19010. Product Language: 1033. Manufacturer: Sonos, Inc.. Reconfiguration success or error status: 0.

MSI (s) (E8:CC) [11:13:13:497]: Value of RebootAction property is 
MSI (s) (E8:CC) [11:13:13:498]: Windows Installer requires a system restart. Product Name: Sonos Controller. Product Version: 57.7.19010. Product Language: 1033. Manufacturer: Sonos, Inc.. Type of System Restart: 1. Reason for Restart: 1.

I think the issue may be with Windows Installer. I can live with this providing I remember to close everything before updating S1 Controller as there is no prompt that a restart is going to happen.

dcart,

Try uninstalling the S1 controller from your PC, reboot the PC, then install a fresh copy of S1.

My S1 log is notably different for the same version, taken just now (with no reboot):

MSI (s) (24:20) [06:20:49:209]: Windows Installer reconfigured the product. Product Name: Sonos Controller. Product Version: 57.7.19010. Product Language: 1033. Manufacturer: Sonos, Inc.. Reconfiguration success or error status: 0.

MSI (s) (24:20) [06:20:49:210]: Attempting to delete file C:\WINDOWS\Installer\5763c44e.mst
MSI (s) (24:20) [06:20:49:210]: Unable to delete the file. LastError = 32
MSI (s) (24:20) [06:20:49:218]: Deferring clean up of packages/files, if any exist
MSI (s) (24:20) [06:20:49:218]: Attempting to delete file C:\WINDOWS\Installer\5763c44e.mst
MSI (s) (24:20) [06:20:49:219]: MainEngineThread is returning 0
MSI (s) (24:10) [06:20:49:225]: RESTART MANAGER: Session closed.
MSI (s) (24:10) [06:20:49:225]: No System Restore sequence number for this installation.
=== Logging stopped: 7/31/2021  6:20:49 ===
MSI (s) (24:10) [06:20:49:229]: User policy value 'DisableRollback' is 0
MSI (s) (24:10) [06:20:49:229]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:10) [06:20:49:229]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (24:10) [06:20:49:229]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (24:10) [06:20:49:234]: Note: 1: 2265 2:  3: -2147287035
MSI (s) (24:10) [06:20:49:234]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (24:10) [06:20:49:237]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (24:10) [06:20:49:237]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\5763c44e.mst'
MSI (s) (24:10) [06:20:49:238]: Destroying RemoteAPI object.
MSI (s) (24:F4) [06:20:49:238]: Custom Action Manager thread ending.
MSI (c) (34:8C) [06:20:49:240]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (34:8C) [06:20:49:241]: MainEngineThread is returning 0
=== Verbose logging stopped: 7/31/2021  6:20:49 ===

I have S2. Same behaviour. Anyone figured this out?

I did initially think I had a fix by uninstalling the S1 controller from my PC (Windows 10 Pro, 21H2), then rebooting and then installing a fresh copy of S1. I then got an automatic-with-no-warning-restart on a subsequent update. So what I do now is when I know an update is available, I don’t use S1 programme to update. Instead, I go to the Sonos website and download the new version from there. Updating and installing this way appears to avoid the automatic restart issue (so far). Even then, I make sure all my work is saved and closed just in case before installing an update. 

Thanks. I just did the fresh install to see if that will help in my case. I guess I will see on next update. Otherwise, I will follow your example I think. I also noticed I still had S1 installed so I removed that as well. Maybe that will help 🤷‍♂️

This is still happening for me (been a couple of years of this now), but with controller S2. I recently needed to do a fresh install of Windows 10, so I took the opportunity to install the S2 controller on a fresh win10 install. First time Sonos issued an update perhaps month later, I got the same reboot without warning. Happens every time now. Today’s update prompted me to come back here and see if there had been any movement on this issue.