Local installation loader.bat opens and closes immediately about jatos

[kristian-lange]

Made a fix and tested it with matanmazor' Windows.

For some reasons that I do not fully understand on some Windows the combination of start /b call doesn't work. So I removed it and start Java and JATOS directly which means I had to abandon logging to loader.log on Windows (Linux still working). Now all output (including errors) go directly to the terminal window. Since the loader.log is barely used (all JATOS logging goes to application.log) and Windows usually isn't used for JATOS servers this is acceptable.

[RomainPastureau]

Yes, it works on my office computer - which is on Windows 10, and administrated by my office. I'm gonna keep on investigating when I have some time, because it would be really convenient to have it on my personal computer too.

Update: I tried removing Avast without any change, so the problem doesn't come from there.

[kristian-lange]

What is in the log files? You can find them in the JATOS folder in the logs folder. There can be a loader.log and an application.log. Are there any errors or exceptions?

[RomainPastureau]

Hello! Thanks for your answer :)

The only file appearing is logs/loader.log after I double click on loader.bat, and it is empty...

[kristian-lange]

So it doesn't seem to be a JATOS problem, otherwise there would be something in the logs. Then I'd check firewalls or anti-virus software. They have been blocking JATOS before. Can you switch them off and try to start JATOS again?

[RomainPastureau]

I tried that already... I have Avast and deactivated all agents for 10 minutes before double clicking on loader.bat, without any result. I don't have any other firewall to my knowledge. I'm going to try to dig so that if anybody finds themselves in the same situation they can rely on this thread. Would you have any other idea?

[kristian-lange]

I do not use MS Windows myself, so I'm a bit lost here. I just tried JATOS 3.7.4 on a Windows 11 system again and it worked fine. But as far as I know Windows has this 'Windows Defender' that might block JATOS? And have you had a look in this 'Windows Security'? I can see there a point 'App and browser control' that might block apps that are considered 'unsafe' by Windows.

[RomainPastureau]

I just tried to deactivate all of the options in the Windows Defender App and browser control security, still no improvement :( I'm guessing it's indeed due to that software though, I'm just annoyed Windows Defender or Avast don't show anything saying that they blocked the program...

[kristian-lange]

That is annoying indeed. Do you have another computer with Windows that you can try?

[mamuerie]

Hi, unfortunately, I have the same problem on Windows 11 when using the batch file (which used to work before). But for me it worked using the git bash and running the shell script via ./loader.sh start.

[kristian-lange]

I'm still not able to reproduce - on my system it's working. Do you get any error messages in the terminal (before it closes)? And can you have a look in log/application.log and log/loader.log if there are any errors?

[mamuerie]

The last thing I can read in the terminal is "Starting jatos... please wait" and then it closes. In the log-files are only information about the session I started with the loader.sh script, if I am using the batch file, there is no entry anywhere. Super wired, a few weeks ago it used to work perfectly fine but I cannot recall that I fundamentally changed something on my PC.

[matanmazor]

I started encountering the same issue on my machine too 😭
Windows 11, happens even when turning off all antiviruses and firewalls.