Updating mozilla firefox
In order to verify that you have indeed been updated to a new build, you can go to about:buildconfig, copy its contents, and then compare it with the contents of about:buildconfig when Firefox starts up after an update.
It would be extremely useful if you can test this with different types of security and anti-virus software running.
If Firefox thinks an add-on is unsafe and can cause a security risk, it will block it from loading.
In case of a soft block Firefox will present a warning message but will allow the user to continue if they wish but with compromised security.
Now, the reason that this approach fixes the problem is that swapping the directories, unlike the actual process of applying the update, is really fast.
We are effectively moving the cost of applying the update to right after the update has been downloaded while the browser is running.
Older versions of the Java Deployment Toolkit (DT) and the Java Plugin have been disabled by Firefox.
To see if you are using an ESR release, check the Firefox menu item (Help - About) and looking for the "ESR" identifier.The next time that Firefox starts up, the existing installation is swapped with the new updated installation which is ready to be used.In this scenario, you likely won’t notice that Firefox has applied an update as no UI is shown.The technical details of how I’m fixing this problem can be found this document. When Firefox finishes downloading an update, it launches the updater application in the background without displaying any UI, and applies the update in a new directory that is completely separate from the existing installation directory.
Instead of staging the update itself, an entire updated version of Firefox is staged.
If you observe any problems or warning, or if you see that the update did not change the contents of about:buildconfig, then please let me know so that I can try to fix those problems.