Patch My PC Ideas & Feedback
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Patch My PC currently provides Java products in two primary ways:
Major version-specific products (for example, Oracle Java 8), which remain within that major version and do not remove other major Java versions that may be installed.
"Latest" products, which automatically update to the newest available release and remove older major versions as part of the installation process.
For some Java vendors, including Oracle Java, the "Latest" product may move between LTS and non-LTS releases depending on the vendor's current release strategy. While this behaviour is appropriate for customers who always want the newest available Java version, it creates challenges for organisations that intentionally deploy non-LTS Java releases alongside existing LTS versions.
A common scenario is where a customer wants to:
Retain an existing LTS release for application compatibility.
Deploy and maintain a specific non-LTS release.
Patch that non-LTS release within its major version.
Avoid uninstalling other Java major versions during updates.
Today, the only option for many non-LTS releases is to use the corresponding "Latest" product. Because "Latest" products are designed to remove older major versions and keep only the current release, this can result in unintentionally removing Java versions that customers want to keep installed side by side.
Requested Enhancement
Add dedicated catalog entries for non-LTS Java releases across supported vendors, including Oracle Java, Azul Zulu, Amazon Corretto, and others where applicable.
These products should behave similarly to existing major version-specific Java offerings:
Target and patch a specific Java major version.
Remain within that release train rather than automatically moving to a newer major version.
Support side-by-side installation scenarios with other Java versions.
Avoid the uninstall and supersedence behaviour associated with "Latest" products.
Business Value
Many organisations have application compatibility requirements that prevent them from standardising on a single Java version. Supporting dedicated non-LTS Java products would provide customers with greater control over their Java estate while allowing them to continue using Patch My PC for automated patching.
This enhancement would reduce the need for custom packaging and manual update processes while better supporting environments where multiple Java versions, including both LTS and non-LTS releases, must coexist.
Similar requests below.
We have different development teams that require different versions of Java JDK. Some still need 17 or 21 while others have moved on to v26. I need to be able to patch v26 installs without removing older major versions. Only when non-LTSC versions are out of support should it remove those versions. It would be great if this could be an option on the "latest" update packages to remove or retain older major versions.