Why Is Edge Not Loading Pages on My PC?
Edge usually stops loading pages because of DNS, proxy/VPN, extension, profile, TLS/certificate, or wider Windows network issues. Start at the first failure point. If only some sites break, check site-specific blocking or TLS. Ignoring the wrong layer can waste time on resets that do nothing and leave you unable to reach email, updates, or work sites. This guide gives you a fast diagnosis tree for Windows PCs before you reset Edge.
What you’ll need
- Access to the affected Windows account and the Edge profile that fails.
- A second website you know should load, such as a major news site or your email sign-in page.
- Permission to change proxy, VPN, and firewall settings on the PC.
- If available, one alternate network such as a phone hotspot for comparison.
Edge loading matrix
| Failure mode | Most likely cause | Quickest test | Least-destructive fix |
|---|---|---|---|
| All pages fail | DNS, proxy/VPN, firewall, or Windows network stack | Try another browser and another network | Check proxy, DNS, and Winsock before resetting Edge |
| Certain pages fail | Site-specific cookies, TLS/certificate, extensions, or tracking prevention | Open the site in InPrivate | Clear that site’s data and test without extensions |
| Blank white page | Profile corruption, extension conflict, or GPU/rendering issue | Create a new Edge profile | Disable extensions, then test a fresh profile |
| Pages start then stall | DNS timeout, VPN tunneling, security filtering, or certificate checks | Open the same site on a hotspot | Switch DNS, remove VPN, and check date/time |
Why won’t pages load in Edge?
When every site fails, the problem is usually outside the page itself. Check network reachability first, then move to proxy, DNS, and security filtering before you touch Edge reset options. If another browser also fails, the issue is likely Windows or the connection, not Edge alone.
Check the connection. Open a second browser and load two unrelated sites, then switch between Wi‑Fi and Ethernet if both are available. If both browsers fail on the same network, focus on Windows network settings and the router rather than Edge.
Check DNS resolution. Open Command Prompt and run
nslookup example.com. If it times out or returns no address, flush the cache withipconfig /flushdns, then retry Edge.Check proxy and VPN. Go to
Settings > Network & internet > Proxyand turn off any manual proxy. Disconnect any VPN app completely, because tunneling can block page loads even when the network icon still looks normal.Check firewall and security filtering. Open
Windows Security > Firewall & network protection > Allow an app through firewalland confirm Edge is allowed on private networks. If a third-party security suite has web filtering, disable it briefly to test.
Check the network path first
This is the quickest way to separate Edge from Windows. Wi‑Fi dropouts, a bad DNS resolver, a work proxy profile, or a VPN tunnel can all stop page loading while the browser still opens normally. If the same site works on a phone hotspot, you have a network-path problem.
Compare Wi‑Fi and Ethernet. If you can, move from Wi‑Fi to Ethernet or the reverse, then try the same site again. A change in behavior points to the adapter, router, or wireless link.
Change DNS temporarily. In
Settings > Network & internet > Wi‑Fi/Ethernet > Hardware properties, confirm the adapter is getting a valid DNS server. If your policy allows it, test with a public resolver such as 1.1.1.1 or 8.8.8.8, then reopen Edge.Reset the socket stack. Open an elevated Command Prompt and run
netsh winsock reset, then restart the PC. Use this after DNS and proxy checks, because it can clear low-level network behavior that blocks name resolution or HTTPS handshakes.
Say your email site stalls on the loading spinner, while a local intranet page opens instantly. That pattern often points to DNS or TLS rather than a full network outage, especially if the spinner stops after the first redirect and never reaches the login screen.
Why is Edge only loading some websites?
When only certain sites fail, think site-specific data, extension interference, or certificate validation. A site can break in Edge while others load because one cookie is corrupted, a privacy extension blocks a script, or the site’s HTTPS chain is being intercepted or rejected.
Open the site in InPrivate. Use
Ctrl+Shift+N. If the page loads there, your main profile data, cookies, or an extension is likely involved.Clear only that site’s data. Go to
Settings > Cookies and site permissions > Manage and delete cookies and site data > See all cookies and site data, search for the domain, and remove its entries. That clears site-specific storage without wiping every login.Test certificate and clock checks. Open
Settings > Time & language > Date & timeand turn on automatic time and time zone. If the site shows a certificate error or only HTTPS pages fail, wrong system time or security software interception is a common cause.Try a new Edge profile. Open
Settings > Profiles > Add profileand sign in only if needed. If the site works in the new profile, your signed-in profile or sync state is the likely problem.
Suppose a banking site loads the homepage but fails at sign-in while every other site works. That often means the site’s cookies or session storage are bad, not that Edge has a general loading fault.
Apply the least-destructive fixes
Use these only after the network path, proxy, DNS, and site-specific checks. Each step preserves more of your data than a reset. Stop as soon as the page loads again.
Restart Edge cleanly. Close every Edge window, then open Task Manager and end any remaining
msedge.exeprocess. Relaunch Edge and refresh the page withCtrl+R.Clear recent cache only. Go to
Settings > Privacy, search, and services > Clear browsing data > Choose what to clear. Start with Cached images and files for Last hour or Last 24 hours, then retry the site before clearing cookies.Disable extensions one by one. Visit
edge://extensionsand turn off ad blockers, privacy tools, and script blockers one at a time. Test after each change so you can identify the exact extension instead of removing all of them at once.Update Edge and Windows. Open
edge://settings/helpfor the browser, then checkSettings > Windows Updatefor system updates. Edge’s update channel matters because an older build can fail on newer TLS or site behavior.
Common mistakes
- Resetting too early. Do not wipe Edge settings before checking DNS, proxy, and certificate problems. That hides the real cause and can remove useful profile state.
- Clearing all cookies first. Start with the affected domain or a short time range. A full clear signs you out of every site and may not fix a single broken login.
- Testing only one site. Compare one normal site, one problem site, and one hotspot connection. That separation tells you whether the fault is site-specific or system-wide.
- Ignoring the clock. A wrong date or time can break HTTPS even when plain HTTP pages load. Always check automatic time before chasing deeper browser fixes.
If that didn’t work, try this next
If the page still will not load, move from browser data to profile repair, then to a settings reset. Keep bookmarks, passwords, and sync data intact until the last step.
Create a fresh profile. Go to
Settings > Profiles > Add profile. If the new profile loads pages normally, keep using it and review sync conflicts in the old one.Check Windows firewall rules. Open
Windows Security > Firewall & network protection > Allow an app through firewalland confirm Edge is allowed. If a third-party security suite is installed, check its web or network filtering section for Edge-specific blocks.Review proxy and PAC scripts. Go to
Settings > Network & internet > Proxyand inspect automatic proxy detection and any PAC script address. Work or school devices often use these profiles, and a bad script can block only some destinations.Reset Edge settings last. Use
edge://settings/resetand choose Restore settings to their default values only if the earlier checks fail. This is the most invasive browser-side step and should come after the diagnosis tree above.
What if the problem is Edge, my network, or Windows?
Use the failure pattern to decide. If every browser fails on every site, the network or Windows stack is the likely layer. If Edge alone fails, focus on the profile, extensions, cache, proxy settings, or Edge’s update state. If only HTTPS sites fail, inspect time, certificate trust, and security filtering first.
Frequently asked questions
Why is Microsoft Edge not loading pages?
The quickest isolation test is edge://extensions plus InPrivate mode. If the site opens there, an extension or profile setting is more likely than a Windows-wide fault. If no browser loads pages, move to DNS and Winsock.
Why won’t Microsoft Edge load certain pages?
Check site cookies, tracking prevention, and TLS errors. Clear only that domain’s data, then verify system time in Settings > Time & language > Date & time. A wrong clock can break one HTTPS site while others still load.
How do I fix Edge when pages keep spinning and never load?
Test the site on a hotspot, then turn off VPN and proxy settings. If the spinner stops on the hotspot, your normal network path is the issue. If it still spins, clear the site’s cookies and try a new Edge profile.
How do I tell if the problem is Edge, my network, or Windows?
Use two browsers and two networks. If both browsers fail on your Wi‑Fi but work on a hotspot, the network or Windows stack is the likely fault. If only Edge fails everywhere, focus on Edge profile data or extensions.

