

Workarounds do exactly that, they rely on coincedence that this works with a handful of users. This is the same shit you see on a stage in Vegas where a psychic does mind tricks on the audience, he will always find a few where it works by coincedence. I am NO fan of brainless workarounds that make me disconnect, reboot, remove and reinstall. Also, if this 98% phenomenon is soooooo popular, why is Fortninet not doing anything against it? Like a WORKING Windows 10 client update maybe? It looks like Fortinet simply doesn't care. In my opinion it's the sloppy programmed code of the Fortinet Client.

So disconnecting, rebooting and killing network ports is NOT an otpion and I refuse to believe that the problem is the device.

I also said that the computer is in a remote location where I need permanent access to.
