none
SSL library load errors on Windows 10 Enterprise (multiple apps showing error) RRS feed

  • Question

  • I found a fix for this error on a MS Support page, but it is for Windows 7 and am running Windows 10 Enterprise.  Can anyone advise if I run the easy fix download file (see download button on MS Support page) support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-a-default-secure-protocols-in if that fix to update the registry settings will work on Windows 10 Enterprise as well as Windows 7?  I have searched for a similar Support page for Windows 10 but cannot find one.

    Regards -
    Carol

    Thursday, October 10, 2019 9:22 PM

Answers

  • No, the above KB and the related fix is applicable for Windows 7 etc... but not for Windows 10.

    Windows 10 and Windows Server 2016 support TLS 1.2 for client-server communications by using WinHTTP.

    Kindly go through the following Microsoft reference:

    How to enable TLS 1.2


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP

    • Marked as answer by CarolP_7591 Friday, October 11, 2019 9:26 PM
    Friday, October 11, 2019 12:25 AM
  • Hi Carol,

    The KB3140245 you mentioned is not applied for Windows 10.

    Beginning with Windows 10, version 1607 and Windows Server 2016, SSL 2.0 has been removed and is no longer supported, SSL 3.0 has been disabled by default.

    TLS 1.2

    This subkey controls the use of TLS 1.2.

    For TLS 1.2 default settings, see Protocols in the TLS/SSL (Schannel SSP).

    Registry path: HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

    To enable the TLS 1.2 protocol, create an Enabled entry in either the Client or Server subkey as described in the following table. This entry does not exist in the registry by default. After you have created the entry, change the DWORD value to 1.

    Detailed information here:

    https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-12

    Regards


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by CarolP_7591 Friday, October 11, 2019 9:26 PM
    Friday, October 11, 2019 1:31 AM
    Moderator

All replies

  • If it tells you how to use the registry to fix this you can add those keys or do what it says windows 10 is still the win NT platform so windows seven registry hacks will work in windows 10 if the DWORD isn't there or the folders create them using the windows 7 method 

    2nd way is to use powershell and the TLS commands and also cipher commands 

    check this link out again and click easy fix 

    Registry information

    To apply this update, the DefaultSecureProtocols registry subkey must be added.
    Note To do this, you can add the registry subkey manually or install the "Easy fix" to populate the registry subkey.

    Friday, October 11, 2019 12:08 AM
  • No, the above KB and the related fix is applicable for Windows 7 etc... but not for Windows 10.

    Windows 10 and Windows Server 2016 support TLS 1.2 for client-server communications by using WinHTTP.

    Kindly go through the following Microsoft reference:

    How to enable TLS 1.2


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP

    • Marked as answer by CarolP_7591 Friday, October 11, 2019 9:26 PM
    Friday, October 11, 2019 12:25 AM
  • Hi Carol,

    The KB3140245 you mentioned is not applied for Windows 10.

    Beginning with Windows 10, version 1607 and Windows Server 2016, SSL 2.0 has been removed and is no longer supported, SSL 3.0 has been disabled by default.

    TLS 1.2

    This subkey controls the use of TLS 1.2.

    For TLS 1.2 default settings, see Protocols in the TLS/SSL (Schannel SSP).

    Registry path: HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

    To enable the TLS 1.2 protocol, create an Enabled entry in either the Client or Server subkey as described in the following table. This entry does not exist in the registry by default. After you have created the entry, change the DWORD value to 1.

    Detailed information here:

    https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-12

    Regards


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by CarolP_7591 Friday, October 11, 2019 9:26 PM
    Friday, October 11, 2019 1:31 AM
    Moderator
  • Thank you very much for your response and assistance.

    Regards -
    Carol

    Friday, October 11, 2019 9:32 PM
  • Thank you Teemo for your response and assistance.

    Regards -
    Carol

    Friday, October 11, 2019 9:33 PM