@phaub I think that’s a great point and is totally worth further discussion and tracking. However, as a test I just booted up an ImageJ 1.x and in my firewall notice it seems like it’s
javaw.exe making the request:
Oddly, I couldn’t get a firewall request to trigger from either
ImageJ-win64.exe launcher in Fiji, despite clearing its entry in the windows defender firewall.
I made an issue to explore and discuss further.
That’s interesting. Since there are a few ways to download launchers, I wanted to mention you can also run
Help > Update... and in the
Advanced mode dialog,
View files of the 'Java-8' Update Site and get it directly from there:
@davidC Thank you for the
debug.exe output! I noticed this line:
Using JRE from ImageJ.cfg: C:\Local\Fiji.app/jre
indicating it has an ImageJ 1.x
@daanb88 I think your
debug.exe output may have been cut off? You can also launch it as
ImageJ-win64.exe --debug from a command prompt (and
ImageJ-win64.exe --debug --console to print the output to the same console).
In any case, I am wondering if you also have an
@daanb88 @davidC Could you try removing the
ImageJ.cfg or removing the Java path specification from the
ImageJ.cfg? (i.e. any line like
jre\bin\javaw.exe) Then try launching the new
ImageJ-win64.exe again and let me know how it goes.
Thank you so much!