Microsoft Edge "Can't Reach This Page" (INET_E_RESOURCE_NOT_FOUND)? It's DNS

Microsoft Edge shows “Hmmm… can’t reach this page” with error INET_E_RESOURCE_NOT_FOUND.

What it means: despite the wording, this is almost always a DNS resolution failure — Edge couldn’t turn the address into an IP. So the fixes are network-level (DNS/Winsock), plus a couple of Edge-specific toggles. It’s rarely the website.

Fix 1: Flush DNS and reset the network stack

Open an admin Command Prompt and run, in order, then reboot:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew

This clears the DNS/socket state that triggers INET_E_RESOURCE_NOT_FOUND. (Full walkthrough: reset TCP/IP & Winsock.)

Fix 2: Turn off TCP Fast Open in Edge

A known Edge trigger:

1. New tab → go to edge://flags.
2. Search TCP Fast Open, set it to Disabled (if present), and restart Edge.

Fix 3: Clear Edge’s browsing data

Settings → Privacy, search, and services → Clear browsing data → Choose what to clear → tick Cookies and other site data + Cached images and files → Clear. Reload.

Fix 4: Try a public DNS / disable VPN

• Set your adapter’s DNS to 1.1.1.1 or 8.8.8.8 (Settings → Network → adapter → Edit DNS).
• Disable any VPN/proxy to test.

Fix 5: Repair or reset Edge

Settings → Apps → Installed apps → Microsoft Edge → Modify/Repair; or in Edge, Settings → Reset settings → Restore settings to their default values.

FAQ

Only Edge fails, Chrome works? Then it’s Edge-specific — TCP Fast Open (Fix 2), Edge cache (Fix 3), or a reset (Fix 5). If both browsers fail, it’s DNS/network (Fix 1).

It started after a VPN/antivirus uninstall? That leaves the socket stack broken — the netsh winsock reset in Fix 1 is exactly the fix.

Sources: Microsoft — Fix network connection issues in Windows, Microsoft Q&A — Fix “Hmmm… can’t reach this page” in Microsoft Edge