This problem occurs on both Windows 32-bit and 64-bit due to Hatch not being able to find java.exe. Batch file hatch.bat is expecting java.exe to be in the same directory with it (see lines 5-8 of hatch.bat).
Windows machines with a PATH system variable set (example: "C:\ProgramData\Oracle\Java\javapath") work without issues since hatch.bat is able to find java.exe from any working directory.
Moving java.exe to the same directory with hatch.bat or adding Java's path (C:\ProgramData\Oracle\Java\javapath) to PATH system variables enables Hatch to work.
Copying java.exe to the same directory with hatch.bat would create a potential security risk since java.exe would not be updated with future Java security patches.
The best fix would be for hatch.bat to look for java.exe in %programdata%\Oracle\Java\javapath if its path is not set in PATH system variables.
This problem occurs on both Windows 32-bit and 64-bit due to Hatch not being able to find java.exe. Batch file hatch.bat is expecting java.exe to be in the same directory with it (see lines 5-8 of hatch.bat).
Windows machines with a PATH system variable set (example: "C:\ProgramData \Oracle\ Java\javapath" ) work without issues since hatch.bat is able to find java.exe from any working directory.
Moving java.exe to the same directory with hatch.bat or adding Java's path (C:\ProgramData \Oracle\ Java\javapath) to PATH system variables enables Hatch to work.
Copying java.exe to the same directory with hatch.bat would create a potential security risk since java.exe would not be updated with future Java security patches.
The best fix would be for hatch.bat to look for java.exe in %programdata% \Oracle\ Java\javapath if its path is not set in PATH system variables.