In setup.bat, has adding code to check the registry for setting the Java path been considered when the existing logic cannot can't find the deployment? I'm specifically referring to scenarios where installed JRE/JDK auto-updating changes the path (to reflect new version) thus invalidating environment variable value(s) and requiring manual intervention. To accommodate this I've modified setup.bat to pull from the registry if the existing logic comes up short.
If there's a simpler way to handle Java's post-update path change, please share. Thanks.