Client reconnects at Startup

[Wizard]

Hi,

It seems, that when you are connected, DON'T disconnect, then turn off your PC (while connected), the software next time comes back
trying to re-connect again, even before logging on if you wait long enough with that...
Seems that when the service starts, it checks if state was connected at shutdown and tries to restore that state re-connecting ?
This happens irrespective of the setting "Set as Startup Connection"...

This is especially annoying when using 2FA on the VPN. That gets then triggered unwanted...
Can this behavior be confirmed and/or is there anything we can do about this behavior as we want to connect on-demand, not according to "last state" ?
If you tell me to post this @Github, please tell me where on Github I can post this for this "normal" version, not DE version...

[solo]

Just remove "SoftEther VPN Client" from "C:\Users\???\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup".

[Wizard]

We tried that, but it then still tries to connect upon startup (if you shutdown while being connected)...

[solo]

My "normal" version does not auto-re-connect after a reboot. Double-check that the manager does not start and in addition set the SE service to manual mode.

[Wizard]

The issue is when "Fast Startup" is enabled in Power Settings, which is by Default...
Shutdown connected, next startup it will connect again...
Logical: Fast Startup does a Hybernate on the kernel/Services, so next startup they just "Continue where they left off", hence the re-connect...
Turning off "Fast Startup" mitigates this behavior...

[dsholm]

There is still a bug where it aggressively tries to reconnect when it shouldn't even try at all. It ignores all the reconnect counts and timers and does its own thing. This causes Two Factor systems to start auto-banning accounts.

We have recently created a script to trigger on resume from sleep or hibernate a these are the events that are triggering the client issue. It simply restarts the service. This will terminate the connection and allow them to manually re-establish and hopefully re-enable the reattempt to connect with shorter intervals.