Event ID 36871: A fatal error occurred while creating a TLS Client credential. Internal Error 10013

[Matthias68]

Dear all,

on our Windows 10 Enterprise clients version 21H2 (latest patch level), the following error occurs often in Event Viewer:

Log Name: System
Source: Schannel
Date: 15.03.2022 13:14:53
Event ID: 36871
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: xxx
Description:
A fatal error occurred while creating a TLS Client credential. The internal error state is 10013.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1f678132-5938-4686-9fdc-c8ff68f15c85}" />
<EventID>36871</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2022-03-15T12:14:53.3843157Z" />
<EventRecordID>193917</EventRecordID>
<Correlation ActivityID="{39dd8104-3340-0001-4581-dd394033d801}" />
<Execution ProcessID="792" ThreadID="8500" />
<Channel>System</Channel>
<Computer>xxx</Computer>
<Security UserID="xxx" />
</System>
<EventData>
<Data Name="Type">Client</Data>
<Data Name="ErrorState">10013</Data>
</EventData>
</Event>

We already tried:

https://www.alitajran.com/a-fatal-error-occurred-while-creating-a-tls-client-credential/

https://www.borncity.com/blog/2018/08/14/tls-1-2-windows-error-reporting-service-wirft-fehler/ 

=> did not work.

Any ideas?

Best,

Matthias

[#2]

@Matthias68 

Any news for this error? We have the same message with windows 10 21H2, latest patch set with Edge 99, latest patch set too.

I noticed, that when we use Chrome browser, we don't have this errors.

Any suggestions?

Greeting

Ingo

[#3]

No solution, we this message direct after a reboot/system start, no matter if any browser has been used.

[#4]

Any news about this problem! we have the same problem with Windows 10 Professional 21H2, I tried allow TLS1.0,1.1 and tried enforce TLS1.2 but the error message continue...