A fatal error occurred while creating a TLS client credential.

Mathias Ottsen 121 Reputation points
2022-02-09T14:35:23.477+00:00

Hey guys,

I've created restrictions on our client devices so that they are only allowed to use TLS 1.2

Now in the event viewer i see tons of error messages:

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

From a couple of google search (primarily https://learn.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions) i've tried the following:

Creating the TLS 1.2 key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2
Create subkeys for Client and Server with: DisabledByDefault 0 & Enabled 1

Created dword entries for .net 32 and 64 bit: 'HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319' / 'HKLM:\SOFTWARE\Microsoft.NETFramework\v4.0.30319' -name 'SystemDefaultTlsVersions' -value '1' and SchUseStrongCrypto '1' - Steps repeated for each .net framework key v1.0, v2.0.50727 and forth.

As an example

172662-image.png

172567-image.png

Our devices are running Windows 10 Enterprise edition. I've tried to test the changes on my device which is running 20H2.

Anyone with an idea of how i can proceed with the troubleshooting?

Windows for business | Windows Client for IT Pros | Devices and deployment | Configure application groups

15 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. eberrocal 1 Reputation point
    2023-01-05T22:04:53.603+00:00

    I have seen this for a couple of years now. several end points...no issues were reported.

    no solution,

    Was this answer helpful?

  2. Tung Tran 0 Reputation points
    2023-09-11T06:00:13.4866667+00:00

    Still error, no help.

    Microsoft, please fix it.

    Was this answer helpful?

    0 comments
  3. Nick M. Kulkarni 26 Reputation points
    2023-10-05T13:40:07.9066667+00:00

    There is an issue with the Microsoft documentation on enabling TLS and other security protocols.
    Older documentation shows setting via registry key needs a DWORD enabled = 1

    later documentation shows the DWORD enabled = ffffffff

    I have tested it recently and enabled =1 did not work it had to be ffffffff.

    Nartac's IIS Crypto GUI app also sets ffffffff . Try using that app https://www.nartac.com/Products/IISCrypto/Download

    to set your servers and clients to Best Practices and rebooting. See if that helps.

    However, I am finding some articles online that show the errors can also be logged when a slow network response causes the client to fall back to a deprecated version of TLS before 1.2 despite TLS 1.2 being correctly enabled.

    https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=azure-monitor#enable-tls-12-on-client-or-server-operating-systems-

    Note

    By default, an OS that supports TLS 1.2 (for example, Windows 10) also supports legacy versions of the TLS protocol. When a connection is made by using TLS 1.2 and it doesn't get a timely response, or when the connection is reset, the OS might try to connect to the target web service by using an older TLS protocol (such as TLS 1.0 or 1.1). This usually occurs if the network is busy, or if a packet drops in the network. After the temporary fallback to the legacy TLS, the OS will try again to make a TLS 1.2 connection.

    What will be the status of such fallback traffic after Microsoft stops supporting the legacy TLS? The OS might still try to make a TLS connection by using the legacy TLS protocol. But if the Microsoft service is no longer supporting the older TLS protocol, the legacy TLS-based connection won't succeed. This will force the OS to try the connection again by using TLS 1.2 instead.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Karl Wester-Ebbinghaus 25 Reputation points
    2023-10-06T08:29:41.38+00:00

    Hi everyone, some state the value has to be 0xffffffff instead of 0x1 (Decimal 1)

    Nartac however patched their product with the following note

    Version 3.2 Build 16 - Released April 11, 2020

    • Added override enabled feature to set Protocols Enabled to 1 instead of 0xffffffff

    The referred guidance still shows that value of one is correct. Where did you see documentation changed to the other value?

    https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=azure-monitor#enable-tls-12-on-client-or-server-operating-systems-

    Was this answer helpful?

    2 people found this answer helpful.
  5. Aleksey Svistunov 0 Reputation points
    2026-01-13T07:58:27.1266667+00:00

    I encountered this error when I tried to run the Microsoft Store and Xbox apps on my Windows 11 Home 25H2.

    User's image

    In the System Events I saw the message:
    A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

    This issue was resolved by enabling TLS 1.2.

    The simplest way to do this is through Internet Properties pane:

    1. Press Win + R
    2. Type inetcpl.cpl and press Enter
    3. In the opened window, go to the Advanced tab
    4. In the Security section check Use TLS 1.2

    User's image

    User's image

    Additionally, for security reasons, it is recomended to:

    1. EnableTLS 1.3
    2. Disable all outdated TLS versions and SSL 3.0

    The registry values mentioned in previous comments are correct, however, the registry entries themselves should not exist by default.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.