Skip to main content
azamp
azamp
New Member
January 30, 2016
Solved

FortiClient 5.4 doesn't work with new Win10 Preview 14251

  • January 30, 2016
  • 6 replies
  • 91026 views

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 ?

    Best answer by egauk

    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."

    6 replies

    Carl_Wallmark
    Carl_Wallmark
    New Member
    January 31, 2016
    Kind of, my forticlient console does not show anymore, I get "webpage cannot be viewed" or something simular, so I cannot configure anything.
    Mattbaldwin
    Mattbaldwin
    New Member
    February 3, 2016

    Also having this issue with not being able to display any forticlient part: Navigation to the webpage was canceled

    Running 5.2.5

    jrvocke
    jrvocke
    New Member
    February 6, 2016

    Build 14257 gives problem to. Starting Forticlient 5.4.780 ends with a BAD POOL CALLER reboot

    educos
    educos
    New Member
    February 12, 2016

    Hi,

    I confirm that I have the same problem.

    Connection goes to 98% then Blue Screen with BAP POOL CALLER error code.

    Please give some explanation or some instructions to get it worked.

    Eric.

    sinmae
    sinmae
    New Member
    February 15, 2016

    Hello,

     

    edit2: and I do have only forticlient VPN part of it, doesnt actually matter, if it is combined (with all other security features), or separate. default windows 10 insider preview installation, just with that crappy defender as AV. no other security solutions. what can I do to help to resolve these issues?

     

    edit: uninstalled all other VPN/virtualization SW, but no difference. maybe in crashdumps will be more info? Im willing to lab/test this issue

     

    its the same here.

     

    i have latest und greatest FortiClient 5.4.0.0780 and Windows 10 Preview 14257.

    not only I had problems with showing menu in client itself, now also restarting to BSOD with bad pool caller.

    Tryied everything, uninstalling all stuff that can interact, to no vail.

     

    Client have huge CPU requirements, but primarily I use it as VPN client on all my devices, even mobile.

    Now I cannot connect via client anymore on windows 10 on PC.

     

    IPsec VPN (L2TP/IPsec) built in windows works without problem actually.

     

    dx

     

    kolawale_FTNT
    Staff
    kolawale_FTNT
    Staff
    February 16, 2016

    Windows OS build 14251 caused FortiClient 5.4 GUI to become blank. This is no longer observed with build 14257.

     

    However, with the latest Windows OS insider build 14257, a BSoD occurs when using FortiClient to establish an SSL VPN connection. This does not happen with previous Windows 10 builds. Development team is working to resolve this in FortiClient 5.4.1.

    sinmae
    sinmae
    New Member
    February 20, 2016

    its the same with newly released Microsoft Windows [Version 10.0.14267] (installed today).

    I tryied logon even with/without User certificate, its still the same (SSL VPN)

    hopefully update will be released soon :)

     

    question is, is it problem with forticlient or is it M$ problem (M$ caused it) and you have to tune your client to comply?

    seadave
    seadave
    New Member
    February 21, 2016

    Fortinet, is it possible to create some sort of page in an obvious location of what combination of FortiClient and OS (MacOS/Windows) are stable and which features are supported?  That would save people a lot of pain and suffering.

     

    Also I would suggest to the above that if you are running into a problem in a lab environment, than that is fine, but if you are in business critical production situations and you are in the fast ring or running ANY type of beta/preview build, you should expect to have problems.

     

    All of these auto-updates on the OS and FortiClient side are destroying stability.  How is anything going to be usable when updates are so frequent and vendor response to coding problems is so slow???  You are going to continue to alienate a lot of customers if you don't find some way to get ahead of these type of issues.

    kolawale_FTNT
    Staff
    kolawale_FTNT
    Staff
    February 24, 2016

    The BSoD issue has been resolved in the latest FortiClient interim builds. You may contact Fortinet Support to receive a build for testing.

     

    sinmae
    sinmae
    New Member
    February 24, 2016

    kolawale_FTNT wrote:

    The BSoD issue has been resolved in the latest FortiClient interim builds. You may contact Fortinet Support to receive a build for testing.

     

    thx for info and effort. I understand, that this is not supported configuration (insider preview).

     

    did requested download via support (P4 ticket), i will let u know, if it helped, or not.

     

    educos
    educos
    New Member
    February 25, 2016

    "You may contact Fortinet Support to receive a build for testing."

     

    Where can I get this request ?

     

    Eric

    SuperJMN
    SuperJMN
    New Member
    March 23, 2016

    No news on this?

    sinmae
    sinmae
    New Member
    March 23, 2016

    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.

     

    egauk
    egauk
    New Member
    April 25, 2016

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

    defcon
    defcon
    New Member
    April 25, 2016

    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]

    defcon
    defcon
    New Member
    April 25, 2016

    ah ya know what I realized, it works with 2-Factor but you cannot specify a port number :port does not seem to work.

    Terms & ConditionsAccessibility statement