“ keeps loading” does not establish a certificate failure; capture the Schannel error and validate the remote certificate chain before changing TLS or registry settings.
1. Identify where the connection stalls
Run these tests from the affected server, preferably under the same account and proxy configuration used by the application:
Resolve-DnsName external.example.com
Test-NetConnection external.example.com -Port 443
netsh winhttp show proxy
- Failed DNS or TCP 443 means the problem occurs before certificate validation.
- If TCP 443 succeeds, reproduce the application request and immediately open Event Viewer → Windows Logs → System. Filter by source Schannel.
- Record the event ID, alert/error code, and timestamp. For example,
0x80090328 indicates an expired certificate, 0x80090325 an untrusted root, and 0x80090331 an algorithm mismatch.^1^
Also provide the exact Server release—2008 R2 SP1, 2012, 2012 R2, or 2016—and whether the application uses WinHTTP, .NET Framework, Java, or a bundled TLS library. The registry corrections below are not interchangeable.
2. Validate the endpoint certificate
From a workstation that can open the endpoint:
- Open the HTTPS URL in a browser.
- Open the certificate information and export the leaf certificate as a DER-encoded
.cer file.
- Copy it to an approved diagnostic folder on the server.
- Run as administrator:
certutil -verify -urlfetch C:\Temp\endpoint.cer
certutil -URL C:\Temp\endpoint.cer
In the URL Retrieval Tool, select Retrieve for the AIA, CDP, and OCSP entries. This distinguishes an expired/untrusted chain from an unreachable revocation or intermediate-certificate endpoint.^2^
Also inspect Subject Alternative Name in the certificate and verify that it contains the hostname requested by the application. certutil -verify validates the chain and revocation state, but does not by itself prove that the requested hostname matches the SAN.
Apply only the matching result:
- Expired certificate: the external endpoint owner must renew it.
- Untrusted issuer/missing intermediate: deploy the legitimate issuer chain through the normal certificate-management process. Do not import an arbitrary leaf certificate into Trusted Root Certification Authorities.
- AIA/CDP/OCSP retrieval failure: allow the listed validation URLs through the server’s firewall or proxy. “Offline” does not mean “revoked.”
- SAN mismatch: use the hostname listed in the SAN or have the endpoint certificate reissued.
3. Capture an unresolved handshake
If TCP 443 and certificate validation succeed but the application still hangs:
mkdir C:\Logs
netsh trace start scenario=InternetClient capture=yes report=yes ^
tracefile=C:\Logs\Https.etl maxSize=256 fileMode=circular
Reproduce the failure once, then stop:
netsh trace stop
netsh trace captures network packets and related Windows events.^3^ Open Https.etl in an approved ETL-capable network analyzer and inspect:
- whether a TCP connection is established;
- the TLS ClientHello protocol versions and cipher suites;
- whether a ServerHello is returned;
- certificate and TLS Alert messages;
- proxy connections or repeated CRL/AIA requests.
Schannel logging may not show useful events when an application uses its own TLS implementation, such as some Java or bundled OpenSSL clients.
For more detailed Schannel events, set HKLM\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\EventLogging to DWORD 7, then reboot. Back up the registry first; enhanced logging does not take effect until restart.^4^
4. Conditional fixes for older clients
WinHTTP on Server 2008 R2 SP1 or Server 2012 only
If the application uses WinHTTP’s default protocol flag and the trace shows it is not offering TLS 1.2:
- On Server 2008 R2, confirm SP1 and install KB3140245; Server 2012 has no prerequisite.
- Back up the affected keys.
- Set TLS 1.2 as the WinHTTP default:
reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" /v DefaultSecureProtocols /t REG_DWORD /d 0x800 /f
reg add "HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" /v DefaultSecureProtocols /t REG_DWORD /d 0x800 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" /v DisabledByDefault /t REG_DWORD /d 0 /f
The Wow6432Node value is required on x64 systems for 32-bit applications. Use 0xA00 instead of 0x800 only when both TLS 1.1 and TLS 1.2 are required. Restart Windows afterward.^5^
This update does not apply to Server 2012 R2 or 2016 and does not affect applications that explicitly select their protocol.
.NET Framework after a Windows upgrade
Only if the application is .NET Framework and connectivity began failing after a Windows upgrade, set SchUseStrongCrypto=1 under the applicable framework version:
reg add "HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" /v SchUseStrongCrypto /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" /v SchUseStrongCrypto /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319" /v SchUseStrongCrypto /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727" /v SchUseStrongCrypto /t REG_DWORD /d 1 /f
Use v4.0.30319 for .NET Framework 4 or later and v2.0.50727 for .NET Framework 3.5; the Wow6432Node entries apply to 32-bit processes on 64-bit Windows.^6^
After certificate-store or TLS-setting changes, restart the affected application service or IIS application pool; reboot when required by the specific registry/update procedure.
References
- Schannel Error Codes for TLS and SSL Alerts
- Configure AIA issuer retrieval and validate certificate endpoints
- netsh trace
- Enable Schannel event logging in Windows and Windows Server
- Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows | Microsoft Support
- Applications that rely on TLS 1.2 strong encryption experience connectivity failures after a Windows upgrade | Microsoft Support