When manually installing a new build of SeaMonkey, if you are using Windows' "User Switching", so that you can have multiple people logged in at the same time, and if another user is logged in and running SeaMonkey, the installer will prompt you if you want to terminate the other running instances of SeaMonkey or not. You can say yes, the processes will be killed, and the installation will continue. This isn't how the automatic update works. With the automatic update, the new version is downloaded - but if another user has SeaMonkey open, the update process simply fails and tells you that all instances of SeaMonkey must first be closed. The automatic update should mirror the manual installation in this regard. It should prompt you if you want to terminate these other processes or not, so that the installation can continue. I'm using Vista, but I presume that XP also has the same issue.

We can't reliably kill the process since we can't know if the user has the rights to kill the other user's browser plus if the user has entered data in the browser this would cause dataloss which we will not do. As far as updater is concerned we can add file in use support which is bug 466778 so duping.

(In reply to comment #1) > We can't reliably kill the process since we can't know if the user has the > rights to kill the other user's browser plus if the user has entered data in > the browser this would cause dataloss which we will not do. > > As far as updater is concerned we can add file in use support which is bug > 466778 so duping. Rob, could you please give some more details what that in detail means? With fixing bug 466778 I don't see a difference for update failures as described here.

This is in reference to the firefox.exe / seamonkey.exe process which bug 466778 does not solve. It is not always possible to acquire the rights to kill a different user's process. We also don't kill processes with the install for similar reasons. Also, killing a different user's process is just bad due to it being dataloss as I stated in comment #1. I might file a bug to figure out if we can find a way around the firefox.exe / seamonkey.exe / etc. process being is use during update but I am going to wait until the work week to decide whether or not to do so in order to discuss this with a couple of other developers.

Sounds good. Thanks!