Hi All,
I’ve been using VStar V2.25.0 on a Windows 11 PC but it no longer launches. I had problems with another program, Period04, which required java to be uninstalled then reinstalling java jre1.8.0_503. Period04 now works but VStar does not.
I uninstalled VStar then down downloaded and ran the VStarWinSetup-2.25.0.exe file, but still get an error message:
Cannot launch VStar.
Exception: EProcess
Error: Failed to execute : 2
Executable: javaw.exe
Parameters:
-splash: C:\Users\markg\vstar\extlib\vsrtaricon.png
-Xms800m
-Xmx1500m
-jar "C:\Users\markg\vstar\dist\vstar.jar
Any ideas how to proceed?
Cheers,
Mark
Hi Mark
This page may help:
That error suggests a file not found however. Can you check that C:\Users\markg\vstar\dist\vstar.jar exists?
Sometimes a Java installation can be the problem because it’s not 64 bit for example but that’s not likely to be the problem here since Period04 works. BTW when you have VStar working again there is another Fourier plugin you may want to check out that has a few different options (written by Max).
Happy to chat if it helps re: this problem.
David
Hi David,
Thanks for replying.
C:\Users\markg\vstar\dist\vstar.jar is there so that isn’t the problem. Any other suggestions?
I’ll check out Max’s Fourier plugin when VStar is working for me again. Cheers,
Mark
Hi Mark
I suspect what’s happened is that after Java was removed and re-installed for Period04, the old Java path entry is now gone or points at an old now non-existent location. Period04 still works because it uses the new Java location but VStar does not.
Please open a command prompt (type cmd in Windows search box) and paste the result of running these commands:
where javaw
java -version
dir "C:\Program Files\Java\jre1.8.0_503\bin\javaw.exe"
dir "C:\Program Files (x86)\Java\jre1.8.0_503\bin\javaw.exe"
The output should give enough information that we can set JavaPath in C:\Users\markg\vstar\VStar.ini to the right bin folder, e.g.
JavaPath="C:\Program Files (x86)\Java\jre1.8.0_503\bin"
As mentioned earlier, you can also the look at this:
and in particular the VStar program group information that shows how to open and modify the config file (VStar.ini). Note also that the Windows installer can be used to reinstall VStar and download a new Java run-time if needed. I don’t know how that would interact with Period04’s Java run-time though.
David
Hi David,
I tried those commands with the following responses:
C:\Users\markg>where javaw
‘where’ is not recognized as an internal or external command,
operable program or batch file.
C:\Users\markg>java -version
‘java’ is not recognized as an internal or external command,
operable program or batch file.
C:\Users\markg>dir “C:\Program Files\Java\jre1.8.0_503\bin\javaw.exe”
Volume in drive C is Windows-SSD
Volume Serial Number is 7211-2C17
Directory of C:\Program Files\Java\jre1.8.0_503\bin
23/07/2026 12:33 PM 311,480 javaw.exe
1 File(s) 311,480 bytes
0 Dir(s) 312,996,126,720 bytes free
C:\Users\markg>dir “C:\Program Files (x86)\Java\jre1.8.0_503\bin\javaw.exe”
The system cannot find the path specified.
Below is the VStar.ini file:
[Settings]
Description=VStar.exe configuration file created at 2026-10-01T08:42:01
;Additional JVM parameters
Parameters=-Xms800m -Xmx1500m
;Set ShowParameters=1 to view parameters to be passed to Java VM
ShowParameters=0
;VSTAR_HOME parameter overrides environment variable VSTAR_HOME
VSTAR_HOME=
;JavaPath
JavaPath=
Hopefully this will help. Cheers,
Mark
Hi Mark
Based on this, modify VStar.ini, setting the JavaPath line to:
JavaPath="C:\Program Files\Java\jre1.8.0_503\bin"
then try re-running VStar and let me know how that goes.
This should get us closer.
See also VStar Debug Mode mentioned here:
which will also provide more information if VStar still doesn’t start.
David
Hi David,
vstar.ini file set to JavaPath=“C:\Program Files\Java\jre1.8.0_503\bin” resulted in the same error message in my first post.
When I tried to Launch the VStar Debug Mode I got the following error message:
Cannot launch VStar.
Exception: EProcess
Error: Failed to execute : 5
Executable: “C:\Program Files\Java\jre1.8.0_503\bin”\java.exe
Parameters:
-splash: C:\Users\markg\vstar\extlib\vsrtaricon.png
-jar “C:\Users\markg\vstar\dist\vstar.jar”
I’ve installed VStar successfully on an older Windows 10 PC and it is working as expected. However, it would be much more convenient if we can sort out the issue with my Win11 PC. Cheers,
Mark
1 Like
Thanks Mark and understand completely.
Can you first show me what the output of these 3 commands in a cmd prompt is:
"C:\Program Files\Java\jre1.8.0_503\bin"\java.exe
"C:\Program Files\Java\jre1.8.0_503\bin\java.exe"
C:\Program Files\Java\jre1.8.0_503\bin\java.exe
The error appears to be a permission denied error. We can likely just change:
JavaPath="C:\Program Files\Java\jre1.8.0_503\bin"
to:
JavaPath=C:\Program Files\Java\jre1.8.0_503\bin
i.e. remove the quotes.
to see what that gives us in debug (assuming it doesn’t run).
David
Hi David,
Your suggestion to remove the quotes from JavaPath in the VStar.ini file seems to have fixed the problem. VStar now launches with no error messages. I’ll play around with a few light curves and try some of the new features.
For the record, below are the responses to the three commands you asked me to run in the command prompt.
the first command gave:
C:\Users\markg>“C:\Program Files\Java\jre1.8.0_503\bin”\java.exe
Usage: java [-options] class [args…]
(to execute a class)
or java [-options] -jar jarfile [args…]
(to execute a jar file)
where options include:
-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available
-server to select the “server” VM
The default VM is server.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose:[class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
Warning: this feature is deprecated and will be removed
in a future release.
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -no-jre-restrict-search
Warning: this feature is deprecated and will be removed
in a future release.
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions with specified granularity
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions with specified granularity
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
-splash:<imagepath>
show splash screen with specified image
The second command gave:
C:\Users\markg>“C:\Program Files\Java\jre1.8.0_503\bin\java.exe”
Usage: java [-options] class [args…]
(to execute a class)
or java [-options] -jar jarfile [args…]
(to execute a jar file)
where options include:
-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available
-server to select the “server” VM
The default VM is server.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose:[class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
Warning: this feature is deprecated and will be removed
in a future release.
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -no-jre-restrict-search
Warning: this feature is deprecated and will be removed
in a future release.
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions with specified granularity
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions with specified granularity
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
-splash:<imagepath>
show splash screen with specified image
The third command gave:
C:\Users\markg>C:\Program Files\Java\jre1.8.0_503\bin\java.exe
‘C:\Program’ is not recognized as an internal or external command,
operable program or batch file.
1 Like
Hi David,
in your first reply to my original post you mentioned another Fourier plugin written by Max. Where can I find it?
When I try to run the plugin manager I get an error message saying “Server returned HTTP response code 403 for URL https://archive.aavso.org/sites/default/files/vstar-plugins/vstar-plugins-2.25.0/plugins.lst”
This error occurs on both my Win11 and Win10 PCs. Cheers,
Mark
Hi Mark
Go to Preferences → Plug-ins tab, then Set Defaults button.
I suspect the plug-in location base URL is pointing to an old location.
David
Hi David,
setting defaults in the Preferences/Plug-ins tab made no difference, still getting the code 403 error message.
Could this be an issue related to AAVSO migrating to a new website? Cheers,
Mark
Hi Mark
Can you please copy and paste the URL you see in Preferences → Plug-ins → Plug-in location base URL?
There is a change required for the plug-in location since the AAVSO migration yes.
The next official release will have a new URL which we can also use now.
David
Hi David,
sorry for my slow response, we were out all yesterday and evening. The new URL works fine now.
In your first post you wrote “BTW when you have VStar working again there is another Fourier plugin you may want to check out that has a few different options (written by Max).” I didn’t see that new plugin in the list in Plug-in Manager, only the original Fourier one. Where can I find the new one? Cheers,
Mark
Hi Mark
You should see it in the list in Tools -> Plug-in Manager as “DFT and Spectral Window Frequency Range”. It contains a few options.
See also VStar/ChangeLog.txt at 2.25.0 · AAVSO/VStar · GitHub
David