Fatal error TLS client credential

Asked Jun 18 '19 at 10:40

Active Nov 29 '19 at 04:18

Viewed 3,386 times

I have disabled SSLv3, TLS1.0 and 1.1 on a Windows 10 domain joined laptop, I also disabled triple DES 168 and MD5 to comply with our PCI scans and since then the system logs are full of the same error: A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

I found some articles about that error, one of which shows how to enable TLS1.2 for the Net framework v.4 which I followed but it didn't help at all.

So I reenabled all protocols on the client side one by one and it seems the error stops when I enable SSLv3.

I have installed Wireshark in hope to see more info, notably by looking at Client Hello and Server Hello but I am getting way too much output.

How would you go about finding what specifically causes these errors?

edited Jun 18 '19 at 11:45

asked Jun 18 '19 at 10:40

ThomasC.

What server(s) are you connecting to? – Greg Askew Jun 18 '19 at 12:01
None in particular, there is some behind the scene connections that cause these issues which is why I thought Wireshark could help find out. – ThomasC. Jun 19 '19 at 13:04
Looks like duplicate of https://stackoverflow.com/questions/53121859/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-erro – Jozef Izso Nov 30 '19 at 00:02
@JozefIzso: It's not. – joshudson Mar 11 '20 at 19:22

Fatal error TLS client credential

0 Answers0