kolawale_FTNT wrote: Seems you disabled everything, so it seems logical
it works again This conflict should be resolved in the next FortiClient
release. It is now July 2016, 2.5 years since the above quote, problem
persists with Forticlient versions ...