how to fix EXE4J_JAVA_HOME, No JVM could be found on your system error?

After successfully installing the 64-bit version of Java 1.7 and exe4j, I eagerly attempted to generate an executable file using exe4j. However, much to my disappointment, an error occurred while running the program.

This is how I set up the path variable. And this is the correct JRE path. What did I overlook? Please inform me.

enter image description here

Thank you.

Inquired on August 5, 2015

Dil.'s user avatar

Dil.Dil.

1,9867 gold medals 41 silver medals

4.

During the configuration process of exe4j, make sure to complete this task. In the fourth step of the Exe4j wizard, choose the Executable Info selection and explore the Advanced options to select either 32-bit or 64-bit. This method proved effective for me. Alternatively, you can install both JDK tool-kits, x64 and x32, on your machine.

Replied on August 30, 2015 at

Chathurika Senani's user avatar

1.

In my situation (OWASP Zap scanner), I needed to install the most recent OpenJDK from https://adoptium.Net.

Responded on January 12th at

cirrus3d's user avatar

Cirrus3dcirrus3d.

1112 silver accolades3

Give it a shot and install the Java 6 32-bit edition, which is fully compatible with Install4J 4.0.5. It should start smoothly, or give you the option to run the installer once more.

Any updated edition or the 64-bit edition of 6 will not succeed, lamenting that the java.Exe is corrupted.

Replied on February 10, 2016 at

bhlowe's user avatar

Bhlowebhlowe.

4184 silver accolades8

There are a couple of steps to address this issue.

  • Remove software that is related to
  • If NodeJS is already installed
  • Get java 8 update161
  • Install it.
  • The issue resolved: The problem brought to my attention during the uninstallation of the openfire server.

    See also  All Uses for Rotten Flesh in Minecraft Listed

    Responded on July 26, 2018 at

    0.

    BH’s response to the installation of Java 6u45 was almost there… Yet, the reboot still triggered a pesky popup. However, the magic happened when Java 6u45 was uninstalled, rebooted, and voila! No more warnings! A big shoutout to BH for saving the day! Subsequently, the cutting-edge version, 8u151-i586, was seamlessly installed and rebooted without any warnings.

    I inserted lines in PATH as mentioned earlier, but it had no effect.

    My operating system is Windows 7, 64-bit. I received a warning because there was no Java Virtual Machine (JVM) found, specifically the 32-bit version. Although I had the option to install the 64-bit version, I chose the 32-bit one since it offers better compatibility with all programs.

    Replied on October 29, 2017 at

    If you’re facing any issues with the Java JDK/JRE package, why not give a shot at downloading and installing/configuring the most up-to-date version of JDK? After a restart, it did the trick for me, and who knows, it might just work wonders for you as well.

    Responded on September 15, 2021 at

    1.

    Facing a comparable issue, albeit with a twist of desiring the 32-bit edition, I resolved it by resorting to the installation of Windows XP’s 32-bit version on a virtual machine.

    Replied on March 15, 2022 at

    FarhadFarhad.

    1043 silver medals 17

    Leave your belongings there and also give the following a try:

    Begin by clicking the Start button, then perform a right-click on My computer. Proceed to select Properties, followed by Advanced system settings. Next, navigate to Environment Variables and locate the variable name labeled “Path” within the lower box.

    See also  How to Summon Pokemon in Pixelmon: Minecraft

    Set path value value as: (you can just add it to the starting of line, don’t forgot semi column in between ).

    c:\Program Files\java\jre7\bin
    

    Responded on August 5, 2015 at

    JeggJegg.

    5513 silver accolades

    6.

    It worked for me, but the exe4j can leave a mark when you double click the .Exe application.

    Responded on August 22, 2017 at

    1.

    Leave a Reply

    Your email address will not be published. Required fields are marked *