Skip to content

Known not a bugs

Jump to bottom
Simon Tushev edited this page Aug 15, 2021 · 8 revisions

🔕 Known not-a-bugs

Do one thing at a time

  • If you add another new (pending) installation entry/entries to list while the app is updating/installing releases, all these entries will be discarded once the ongoing process finishes. Please do one thing at a time.

I receive continuous update notifications

  • Unfortunately, if you install a release with partially incorrect metadata, such as Eclipse Temurin™ 8.0.302+8.1, you may experience an "update loop".
  • This is not a bug in Update Watcher, this is caused by a bug in release metadata.
    We are working together with Adoptium Team to resolve it, however, this is not likely to be fixed soon.

✔ SOLUTION: "skip" the 8.0.302+8.1 release after you've installed it - so no further suggestions for updating to 8.0.302+8.1 will appear.
Please see https://github.com/tushev/aojdk-updatewatcher/wiki/Skipping-releases on how to do it.

JAVA_HOME is not updated

  • JAVA_HOME value is updated only when the app is launched (either in configuration mode or during background check). If you change JAVA_HOME value while running configuration screen, the value will not be updated in the app. However, you can close the configuration window safely: when the next background check occurs, actual value of JAVA_HOME at that time will be used

⚠ Please keep in mind that if JAVA_HOME installation significantly changes (i.e., 8 → 11, or JRE → JDK), you should update API parameters manually (because the app cannot decide whether this is intended or not).
You can use Detect (reset) API settings for selected button to do it.

Turn on scheduled task reminder

  • If the configuration app continiously reminds you to turn on scheduled task (even if you opted out before), this happens because you have not either added some installations manually, or turned auto-discovery on. Once you set at least one of these, the app will consider itself as 'configured' and will remember your opt-out.

Build number not detected

  • For manually added installations that were released prior to Sep 16 2020, it may be not always possible to detect build number.

Build number is +NUM part of AA.BB.CC+NUM version, i.e., for release ver. 8.0.265+2 build number is 2.

If local build number cannot be detected, it will be ignored when checking for new versions: the updater will compare only AA.BB.CC version literals, not AA.BB.CC+NUM. Thus you may miss an update, say, from 8.0.265+1 to 8.0.265+2 - for manually added installations.

It is highly recommended to use automatic discovery (which detects build numbers) for releases downloaded and installed prior to 16 September 2020.

Update left old version installed as well, I have two JDKs/JREs (new and old) now

  • Update from version 11.0.9+11 to 11.0.9.1+1 does not remove 11.0.9+11, instead 11.0.9.1+1 installs alongside, resulting in "duplicate" installs. The MSI features like JAVA_HOME are not kept.
    While this is an issue, is not an issue with this Updater, but with AdoptOpenJDK MSIs themselves in particular and MSI Upgrade mechanism in general: https://adoptopenjdk.net/installation.html#installers, see Upgrade limitation section.
    As a solution, AdoptOpenJDK project suggests Either keep both installations or uninstall the older one.
  • Version 2.0.3 have a mechanism that detects if the old version was not uninstalled and suggests to disable checking for updates.

Icons missing in EOL versions of Windows

  • Icons may be missing in Windows 7/8. This is caused by the fact that Segoe MDL2 Assets font (that provides icons) is missing in Windows 7/8. Unfortunately, I'm not aware whether Microsoft licensing terms allow installing that font on legacy versions of Windows.
Clone this wiki locally