Liquibase --help returns "The system cannot find the path specified"

I am using Liquibase from the command prompt on my Windows 10 PC and I have been using Liquibase since version 3.5.5 and 3.6.3 from the command prompt. I recently tried to upgrade to 3.8.9 using the associated ZIP files under the GitHub releases page. I updated my LIQUIBASE_HOME environment variable to point to the new un-ziped Liquibase 3.8.9 directory which is in the same directory as version 3.5.5 and 3.6.3 (each version has its own folder), I reboot my PC for the updated LIQUIBASE_HOME environment variable to update (it’s probably not necessary but I do the reboot anyway). JAVA_HOME is pointing to an AdoptOpenJDK Java 8 JDK version (Jave 8 update 242 b 8) and java is working from the command prompt. However when I go to run ‘liquibase --help’ at the command prompt I get a ‘The system cannot find the path specified.’ message.

Here’s the command prompt output of ‘liquibase --version’ command not working with Liquibase Version 3.8.9:

I have no clue why I can only get Liquibase version 3.5.5 and 3.6.3 to work form my command prompt. I have tried a bunch of other versions like 3.8.9, 4.3.3, 4.4.0, and 4.4.2 and all have the same problem.

I don’t know what the issue is and I have even tried to use the windows installer that has been packaged into the new versions of Liquibase and I get the same issue.

Does anyone know how to fix this issue?

When I search online, the ‘The system cannot find the path specified.’ error message leads me to issues with JAVA_HOME system variables and nothing is really Liquibase related. There was one stackoverflow article about this issue and Liquibase but a reboot fixed the posters issue for them and a reboot hasn’t helped me and as shown above some versions of liquibase work fine and others do not.

  • I can only post one image at a time for being a new user.

And here’s the command prompt output of ‘liquibase --version’ command working with Liquibase Version 3.6.3

Did you figure this out? Looks like there may be some other java environment variables that are messing with the output, for instance, I see _JAVA_OPTIONS is being picked up. You might clear some of those other options if you have not already resolved this issue.