In some versions of the tray, a race condition between the updater and the tray during an update of the ESE backup client prevents the tray from detecting that it is being updated. Under this condition, the tray does not relaunch, but the user will not know that an old version of the tray is still running unless a bug appears. The latest version of the tray launches automatically when the user next logs into their account, which means that this condition does not normally pose a problem.
However, a problem arises when updating older versions of the client, since the Java Runtime Environment (JRE) directory is cached at startup by older versions of the tray, and when the JRE changes, the tray becomes unable to reload the UI. We have addressed this problem by killing the previous versions of the tray that are still present at the end of an update. In this case, the user has two options:
- relaunch the tray using the Windows Start Menu, or
- log out of the session and log in again.