FortiClient 5.6.2 delayed network connection

[Ttfreer]

We just upgraded FortiClient from 5.6.0 to .2. After the upgrade when the PC boots up it does not automatically connect to the network unless it sits at the login screen for about 30 or so seconds. This is causing a issue for our end users because if they log in too fast it does not run the login scripts or map the home folder. Has anyone else seen this issue with FortiClient 5.6.2?

[PINKVAK]

We do have the exact same problem. After we applied the "Always wait for the network at computer startup and logon" it got a little better in Windows 7, but on Windows 10 its extremly annoying.

It looks like the networkadapters get completely disabled until the FortiClient has completely started.