FortiClient 5.4 doesn't work with new Win10 Preview 14251

[azamp]

Hi after installing new Windows 10 Preview 14251 latest FortiClient 5.4. doesn't work anymore. I deinstalled and reinstalled the same Problem.

"Your system has been quarantined." error message after starting. It seems that the Network Driver is incompatible.  

Anyone with the same experience ?

[egauk · Accepted solution]

I opened a ticket last week as well and interim build 5.4.0.799 was provided.  However, under Windows 10 insider preview it still causes a BSOD immediately after connecting to the VPN.

It should be fixed in 5.4.1 - here is the response from Fortinet support.

"Actually FortiClient 5.4.1 is expected Mar 08, 2016 - Mar 25, 2016. The above date is for guidance purposes and subject to change without notice."

[egauk · Accepted solution]

It is possible that I have missed something, but in my search for an alternative there just isn't one.  Fortinet uses a proprietary implementation of SSL-VPN so clients like SoftEther won't work.  I'm with you though, this nonsense with the Forticlient not working every few months is getting old and it's not just with Windows 10 preview.  Mac also has its issues with the Forticlient.

[seadave · Accepted solution]

What version are you running on the FG?  I'm using 5.4 and the SSLVPN - HTML5 RDP client is awesome (no need for FC install).  If you don't have two FGs to test with, I wouldn't suggest upgrading though.  I'm not having problems, but I have two FG500Ds and was able to do a lot of testing to ensure it would like my config.  I think 5.4 also runs better on devices like the 500D that have more RAM and CPUs.

Perhaps you could use IPsec or the native L2TP client in Windows.  I believe that is supported. 

5.2 - http://docs.fortinet.com/d/fortigate-ipsec-vpn-520

5.4 - http://docs.fortinet.com/d/fortigate-ipsec-vpn-5.4

[defcon]

Still bluescreening on latest Windows 10

[SuperJMN]

No news on this?

[sinmae · Accepted solution]

no, even with two interim builds (requested from support) , still almost the same scenario. now it did not restarted, but seems that ISDN virtual adapter will not fetch assigned address. in fortiVPN client you can see selected/assigned IP address, but in ISDN adapter, there is just APIPA. any attempt to change that will result in not connecting at all.

if you try that same config and same version of forticlient in other machine (like in VM 2008 server) everything is ok, so seems to be no problem with fortigate config.

[alpeshthaker]

Any update on this error ?

or any alternative to connect VPN till this error resolve ?

[kolawale_FTNT]

Consider requesting for an interim build of FortiClient 5.4.1 through Fortinet Support.

[sinmae]

already did that and got two interim builds. none of them did worked yet.

5.4.0.0800 is version Ive got right now.

should somebody test 5.4.1 and post results, I will be happy :)

[kolawale_FTNT]

Interim builds newer than 0800 run better on the latest Windows 10 insider previews

Lets all hope that Windows 10 will no longer change too much. Or they will be backwards compatible with existing network drivers.

[mwkirk]

Reading this thread seems that 5.4.1 should be out soon?  I am having issues where SSL VPN seems to work fine for a little bit then it will stop working.  I can disconnect and then a lot of the time it will not reconnect.  There is an  PPPoP WAN adapter that just sits with a state of connecting.  The only fix is to reboot the computer.  Hoping maybe a VPN client update will fix this?? 

[egauk]

FYI, the FortiClient available in the Windows Store is working for SSL VPN under Windows 10 Insider Preview builds!

[defcon]

egauk wrote:

FYI, the FortiClient available in the Windows Store is working for SSL VPN under Windows 10 Insider Preview builds!

[strike]Unfortunately the Windows Store SSL Client does not allow 2 Factor authentication, if at all possible can someone send me a link to an Interim Build that works to kyle.omegasystems[at.]gmail[dot]com[/strike]

[strike] [/strike]