May be wrong or unsupported default locale, I had such error during stage starting for FR some time ago. It was exactly similar style - not to find JVM, but by fact was stage starting problem
I made a mistake, sorry, in order to find why java-based bisq isn’t started you should run in cmd from the C:\Users\John\Appdata\Local\Bisq\ next command: java -jar app/Bisq.jar.
From the Nodejs 5.1.1 (x64) and npm command prompt I get the following:
C:\Users\John\>C:\Users\John\Appdata\Local\Bisq\ C:\Users\John\Appdata\Local\Bisq\ is not recognised as an internal or external command, operable program or batch file.
C:\Users\John\>java -jar app/Bisq.jar Error: Unable to access jarfile app/Bisq.jar
In order to navigate to the directory you need to use a command for changing directory called “cd”.
So in the above output your current working directory is C:\Users\John so to go to C:\Users\John\Appdata\Local\Bisq\ you need to run the following command first "cd Appdata\Local\Bisq\"
From there you need to run the “java -jar app\Bisq.jar”
Now it starts loading, but gives me the message, “Couldn’t generate key.” If I check obfs4 or use the provided bridges, it doesn’t give me a link. If I restart, it does the same thing.
The file is too large to post, and reporting on github would not be anonymous. What part of the logs would you like to see? (or for what should I be looking?)
Just a wild stab, but I had a similar problem while developing an unrelated project with Java dependency. What happened was that the user had JDK and JRE installed, and JDK was on PATH for “java” command.
Well if it is running now then you might not have a problem with java anymore, but I don’t know. Maybe there is something in particular with your java installations and so on that is causing the issue. Reading the log file and looking for some errors or warnings could help debug the issue.
About the bridges and obfs4, there should be a reason for you to use those unless you can’t connect to the Tor network, for example with the Tor browser.
I seriously doubt that your local wallets are causing the issue here. Bisq doesn’t really require or use them when it is run. (it just prefers a local node to connect to for Bitcoin data, but that is unrelated to this, I would say)
If you run from the jar file you use the local JDK and that is missing a certain jar file (bouncycastle). Try to run the exe then you dont have that issue or otherwise build from source like described in the /doc/build.md file.
I had the same issue today. Windows 10 pro. It was solved by giving administrator access to the user. The installation goes to the admin profile and runs fine. If you installed with a user it never finish installing.
I make a shortcut to the admin folder and now is working. If I run the program installed in the user profile I ever get this error.
Manfred, if you need further tests just send me an email. Greetings.