Microsoft Edge loading a blank page, showing “Hmm, can’t reach this page,” or failing to connect to any site is frustrating partly because Edge is so tightly integrated into Windows 11 that its failures can affect other things too. The good news: in most cases the fix is fast. This fits into the wider topic we cover in our Google Chrome Errors.
Start with the fastest possible test: press Ctrl + Shift + N to open an InPrivate window and try loading the same page there. InPrivate starts with no extensions, no cached data, and a fresh session. If the page loads in InPrivate but not normally, the problem is either a corrupted cache or an extension — both are easy fixes. If InPrivate also fails, the issue is at the network layer or in Edge’s installation itself.
Identify the Error Type First
Edge’s error pages are actually informative if you read them carefully:
- “Hmm, can’t reach this page” / ERR_NAME_NOT_RESOLVED — DNS failure. Edge can’t translate the domain name to an IP address.
- “This site can’t be reached” / ERR_CONNECTION_REFUSED — The server actively refused the connection, or the site is down.
- ERR_CONNECTION_TIMED_OUT — Connection attempt started but never completed. Network issue or firewall blocking.
- Blank white page with no error — Usually a rendering failure or hardware acceleration issue.
- Certificate error (NET::ERR_CERT_AUTHORITY_INVALID) — SSL/TLS certificate problem. Separate fix category from loading failures.
Fix 1: Clear Cache and Cookies
A corrupted cache causes Edge to repeatedly try loading broken cached resources rather than fetching fresh ones from the server. This produces pages that partially load, show stale content, or fail entirely on specific sites while others load normally.
Ctrl + Shift + Delete → All time → tick Cached images and files and Cookies and other site data → Clear now → restart Edge. For clearing just one site’s data without affecting everything else: click the padlock icon in the address bar → Cookies and site data → Manage on this site → remove all entries for that domain.
Fix 2: Reset Network Settings
When nothing loads in Edge and other browsers also fail, the problem is Windows’ network stack rather than Edge specifically. The same Winsock and TCP/IP reset that fixes other browser failures works here:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renewRun from an administrator Command Prompt and restart the PC. This resolves DNS failures, connectivity issues from VPN remnants, and corrupted network configuration — the most common Windows-level causes of all-browser page loading failures.
Fix 3: Disable Extensions
Edge extensions — particularly ad blockers, privacy tools, and VPN extensions — intercept network requests. When these block resources a page needs, the page loads partially or not at all. If InPrivate mode confirmed extensions are the cause:
Navigate to edge://extensions → toggle all off → restart Edge → test pages → re-enable extensions one at a time. When a specific page breaks again after re-enabling a specific extension, that extension is blocking something the page needs. Either adjust the extension’s settings for that site (most have per-site allowlist options) or disable the extension for sites it breaks.
Fix 4: Hardware Acceleration
Edge uses GPU acceleration for rendering. When GPU driver issues cause the rendering pipeline to fail, pages either don’t render (blank white page despite loading completing) or Edge becomes unstable while loading complex content.
Edge Settings → System and performance → toggle off “Use hardware acceleration when available” → Restart. Test whether pages now load correctly. If they do, update the GPU driver from the manufacturer’s website. After updating, re-enable hardware acceleration — the updated driver should handle Edge’s rendering requirements without issues.
Fix 5: DNS Settings
Edge-specific DNS failures — where DNS works in other applications but Edge shows ERR_NAME_NOT_RESOLVED — can be caused by Edge’s own DNS-over-HTTPS (DoH) configuration conflicting with the local network setup.
Check Edge’s DNS settings: Settings → Privacy, search, and services → Security → Use secure DNS → set to “Use your current service provider” (disables Edge’s independent DoH and uses Windows’ DNS configuration). If name resolution errors stop, Edge’s DoH provider was returning incorrect results. Switch to a different DoH provider (Cloudflare 1.1.1.1 or Google 8.8.8.8) if you want to keep DoH enabled.
Fix 6: Proxy Settings
Proxy configuration problems cause exactly the same symptoms as DNS failures or network issues — pages don’t load, errors appear, and there’s no obvious connection to proxies unless you know to look. Stale proxy settings from a previous corporate network, or proxy configuration left by VPN software, cause Edge to route requests through an inaccessible proxy server.
Settings → Network and internet → Proxy → check both “Automatically detect settings” and “Use a proxy server.” If “Use a proxy server” is On with an address that’s no longer valid, disable it. Click the padlock in Edge’s address bar → the network status section may also show proxy information for the current connection.
Fix 7: Repair or Reinstall Edge
When pages fail in Edge across all modes (regular, InPrivate, with extensions disabled) and the network works fine in other browsers: Edge’s installation is damaged.
Settings → Apps → Installed apps → Microsoft Edge → three-dot menu → Modify → Repair. This reinstalls Edge’s binaries while keeping your profile, bookmarks, and settings. After repair, restart and test. If Repair doesn’t resolve it, download the latest Edge installer directly from microsoft.com/edge and run it over the existing installation.
Edge Group Policy Affecting Page Access
On corporate-managed Windows 11 machines, Edge’s behaviour is often controlled by Group Policy — including URL filtering, proxy configuration, and feature restrictions. If Edge suddenly stops loading specific categories of sites on a work machine, a policy change from IT is more likely the cause than a technical failure.
Check active policies: navigate to edge://policy in Edge’s address bar. All Group Policy settings applied to Edge appear here. “URLBlocklist” entries block specific URLs or URL patterns. If a site you need is blocked by policy, contact IT for an exception rather than attempting technical fixes that won’t address policy-level restrictions.
Edge Profile Corruption
A corrupted Edge profile causes loading failures specific to one user account — Edge works fine for other users on the same machine but not for the affected user. Creating a fresh profile bypasses the corruption:
Click the profile picture in Edge’s top right → Add profile → Set up and continue without signing in. Browse in the new profile. If pages load normally, sign into your Microsoft account in the new profile to restore synced bookmarks and passwords. The old corrupted profile can then be deleted from profile management.
Our guide on Chrome not loading pages covers the parallel fixes for Chrome users — the network stack reset, proxy settings, and hardware acceleration steps apply equally to both Chromium-based browsers. For Edge not opening at all rather than failing to load pages, our Edge won’t open guide covers the launch failures. Microsoft’s Edge troubleshooting documentation covers the edge://net-internals diagnostics tool for detailed connection analysis, equivalent to Chrome’s net-internals for investigating specific page loading failures at the protocol level.
Edge Not Loading Specific Sites Only
When Edge loads most sites but consistently fails on specific domains, the issue is more targeted than a general browser or network failure. Likely causes for site-specific failures:
Windows hosts file blocking the domain: Open Notepad as administrator → File → Open → C:WindowsSystem32driversetchosts (change file filter to All Files). Any non-comment line containing the failing domain redirects it, effectively blocking it. Remove that line to restore access.
Edge’s Tracking Prevention blocking resources: Edge’s Tracking Prevention in Strict or Balanced mode occasionally blocks resources that sites need to function. Click the shield icon in the address bar → expand the Tracking Prevention section → turn it off for that site. If the page loads after doing this, add the site to Tracking Prevention exceptions.
Microsoft Defender SmartScreen blocking the site: SmartScreen sometimes incorrectly flags legitimate sites. If Edge shows a SmartScreen warning before the page fails, clicking “More information → Go to [site]” bypasses it. For persistent incorrect blocks, report the site as safe through the SmartScreen warning interface.
TLS certificate issues: Some older sites use TLS configurations that Edge’s security requirements reject. The error code (NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM, ERR_SSL_VERSION_OR_CIPHER_MISMATCH) identifies the specific incompatibility. Accessing the site through Edge’s InPrivate mode sometimes bypasses certain certificate policies for isolated viewing.
Edge Performance Mode and Loading Issues
Edge’s Performance Mode (Settings → System and performance) optimises Edge for speed by reducing visual effects and background activity. While this generally improves performance, the “Sleeping Tabs” feature within Performance Mode occasionally causes issues where tabs that were asleep fail to properly reload when reactivated — showing an error page or a blank white screen instead of the expected content.
If page loading failures happen specifically when returning to tabs you haven’t visited in a while: Settings → System and performance → Sleeping tabs → toggle off “Save resources with sleeping tabs.” Edge will no longer suspend inactive tabs, using more memory but avoiding the wake-from-sleep loading failures. Alternatively, increase the “Put inactive tabs to sleep after” time from the default to a longer interval, reducing how often tabs enter the sleep state that may cause loading issues.
Edge’s QUIC Protocol and Network Compatibility
Like Chrome, Edge uses the QUIC protocol (over UDP) for connections to Microsoft and Google services. Some networks block UDP in ways that cause QUIC-dependent connections to fail while standard TCP connections work fine. The symptom: specific Microsoft services (Outlook Web, OneDrive web, Office 365) fail to load in Edge while other sites load normally.
Test: navigate to edge://flags in Edge → search for “Experimental QUIC protocol” → disable it → Relaunch. If the previously failing Microsoft service sites now load, your network blocks QUIC. The fix is either leaving this flag disabled or asking your network administrator to allow UDP on ports 80 and 443 for Microsoft’s IP ranges.
Comparing Edge and Chrome for Diagnosis
If Chrome loads pages that Edge can’t, the problem is definitively Edge-specific rather than a network issue. The most valuable thing this comparison tells you is which layer of the stack to focus on: Edge’s own configuration (profile, extensions, flags, security settings) rather than Windows networking, DNS, or proxy settings — which would affect both browsers equally.
Conversely, if neither Edge nor Chrome loads the same page, the fix is in Windows networking rather than either browser specifically. The distinction is worth confirming early because it determines whether you spend time in Edge settings or in Command Prompt running network reset commands.
Internet Explorer Mode in Edge
Some enterprise internal sites require Internet Explorer compatibility. Edge includes “Internet Explorer mode” for these sites — which sometimes produces loading failures when sites are incorrectly routed to IE mode or when IE mode encounters a site it can’t handle.
Check whether IE mode is affecting a specific failing site: Settings → Default browser → Internet Explorer compatibility → Redirect incompatible sites automatically → confirm whether this is enabled and whether the failing site is being affected by it. IE mode sites have a special icon in the address bar indicating they’re running in compatibility mode. If a site is loading in IE mode unexpectedly, removing it from the IE mode sites list restores normal Edge rendering for it.
WebView2 Runtime Affecting Edge Page Loading
Edge’s page rendering depends partially on the WebView2 Runtime — a separate component that Microsoft maintains independently. When WebView2 becomes corrupted or falls out of sync with Edge’s version, certain types of content (embedded media, complex web applications, Microsoft 365 web apps) fail to render correctly within Edge while simple pages still load.
Check WebView2: Settings → Apps → Installed apps → search “WebView2” → confirm it’s present and at a current version. If it’s outdated or missing, download the WebView2 Runtime installer from Microsoft’s developer pages and install it. Edge’s rendering for affected content types typically restores immediately after the WebView2 update. If you’ve recently updated Edge but not WebView2, they may be out of version sync — updating WebView2 to match Edge’s current version resolves the incompatibility.
This issue is more likely to appear after major Edge updates that advance the underlying Chromium version significantly, particularly on machines where WebView2 auto-updates have been delayed by update policies or network restrictions. The diagnostic clue: Edge loads basic pages but fails specifically on Microsoft 365 web apps, Microsoft Teams web client, or other Microsoft services that use WebView2 heavily for their rendering pipeline. If this sounds familiar, Microsoft Edge Not Loading Pages is worth a look.
Worth noting for completeness: when Edge fails to load pages on a machine that just had Windows 11 freshly installed, the cause is almost always that Edge needs to complete its own first-run setup before it can browse normally — which requires briefly accepting its configuration prompts. Edge also automatically updates on first run after installation, and if this update download fails (due to network restrictions), the initial version may have known page-loading bugs that the first update would have fixed. Manually downloading and installing Edge’s latest version from microsoft.com/edge bypasses the auto-update delay and gets to a fully current browser state immediately. Our guide on Microsoft Edge Won’t Open? Every Fix for Launch Failures covers an adjacent issue.
