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

%3CLINGO-SUB%20id%3D%22lingo-sub-3257456%22%20slang%3D%22de-DE%22%3EEvent%20ID%2036871%3A%20A%20fatal%20error%20occurred%20while%20creating%20a%20TLS%20Client%20credential.%20Internal%20Error%2010013%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3257456%22%20slang%3D%22de-DE%22%3E%3CP%3EDear%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eon%20our%20Windows%2010%20Enterprise%20clients%20version%2021H2%20(latest%20patch%20level)%2C%20the%20following%20error%20occurs%20often%20in%20Event%20Viewer%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELog%20Name%3A%20SystemSource%3CBR%20%2F%3E%3A%20SchannelDate%3CBR%20%2F%3E%3A%2003%2F15%2F2022%2013%3A14%3A53Event%3CBR%20%2F%3E%20ID%3A%2036871Task%3CBR%20%2F%3E%20Category%3A%20NoneLevel%3CBR%20%2F%3E%3A%20ErrorKeywords%3CBR%20%2F%3E%3A%3CBR%20%2F%3EUser%3A%20SYSTEMComputer%3CBR%20%2F%3E%3A%20xxxDescription%3CBR%20%2F%3E%3A%3CBR%20%2F%3EA%20fatal%20error%20occurred%20while%20creating%20a%20TLS%20Client%20credential.%20The%20internal%20error%20state%20is%2010013.%3CBR%20%2F%3EEvent%20Xml%3A%3CBR%20%2F%3E%3CEVENT%20xmlns%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%3C%2FA%3E%22%26gt%3B%3CBR%20%2F%3E%3CSYSTEM%3E%3CBR%20%2F%3E%3CPROVIDER%20name%3D%22%26quot%3BSchannel%26quot%3B%22%20guid%3D%22%26quot%3B%7B1f678132-5938-4686-9fdc-c8ff68f15c85%7D%26quot%3B%22%3E%3C%2FPROVIDER%3E%3CBR%20%2F%3E%3CEVENTID%3E36871%3C%2FEVENTID%3E%3CBR%20%2F%3E%3CVERSION%3E0%3C%2FVERSION%3E%3CBR%20%2F%3E%3CLEVEL%3E2%3C%2FLEVEL%3E%3CBR%20%2F%3E%3CTASK%3E0%3C%2FTASK%3E%3CBR%20%2F%3E%3COPCODE%3E0%3C%2FOPCODE%3E%3CBR%20%2F%3E%3CKEYWORDS%3E0x8000000000000000%3CBR%20%2F%3E%3CTIMECREATED%20systemtime%3D%22%26quot%3B2022-03-15T12%3A14%3A53.3843157Z%26quot%3B%22%3E%3C%2FTIMECREATED%3E%3CBR%20%2F%3E%3CEVENTRECORDID%3E193917%3C%2FEVENTRECORDID%3E%3CBR%20%2F%3E%3CCORRELATION%20activityid%3D%22%26quot%3B%7B39dd8104-3340-0001-4581-dd394033d801%7D%26quot%3B%22%3E%3C%2FCORRELATION%3E%3CBR%20%2F%3E%3CEXECUTION%20processid%3D%22%26quot%3B792%26quot%3B%22%20threadid%3D%22%26quot%3B8500%26quot%3B%22%3E%3C%2FEXECUTION%3E%3CBR%20%2F%3E%3CCHANNEL%3ESystem%3C%2FCHANNEL%3E%3CBR%20%2F%3E%3CCOMPUTER%3Exxx%3C%2FCOMPUTER%3E%3CBR%20%2F%3E%3CSECURITY%20userid%3D%22%26quot%3Bxxx%26quot%3B%22%3E%3C%2FSECURITY%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEVENTDATA%3E%3CBR%20%2F%3E%3CDATA%20name%3D%22%26quot%3BType%26quot%3B%22%3EClient%3C%2FDATA%3E%3CBR%20%2F%3E%3CDATA%20name%3D%22%26quot%3BErrorState%26quot%3B%22%3E10013%3C%2FDATA%3E%3CBR%20%2F%3E%3C%2FEVENTDATA%3E%3CBR%20%2F%3E%3C%2FKEYWORDS%3E%3C%2FSYSTEM%3E%3C%2FEVENT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20already%20tried%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.alitajran.com%2Fa-fatal-error-occurred-while-creating-a-tls-client-credential%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.alitajran.com%2Fa-fatal-error-occurred-while-creating-a-tls-client-credential%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.borncity.com%2Fblog%2F2018%2F08%2F14%2Ftls-1-2-windows-error-reporting-service-wirft-fehler%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.borncity.com%2Fblog%2F2018%2F08%2F14%2Ftls-1-2-windows-error-reporting-service-wirft-fehler%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3D%26gt%3B%20did%20not%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%3C%2FP%3E%3CP%3EMatthias%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3261076%22%20slang%3D%22en-US%22%3ERe%3A%20Event%20ID%2036871%3A%20A%20fatal%20error%20occurred%20while%20creating%20a%20TLS%20Client%20credential.%20Internal%20Error%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3261076%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903482%22%20target%3D%22_blank%22%3E%40Matthias68%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20news%20for%20this%20error%3F%20We%20have%20the%20same%20message%20with%20windows%2010%2021H2%2C%20latest%20patch%20set%20with%20Edge%2099%2C%20latest%20patch%20set%20too.%3C%2FP%3E%3CP%3EI%20noticed%2C%20that%20when%20we%20use%20Chrome%20browser%2C%20we%20don't%20have%20this%20errors.%3C%2FP%3E%3CP%3EAny%20suggestions%3F%3C%2FP%3E%3CP%3EGreeting%3C%2FP%3E%3CP%3EIngo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3261181%22%20slang%3D%22de-DE%22%3ERe%3A%20Event%20ID%2036871%3A%20A%20fatal%20error%20occurred%20while%20creating%20a%20TLS%20Client%20credential.%20Internal%20Error%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3261181%22%20slang%3D%22de-DE%22%3ENo%20solution%2C%20we%20this%20message%20direct%20after%20a%20reboot%2Fsystem%20start%2C%20no%20matter%20if%20any%20browser%20has%20been%20used.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3399536%22%20slang%3D%22en-US%22%3ERe%3A%20Event%20ID%2036871%3A%20A%20fatal%20error%20occurred%20while%20creating%20a%20TLS%20Client%20credential.%20Internal%20Error%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3399536%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20news%20about%20this%20problem!%20we%20have%20the%20same%20problem%20with%20Windows%2010%20Professional%2021H2%2C%20I%20tried%20allow%20TLS1.0%2C1.1%20and%20tried%20enforce%20TLS1.2%20but%20the%20error%20message%20continue...%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

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

 

3 Replies

@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

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

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...