Navigating to a website in Microsoft Edge only to be greeted by the warning “Can’t connect securely to this page”—often accompanied by the explanation “This might be because the site uses outdated or unsafe TLS security settings”—indicates a Transport Layer Security (TLS) handshake failure between your browser and the destination web server.
Because modern versions of Microsoft Edge enforce strict cryptographic standards (deprecating SSL 3.0, TLS 1.0, and TLS 1.1 in favor of TLS 1.2 and TLS 1.3), servers utilizing obsolete cipher suites, corporate web proxies performing deep packet inspection, corrupted Windows Internet SSL states, or third-party antivirus shields trigger this block.
| Security Block Factor | Technical Fault | Primary Resolution |
|---|---|---|
| Outdated TLS Protocols | Server only supports TLS 1.0/1.1; Edge requires TLS 1.2+ | Verify TLS protocol settings in Internet Options |
| Corrupted Windows SSL Cache | Stale session tickets stored in Windows Schannel cache | Clear SSL State in Internet Properties |
| Antivirus HTTPS Scanning Conflict | Third-party security tool intercepts and modifies TLS certificates | Disable HTTPS / Encrypted connection scanning |
| Edge Secure DNS / QUIC Bug | HTTP/3 (QUIC) protocol drops UDP packets over corporate firewall | Disable Experimental QUIC in edge://flags |
Method 1: Verify and Enable TLS 1.2 and TLS 1.3 in Internet Options
Microsoft Edge relies on Windows’ underlying Schannel security provider. If TLS 1.2 or TLS 1.3 protocols are accidentally disabled in the Windows networking stack, modern secure sites cannot connect.
- Press Windows Key + R, type
inetcpl.cpl, and press Enter to open Internet Properties. - Switch to the Advanced tab.
- Scroll down to the Security section at the bottom of the list.
- Ensure the following checkboxes are checked:
- Use TLS 1.2
- Use TLS 1.3
- Ensure that obsolete protocols like Use SSL 3.0 and Use TLS 1.0 remain unchecked.
- Click Apply, then click OK.
- Restart Microsoft Edge and reload the webpage.
Method 2: Clear the Windows SSL State
Windows caches SSL certificates and session renegotiation tokens. Stale or corrupted certificates in this cache prevent successful cryptographic handshakes.
- Press Windows Key + R, type
inetcpl.cpl, and press Enter. - Click the Content tab along the top.
- In the Certificates section, click the Clear SSL state button.
- A confirmation prompt will report: “The SSL cache was successfully cleared.”
- Click OK, close the dialog, and test your connection in Edge.
Method 3: Disable Experimental QUIC Protocol in Edge
The experimental QUIC (Quick UDP Internet Connections / HTTP/3) protocol can fail on networks that block or throttle UDP traffic on port 443, causing TLS negotiation timeouts.
- In the Microsoft Edge address bar, type
edge://flagsand press Enter. - In the search box at the top, type
QUIC. - Locate the flag named Experimental QUIC protocol.
- Click the dropdown menu next to it and select Disabled.
- Click the blue Restart button at the bottom of the browser to relaunch Edge.
Method 4: Temporarily Disable Antivirus HTTPS Scanning
Many third-party security software suites (such as Avast, Bitdefender, or Kaspersky) insert a custom root certificate authority to inspect encrypted HTTPS traffic. If this intermediate certificate expires or becomes desynchronised, Edge blocks the connection as untrusted.
- Open your third-party antivirus dashboard.
- Navigate to Settings > Web Protection (or Network Protection).
- Locate options such as Enable HTTPS Scanning, Scan Encrypted Connections, or SSL/TLS Inspection.
- Temporarily disable this feature.
- Refresh the problematic webpage in Microsoft Edge.
- If the page loads, reinstall your antivirus suite or update its root certificate certificates.
Method 5: Reset Microsoft Edge to Default Settings
Misconfigured enterprise group policies, corrupted edge extensions, or broken network socket states within the browser profile can be cleanly resolved by restoring defaults.
- In Edge, click the three-dot menu icon in the top-right corner and select Settings.
- Select Reset settings from the left navigation menu.
- Click Restore settings to their default values.
- Click Reset to confirm. This clears temporary cache, cookies, and disables extensions without altering your saved passwords or favourites.
- Restart Edge and verify connection.
Handling Legacy Intranet Web Portals
If you are accessing an older legacy intranet portal inside a corporate environment that genuinely requires legacy TLS 1.0 or 1.1, utilize Microsoft Edge’s integrated Internet Explorer (IE) Mode. Navigate to Settings > Default browser, set Allow sites to be reloaded in Internet Explorer mode to Allow, and reload the page in IE mode to navigate through backward-compatible compatibility layers.