The Software Update feature allows you to automatically update your Mozilla application and installed add-ons (extensions and themes, but not plugins). Software Update is available in Firefox, Thunderbird, and SeaMonkey 2. This article describes how to configure and run Software Update and discusses problems that can occur during or after an update.
- 1 Checking for updates
- 2 The update process
- 3 Software Update not working properly
- 3.1 Software Update Failed
- 3.2 AUS Update XML File Malformed 200
- 4 Problems after an update
- 5 Configuring Software Update
- 6 See also
- 7 External links
Checking for updates
By default, Software Update periodically checks for updates and notifies you when an update is found. You can modify these settings in your Options/Preferences via the "Advanced -> Update" preference panel (Firefox and Thunderbird) or the "Software Installation" panel (SeaMonkey 2). If you want to force an update check, choose "Help -> Check for Updates...".
The update process
When an update is found, follow the on-screen instructions to download and install the update. The application will need to restart to apply the update, but you can choose to restart later by pressing the Later button.
Software Update not working properly
Software Update problems can sometimes be resolved by simply restarting the computer and then reopening your Mozilla application.  Other update problems can be fixed by downloading the latest version of Firefox, Thunderbird, or SeaMonkey and installing the new version "on top of" your current version  .
If the problem continues, you can manually reset the Software Update feature by closing your Mozilla application and deleting the "updates" folder and the two files "active-update.xml" and "updates.xml", which can be found in the folder where Mozilla stores temporary application data for your operating system.
For example, on Windows 7, the files "active-update.xml", "updates.xml", and the "updates" folder can be found in one of these locations  (using Firefox in the first example). Note: You'll need to show hidden files and folders to find these locations:
- C:\Users\<username>\AppData\Local\Mozilla\Firefox\Mozilla Firefox
- C:\Users\<username>\AppData\Local\Mozilla\updates\<alphanumeric string>
This will solve a number of Software Update problems, including:
- Updates reported when running newest version
- "Check for Updates" is not available in the Help menu ("Downloading..." is shown) after an "AUS: Connection timed out" message 
- In Firefox 1.5 and Thunderbird 1.5, the update download may get stuck at paused 
- "Software Update Failed" error when starting Firefox or Thunderbird.  .
Software Update Failed
Update Failed. Something is trying to trick Firefox into accepting an insecure update
A Software Update "Update Failed" error, Something is trying to trick Firefox into accepting an insecure update. Please contract your network provider and seek help, has been reported to Mozilla in bug 653830 (under investigation at time of writing). See also the forum discussions here and here.
Software Update Failed. One or more files could not be updated
If you see a Software Update Failed error with the message, One or more files could not be updated. (or, in Firefox 3, The update could not be installed), try ending all instances of Firefox or Thunderbird (or reboot the computer) and then restart your Mozilla application, to see if that allows the update to complete. Also try closing any other running programs that may be interfering with the update process, such as the applications listed below.
Software that can cause updates to fail
Other installed applications can disrupt the update process and cause the Software Update Failed error. See this forum topic for other causes and solutions.
- Logitech QuickCam: Disconnect your Web camera, right-click the QuickCam icon in the system tray and select 'Exit" (or open the Windows Task Manager and end the "QuickCam" process, e.g., "QuickCam10.exe") then try the update again.  
- Spybot S&D TeaTimer: Disable TeaTimer as follows, then try updating again (more information here).
- Go into Spybot - Mode - Advanced Mode - Tools - Resident.
- Uncheck the following: Resident "TeaTimer" (Protection of over-all system settings) Active.
Other running programs that may interfere with the update process include:
- Virus scanners, including Comodo Antivirus  NOD32 AntiVirus  and AVG AntiVirus 
- Anti-spyware programs, including SpySweeper  and Spyware Blaster 
- Aqua Dock 
- Gadwin Printscreen 
- Azureus Vuze 
Software Update Failed. The update could not be installed
Some users may see a "Software Update Failed" dialog after restarting Firefox with the message, The update could not be installed. Please make sure there are no other copies of Firefox running on your computer, and then restart Firefox to try again. If you see this dialog, end any Firefox processes (or reboot the computer) and restart Firefox.
If the issue is still not resolved and you are using Windows Vista, try the following: 
- Kill the Firefox process in the Windows Task manager (Press Ctrl+Shift+Esc, go to the "Processes" tab, select the "firefox.exe" process, click "End Process" and confirm your action in the warning dialog).
- Open the Windows Start Menu, type "firefox" (without the quotes) and right-click on the "Mozilla Firefox" entry that appears.
- Select "Run as Administrator" and "Continue" if the User Account Control dialog comes up (some Vista installs do not have UAC enabled).
Another possible solution is to reset the Software Update feature by ending all Firefox processes and then removing "active-update.xml", "updates.xml" and the "updates" folder from the appropriate folder locations (see above). As a last resort, download the latest version of Firefox from www.mozilla.com and install it over your current version.
AUS Update XML File Malformed 200
The message, AUS: Update XML File Malformed (200) can sometimes appear during a check for updates. This is a "catch-all" update error which can occur for different reasons such as being in "offline" mode, network problems, or not being signed on with your Master password (if you've set one up) before the update check . Software Update requires a secure connection so, if you are also receiving errors on webmail login pages, bank sites or other secure (https) sites (e.g. https://addons.mozilla.org) see Error loading secure sites.
If Software Update errors persist, you can download the latest version of Firefox or Thunderbird from www.mozilla.com and install it "on top of" your current version, instead of using the Software Update feature.
Related bug reports include:
- Bug 312661 - Software Update displays "AUS: Update XML File Malformed (200)" if working offline
- Bug 358734 – FIPS prevents manuell update
- Bug 358915 – error trying Firefox Update, AUS: Update XML File Malformed (200)
- Bug 376273 – Improve error message for a failed connection (network error) during update
- Bug 390746 – Software Update displays "AUS: Update XML File Malformed (200)" if system clock is off
Problems after an update
The following issues can occur after a Firefox or Thunderbird update (see the linked articles for details).
- Browser will not start up
- Cannot connect to the Internet after updating (Firewall issues)
- Gray bar below status bar
- Scrollbar gone
- Java Console is disabled message after updating Firefox
- Incompatible add-ons (extensions and themes) are disabled after an update
- Add-ons not working or unable to install themes or extensions - Unexpected installation error -203 after an update
- On Windows laptops with Protector Suite QL (Upek, Inc.) installed, the message Confirm following elevation request to remove orphan Password Bank support may appear each time Firefox starts, if the "Password Bank" fingerprint scanning component detects a change in browser version. Unless you need some feature of the Protector Suite you should uninstall it, as detailed here.
Configuring Software Update
Update channels - Advanced
Updates can be retrieved from a number of different update channels. To check which channel you are on, look in about:config at app.update.channel. This determines what kind of updates you will receive. The current update channels are:
- release: The release channel will provide stable release versions, including security updates (e.g. Firefox 2.0, 184.108.40.206 etc.).
- esr: This is a special release channel for extended-support releases which are mostly targeting enterprise users. Features are frozen with every 7th or so update cycle and only security updates provided (i.e., Firefox/Thunderbird 10.0 ESR updates to 10.0.1, 10.0.2, ..., 10.0.x, then 17.0 as the next ESR branch).
- beta: The beta channel lets you receive every beta, release candidate, and release version of the product (e.g. Firefox 1.5 beta 1, Firefox 1.5 RC 1, Firefox 1.5, etc.). With the new rapid-release process (starting with Firefox/Thunderbird 5.0 and SeaMonkey 2.1), every beta is a release candidate for the next version now, and the actual release build is no longer provided on the beta channel.
- aurora: This is a new channel which has been introduced with the rapid-release scheme; these builds reflect changes which also went into beta for the next release, thus making them available immediately, or which were deemed unsuitable for beta but safe for the following release (and, in general don't contain any string changes).
- nightly: The nightly channel allows you to update to every nightly test build that is produced. There are nightly channels for the trunk (i.e., current release version plus 3 numbers); this is also a nightly channel for the remaining legacy branches (Firefox 3.6 & Thunderbird 3.1 builds).
- default: This channel is used when there is no channel information, for example if you build Firefox or Thunderbird yourself. There are no updates on this channel. This channel is frequently used by Linux distributions, given that they provide own updates through their respective package-management system.
Please be aware that the nightly, and to a lesser extent aurora and beta, channels may install builds that have serious bugs. The application may be non-functional and/or result in your profile being corrupted. See Profile_backup for information to safeguard your data, and see the daily builds threads at the Mozillazine forums for the current status of the builds: Firefox, Thunderbird.
The installer/zip/tar/dmg that you last used to install Firefox, Thunderbird, or SeaMonkey determines what update channel you start on. It does this by installing the file "channel-prefs.js" into <installation directory>\defaults\pref. With the new rapid-release system, you will stay on that channel, thus receive a "bump" to the next version when the repositories are migrated. On the aurora and beta channels, this also implies that a lot of patches are landing at that time (including API and string changes) to synchronize the repositories with the new versions they are carrying.
Note that you cannot change channel using about:config. Instead, you can use the Update Channel Changer extension (go to Help -> Check for Updates -> Change Update Channel). Alternatively, you can edit the channel-prefs.js file with a text editor.
If you tried to change the channel by editing channel-prefs.js and there is no app.update.channel pref in about:config, or it has not changed, then the channel-prefs.js file needs fixing. Either install the Update Channel Changer, or open <installation directory>\defaults\pref\channel-prefs.js in a text editor like Notepad, making sure that it has two lines like this (for the nightly channel):
//@line 2 "/cygdrive/c/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/browser/app/profile/channel-prefs.js" pref("app.update.channel", "nightly");
Only the // on the first line is important because it is a comment. If the value in about:config has still not changed, then right click and reset the preference - this removes the profile value that is masking the application one.
Update URLs - Advanced
Early in the testing cycle of the new software update, testers were required to enter a special update url into the preference app.update.url. This is no longer the case and in fact now that preference is almost ignored. Only the setting from the file firefox.js (or all-thunderbird.js) in the installation directory is used. This is so the application always uses the same updates regardless of what user profile you are running with.