ConfigurationLoadCredential failed, 0x80070057! #4146
Unanswered
savaspapadopoulos
asked this question in
Q&A
Replies: 2 comments 4 replies
-
Windows Schannel doesn't support TLS 1.3 before Windows Server 2022. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Do you have any luck with bcrypthash problem? "The other issue, on Server 2012 R2 the sample (executable) won't even load: "the procedure entry point bcrypthash could not be located in the dynamic link library". Note it's all statically linked." I have similar problem with pre-Windows 10 - but strangely release build does not trigger such error. Do you have problem in release build as well? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi I have a Windows build of msquic but with OpenSSL.
I've tried it on several operating systems. The same binaries work on Windows 10 and Windows Server 2022 without issues. Same settings everywhere.
When I run it on Server 2016 using a self-signed certificate (created with same Powershell command on all platforms)
it shows this error:
Quic -server -cert_hash:6B6E9F9D8515AA64A875B2B95E78CC49D92E7E38
ConfigurationLoadCredential failed, 0x80070057!
Then I tried an OpenSSL self-signed certificate and it works:
MsQuic -server -cert_file:cert.pem -key_file:key.pem
However the same call through -cert_hash works on Server 2022 and Windows 10. It doesn't work on Server 2016
the error is: ConfigurationLoadCredential failed, 0x80070057
Does anyone know what the problem might be?
Is there any way to make this build also work on Windows 7 SP1 and/or Server 2008 R2 or at least Server 2012 R2? Upon starting the executable the following error shows:
the procedure entry point bcrypthash could not be located in the dynamic link library
Thanks
Beta Was this translation helpful? Give feedback.
All reactions