legacy-knowledge-base
公開されました Sep. 10, 2025

hotfix-123 :: Currently not installed; Won't be installed: requires version 2025.Q1.XX

written-by

Anushka Tiwari

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

legacy-article

learn-legacy-article-disclaimer-text

Issue

  • After adding a hotfix in the patching folder and running the ./patching-tool.sh info command, it shows the following response:
    Product information: 
    * DXP version: 2025.Q1.x LTS 
    * Patching Tool version: 4.0.5 
    * Time: 2025-06-12 09:23Z 
    Currently installed patch: - 
    Available patches: hotfix-123 
    Detailed patch list: [ !] hotfix-123 :: Currently not installed; Won't be installed: requires version 2025.q1.x-lts
  • After running the hotfix installation command (./patching-tool.sh install or ./patching-tool.sh install hotfix-123), observed the following response, and the hotfix did not install as expected:
    ./patching-tool.sh install hotfix-172 
    Downloading hotfix... 
    The specified hotfix does not exist on the servers
    ./patching-tool.sh install 
    No patch is available, DXP is being reverted to the default state... 
    Success in 0.028 seconds. The product is successfully reverted.


Environment

  • Liferay 2025.Q1.x and above.

Resolution

  • In order to resolve this type of issue, there are two ways.
    1. Use the latest patching tool version, which can be downloaded from here: Latest Patching tool
    2. The message displayed “hotfix-123 :: Currently not installed; Won't be installed: requires version 2025.q1.x-lts“ suggests that the error was caused by trying to install the hotfix in the wrong version, or there is an issue with the bundle. Therefore, try to install the hotfix on a clean/new bundle; it should install successfully.

Additional Information

did-this-article-resolve-your-issue

legacy-knowledge-base