PM 11.30 - WinInet error 12157



after upgrading to PM 11.30 my F-secure Status Monitor window showing "WinInet error 12157" on Administration module and Web Reporting module. Host module status is OK


I have no problem when login in as localhost but administrators using remote console having problems with connection - sometimes they are unable to connect or they get disconected while working.


  • Vad
    Vad Posts: 1,089 Forum Guru

    Hello kallstrom,


    We need more detailed information/logs from your machine for investigation. Please, contact support.


    Best regards,


  • kallstrom
    kallstrom Posts: 25

    I have soled the problem today. It looks like some microsoft updates changed Internet Security Options.

    I have set my IE browser to use SSL 3.0 and TLS 1.0 instead of SSL 2.0 and SSL 3.0

  • etomcat
    etomcat Posts: 1,319 Superuser



    People are reporting the same Wininiet 12157 error message while trying to access the web browser based local GUI of FSAV PSB Server Security 11.


    Trying to adjust SSL / TLS settings under IE net connections / special settings doesn't appear to help. People have to use Firefox browser instead of IE to regain access.


    The problem is possibly related to, but not confimed as casued by Microsoft Updates.


    Yours Sincerely: Tamas Feher, 2F 2000 Kft., Hungary.

  • Vad
    Vad Posts: 1,089 Forum Guru

    Hello Tamas,


    We have one known issue related to WebUI. It appears after Microsoft Update KB3061518.

    Workaround for the issue is to set the ClientMinKeyBitLength registry DWord value to 00000200.


    More details can be found here:


    Best regards,


  • etomcat
    etomcat Posts: 1,319 Superuser

    Dear All,


    Today, I have received an e-mail response from F-Secure Technical Support.


    Yours Sincerely: Tamas Feher, Hungary.




    The F-Secure Technical Support Engineer wrote:


    "... kindly be informed that the error indicates it is related to the secure channel:


    We have released a hotfix to resolve this issue. The hotfix mentions it was for Google Chrome and Mozilla Firefox, we have confirmed that it works for IE as well:

    Thank you and Best regards"

  • Shahrir
    Shahrir Posts: 53
    The direct link to the hotfix seems to be broken, here's the correct link:
This discussion has been closed.