A fatal error occurred while creating a TLS client credential The internal error state is 10013

Question

Recently deployed a Windows 2016 Standard Server  with Active Directory and Exchange 2016     We have disabled SSL 1 0  2 0 and 3 0 for both Server and Client  and have disabled TLS 1 0 and TLS 1 1   We are repeatedly getting the following entry in our system log   What is causing this  and how can I fix it

User · Accepted Answer

Basically we had to enable TLS 1 2 for  NET 4 x   Making this registry changed worked for me  and stopped the event log filling up with the Schannel error  More information on the answer can be found here Linked Info Summary Enable TLS 1 2 at the system  SCHANNEL  level  Windows Registry Editor Version 5 00  HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2   HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Client   quot DisabledByDefault quot  dword 00000000  quot Enabled quot  dword 00000001  HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control SecurityProviders SCHANNEL Protocols TLS 1 2 Server   quot DisabledByDefault quot  dword 00000000  quot Enabled quot  dword 00000001   equivalent keys are probably also available for other TLS versions  Tell  NET Framework to use the system TLS versions  Windows Registry Editor Version 5 00  HKEY LOCAL MACHINE SOFTWARE Microsoft  NETFramework v4 0 30319   quot SystemDefaultTlsVersions quot  dword 00000001  HKEY LOCAL MACHINE SOFTWARE Wow6432Node Microsoft  NETFramework v4 0 30319   quot SystemDefaultTlsVersions quot  dword 00000001  This may not be desirable for edge cases where  NET Framework 4 x applications need to have different protocols enabled and disabled than the OS does

User · Answer

After making no changes to a production server we began receiving this error   After trying several different things and thinking that perhaps there were DNS issues  restarting IIS fixed the issue  restarting only the site did not fix the issue    It likely won t work for everyone but if we tried that first it would have saved a lot of time

User · Answer

I found this here  https   port135 com schannel-the-internal-error-state-is-10013-solved   quot Correct file permissions Correct the permissions on the c  ProgramData Microsoft Crypto RSA MachineKeys folder  Everyone Access  Special Applies to  This folder only  Network Service Access  Read  amp  Execute Applies to  This folder  subfolders and files  Administrators Access  Full Control Applies to  This folder  subfolder and files  System Access  Full control Applies to  This folder  subfolder and Files  IUSR Access  Full Control Applies to  This folder  subfolder and files  The internal error state is 10013 After these changes  restart the server  The 10013 errors should disappear  quot

[windows] A fatal error occurred while creating a TLS client credential. The internal error state is 10013

Linked Info Summary

Examples related to windows

Examples related to ssl

Examples related to tls1.2

Examples related to windows-server-2016

Examples related to exchange-server-2016