How to Fix ‘Can’t Connect Securely to This Page’ in Microsoft Edge

Attempting to navigate to an internal enterprise portal, banking dashboard, or legacy web service in Microsoft Edge only to encounter the error message “Can’t connect securely to this page. This might be because the site uses outdated or unsafe TLS security settings” halts secure web browsing. Modern Chromium-based Microsoft Edge enforces rigorous transport layer security, strictly disallowing deprecated protocols (such as SSL 3.0, TLS 1.0, and TLS 1.1) and flagging weak cipher suites. When a destination web server has not modernized its cryptographic certificates, an antivirus SSL-inspection proxy corrupts the certificate chain, or local Windows Internet properties disable TLS 1.2/1.3, Edge blocks HTTP/HTTPS handshakes. This guide outlines how to reconfigure TLS protocol suites, reset the Windows SSL state, and safely access required secure web portals in Microsoft Edge.

What Triggers the ‘Can’t Connect Securely to This Page’ Error in Edge?

The cryptographic security stack in Microsoft Edge evaluates multiple validation layers before loading an encrypted connection:

  • Outdated Server-Side TLS Standards: The web host relies exclusively on obsolete TLS 1.0 or TLS 1.1 protocols that are deprecated across modern browsers.
  • Disabled TLS Protocols in Windows Internet Properties: System-wide Schannel configuration disabling TLS 1.2 or TLS 1.3 flags within the operating system registry.
  • Antivirus HTTPS Scanning Interception: Third-party security suites attempting to perform deep packet inspection by injecting self-signed intermediary root certificates.
  • Corrupted Windows SSL Certificate State: Damaged local SSL session tokens and certificate revoking status caches in volatile memory.
  • Third-Party Browser Extension Filtering: Network proxy extensions altering packet headers during cryptographic handshakes.

Method 1: Enable Modern and Legacy TLS Protocols via Internet Options

Ensuring system-wide cryptographic protocols are activated allows Edge to negotiate secure fallback ciphers.

  1. Press Win + R to launch the Run dialogue box.
  2. Type inetcpl.cpl and press Enter to open Internet Properties.
  3. Switch to the Advanced tab located on the far right.
  4. Scroll down to the Security section near the bottom of the list.
  5. Verify and ensure the following checkboxes are ticked:
    • Use TLS 1.2 (mandatory)
    • Use TLS 1.3 (mandatory)
    • Use TLS 1.0 and Use TLS 1.1 (temporarily tick these only if attempting to access older legacy intranets)
  6. Click Apply, then click OK.
  7. Restart Microsoft Edge and retry accessing the destination page.

Method 2: Clear the Windows SSL State

Purging the operating system SSL certificate cache clears corrupted session tickets and expired handshake tokens.

  1. Press Win + R, input inetcpl.cpl, and press Enter.
  2. Switch to the Content tab.
  3. In the Certificates section, click the button labelled Clear SSL state.
  4. A confirmation prompt will state: “The SSL cache was successfully cleared.” Click OK.
  5. Click OK to close Internet Properties.
  6. Reload the webpage in Edge to initiate a fresh TLS handshake from scratch.

Method 3: Temporarily Disable Antivirus HTTPS Scanning

Antivirus utilities inspect encrypted traffic by acting as a local proxy; broken certificate injection triggers immediate connection termination in Edge.

  1. Open your installed third-party security software (e.g., Avast, AVG, Bitdefender, or Kaspersky).
  2. Navigate to Protection Settings > Core Shields (or Web Protection).
  3. Locate options such as HTTPS Scanning, Scan encrypted connections, or Web Shield.
  4. Temporarily toggle this feature to Disabled for 10 minutes.
  5. Refresh the problematic webpage in Microsoft Edge. If the page loads securely, your antivirus program requires a certificate update to validate modern cipher suites.

Method 4: Open the Site in Microsoft Edge Internet Explorer (IE) Mode

For enterprise portals and legacy corporate intranets built on older security frameworks, Edge includes an integrated compatibility mode.

  1. In Microsoft Edge, click the three dots in the upper-right corner and select Settings.
  2. Click Default browser in the left sidebar.
  3. Under Internet Explorer compatibility, locate Allow sites to be reloaded in Internet Explorer mode (IE mode) and set it to Allow.
  4. Click the Restart button to refresh Edge.
  5. Navigate to the blocked URL, click the three dots, and select Reload in Internet Explorer mode.
  6. The site will render using legacy engine protocols without triggering modern TLS restriction barriers.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.