Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server.

[1337BeerCan]

The above error message is the only result I get when I click "Start" On Qjackctrl.

It complains about dlls that are not drivers. Maybe they're not, but they are present in C:\Program Files\JACK2\jack

This is a fresh install (64 bit).

What obvious thing am I missing?

[MonstoBusta]

1.9.22 just doesn't work for me either. Roll back to 1.9.21 and see if that version works. That, or running a nightly build under Actions, which is what I did.

[Jealmenh]

The solution to this problem, which worked for me, was to increase, in the Settings/Advanced tab, the delay at startup time and in Options, under Execute script on startup, in the arrow, I selected %N server Name. This solved my problem. Apparently, Windows was not running it automatically and you have to tell it manually.

As you can compare in the image, when it presents the error (left side) it is not running: C:/Program Files/JACK2/jack-router/win64/JackRouter.ini%N , and in the other image, the difference: is running , for that reason it does not start.

Part of the solution I found, which I saw in another thread, was to increase the startup time, that will depend on the amount of audio drivers running at the time Jack starts. On my PC it took 10 sec. What I noticed is that the minimum should be 5 sec, giving Jack a chance to start.

The second thing, after having a while analyzing and testing, in the Options tab I found that, manually it is indicated the route to initiate its connection to the server, exactly the problem, which it did not do and when doing it, it started without problems.