Known not a bugs

🔕 Known not-a-bugs

• JAVA_HOME value is updated 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.

• 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.
• 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.

• 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 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.

• 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.