User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Firefox produced a message saying it had just finished downloading 2.0.0.12 and needs to restart. But the user who had logged in before me had already seen the update being downloaded and deferred restarting until later. Since that user did not restart firefox, the update was not completed when I logged in instead. On checking, I can see that the version is still 2.0.0.11 Both users have sufficient privileges in Windows to complete the update. Reproducible: Didn't try Steps to Reproduce: 1. Login as a user with sufficient privileges and let firefox download and update 2. Defer restarting the browser and instead logout 3. Login as a different user and start firefox Actual Results: Firefox wastes bandwidth by downloading the update again, for the new user. Expected Results: Firefox should have finished the update initiated by the previous user. I suspect that the update downloaded by the first user was stored in that users home or profile. All handling of updates should be system-wide, not per user. Especially since the earlier user had sufficient privileges, the update should have been stored in a central place, and continued when the second user logs in.

Sometimes I have seen that updates are downloaded to the application folder. Normally they are downloaded to the local settings folder inside the user profile. Robert, is there an already existing bug which covers that issue? Why we still don't download to the application folder each time?