question

AntonMartinez-5951 avatar image
0 Votes"
AntonMartinez-5951 asked FanFan-MSFT commented

Fatal error while creating a TLS client credential (internal error 10013) after Windows Update 20H1

Hi, after trying everything I found in this community and other websites to solve this issue, I have to do this post because I couldn't fix it.

We have a .Net (4.0) software that connects to a WebService for medical products traceability, and it was working just fine until Windows updated to version 20H1. I've checked with the Service providers and there have been no changes or updates in the Service for years.

Error whithin the software:

93315-6ba96c91-0b38-43c5-a589-291467aa5af7.jpg


This translates to: "Error recieving the HTTP response to https://___. This may be because the link of the service end doesn't use the HTTP protocol. It may also be because the server rejects an HTTP request context (possibly due to the service closure)..."
Then, on debugging we get this error:

93403-ab6c38c8-5ab7-4196-a051-b46b6698ed9e.jpg

Which translates to "The client and the server cannot communicate, because they don't have a common algorithm" Message: " The connection has been terminated. Reception unexpected error"

Finally, in the windows events log:

93382-c7db984f-a4f3-4cdc-a670-836234326009.jpg

We have tried several things to fix this, for example:

  • Enabling TLS 1.0, 1.1, 1.2 and Strong Crypto on the windows registry

  • Enabling FIPS compliant algorithms for encryption

This only happens for update 20H1 and up. We're currently working with a previous windows versión and the WS connection works perfectly fine. But we'd like to have the SO always updated to the last version for security and support reasons.

Any ideas on how to fix this?

Thanks in advance!



windows-10-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

FanFan-MSFT avatar image
0 Votes"
FanFan-MSFT answered FanFan-MSFT commented

Hi,
Check if the following link is helpful:
https://port135.com/schannel-the-internal-error-state-is-10013-solved/
http://www.fileerrors.com/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013.html
https://blog.matrixpost.net/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013/
This response contains a third-party link. We provide this link for easy reference. Microsoft cannot guarantee the validity of any information and content in this link.
Best Regards,

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, thanks for the answer. I've already tried a few of those posible solutions with no luck, the third link one is new to me but it didn't work either.

Thanks again for the help! I'll keep trying to fix it.
Greetings!

0 Votes 0 ·

I am sorry that this issue still hasn't been resolved.
If there is no progress, I would suggest you contact Microsoft Customer Services and Support to get an efficient solution:
https://support.microsoft.com/en-in/hub/4343728/support-for-business
Best Regards,

0 Votes 0 ·