Browsing internal corporate portals, legacy network hardware consoles, or public websites in Microsoft Edge can occasionally be blocked by the error message: “Can’t connect securely to this page. This might be because the site uses outdated or unsafe TLS security settings”. Accompanying error codes often specify ERR_SSL_VERSION_OR_CIPHER_MISMATCH, INET_E_INVALID_PNO, or ERROR_INTERNET_SEC_CERT_REVOKED. Modern Chromium-based Microsoft Edge enforces strict transport security, deprecating obsolete cryptographic handshakes. When web servers run legacy TLS 1.0 or 1.1 protocols, local SSL state caches corrupt, or security filtering software proxies SSL packets improperly, Edge refuses the connection to safeguard user credentials. This guide outlines how to reconfigure cryptographic settings and resolve connection failures safely.
What Causes the Secure Connection Error in Microsoft Edge?
Secure connections rely on symmetric and asymmetric cryptographic handshakes between browser and server. Common causes include:
- Deprecated TLS 1.0 and 1.1 Handshakes: Edge actively disabling unencrypted or weak cipher suites when connecting to older web servers or embedded router interfaces.
- Corrupted Windows Cryptographic Service SSL Cache: Stale intermediate Certificate Authority (CA) certificates or revocation status lists in Windows.
- System Clock and Timezone Desynchronisation: Local system clocks differing from server timestamps, causing valid digital certificates to evaluate as expired or premature.
- Third-Party Antivirus HTTPS Scanning: Security suites injecting self-signed root certificates that fail Chromium certificate transparency checks.
- Misconfigured Proxy or VPN Tunnels: Network tunnels failing to support modern Elliptic Curve Cryptography (ECC) cipher suites.
Step 1: Verify and Synchronise System Time and Date
Digital SSL/TLS certificates contain strict “Valid From” and “Valid To” UNIX timestamps. A clock disparity of even a few minutes triggers security aborts.
- Right-click the clock in the bottom-right corner of the taskbar and select Adjust date and time.
- Ensure the toggle for Set time automatically is turned On.
- Ensure the toggle for Set time zone automatically is turned On.
- Under Additional settings, click the Sync now button.
- Verify that the timestamp shows a successful checkmark next to the current time, then restart Edge.
Step 2: Clear the Windows SSL State Cache
Windows maintains a central SSL certificate cache across all native networking stacks. Stale tokens can prevent Edge from negotiating updated handshakes.
- Press Win + R to open the Run dialogue box.
- Type
inetcpl.cpland press Enter to open Internet Properties. - Click on the Content tab.
- Click the Clear SSL state button.
- A confirmation prompt will state: “The SSL cache was successfully cleared”. Click OK.
Step 3: Enable Modern and Legacy TLS Protocols in Internet Options
If accessing an older legacy intranet site, verifying that proper TLS protocol versions are enabled in the Windows network subsystem is essential.
- In Internet Properties (
inetcpl.cpl), click on the Advanced tab. - Scroll down to the Security section near the bottom of the list.
- Ensure the following checkboxes are checked:
- Use TLS 1.2
- Use TLS 1.3
- If connecting to an essential internal legacy device (such as an old printer console or router), temporarily check Use TLS 1.0 and Use TLS 1.1 to establish compatibility.
- Click Apply and then OK.
Step 4: Use Internet Explorer Mode for Legacy Corporate Sites
For older intranet applications built specifically for legacy encryption standards, Microsoft Edge includes a dedicated Enterprise IE Mode.
- Open Microsoft Edge.
- Click the three horizontal dots (…) in the top-right corner and select Settings.
- In the left sidebar, click Default browser.
- Under Internet Explorer compatibility, locate Allow sites to be reloaded in Internet Explorer mode (IE mode) and set it to Allow.
- Click Restart to restart the browser.
- Navigate to the problematic legacy website, click the three dots menu, and select Reload in Internet Explorer mode. The page will load using backward-compatible security protocols.
Step 5: Temporarily Disable Antivirus HTTPS Scanning or Web Shield
Third-party security software (e.g. Avast, Bitdefender, Kaspersky, AVG) intercepts HTTPS web traffic to scan for malware, often breaking secure handshakes.
- Open your third-party security suite.
- Navigate to Web Protection or Shields settings.
- Locate options such as HTTPS Scanning, SSL/TLS Inspection, or Encrypted Connection Scanning.
- Temporarily disable this feature.
- Reload Microsoft Edge and test if the website connects cleanly. If successful, add an exclusion for the target URL in your antivirus settings rather than leaving protection permanently disabled.
Edge TLS Error Remediation Summary
| Underlying Cause | Diagnostic Indicator | Target Solution |
|---|---|---|
| Time Desynchronisation | SEC_ERROR_EXPIRED_CERTIFICATE |
Synchronise Windows clock in Settings |
| Corrupted Certificate Cache | INET_E_INVALID_PNO |
Clear SSL State in inetcpl.cpl |
| Legacy Cipher Suite | ERR_SSL_VERSION_OR_CIPHER_MISMATCH |
Load in Edge IE Mode or enable TLS 1.2/1.3 |
| Antivirus SSL MITM Proxy | CERT_AUTHORITY_INVALID |
Disable HTTPS Web Shield scanning in antivirus |
Applying these steps resolves secure handshake timeouts while maintaining robust encryption standards across Microsoft Edge.