Fix Chrome Not Loading Pages

When Chrome can’t load any pages, the problem is almost never Chrome itself — it’s something between Chrome and the internet. The diagnostic that quickly identifies which layer: open another browser (Edge, Firefox) and try the same page. If it works there, the problem is Chrome-specific (settings, extensions, profile). If it fails there too, the problem is system-wide (DNS, proxy, firewall, network). We go deeper on the whole subject in our Google Chrome Errors.

For Chrome-only failures: incognito mode test is next. Ctrl+Shift+N opens incognito with extensions disabled. If pages load in incognito but not normal Chrome, an extension is the cause. If incognito also fails, it’s the Chrome profile or settings — chrome://flags reset or profile reset is the path forward.

For system-wide failures: chrome://net-internals/#dns → click Clear host cache, then chrome://net-internals/#sockets → Flush socket pools. These clear Chrome’s network-level caches that can hold bad entries even when the underlying network is fine. Combined with switching DNS to Cloudflare (1.1.1.1) at the Windows level, this resolves most network-layer issues. Full diagnostic below covers each scenario.

Start Here: The 90-Second Tests

Before changing any settings, run these checks in order — each one takes 30 seconds and rules out a specific layer:

1. Try another browser (Edge, Firefox). If pages load there, the issue is Chrome-specific. If nothing works in any browser, it’s a Windows network problem.
2. Check on your phone via the same Wi-Fi. If the phone also can’t reach sites, the issue is the network or router. Restart the router and test again.
3. Incognito mode (Ctrl + Shift + N). If it works in Incognito, an extension is blocking page loading in your regular session.

These three tests together narrow the problem to one of three categories (Chrome-specific, Windows network, extension) in under two minutes. The rest of the fixes target each category.

Fix 1: Clear Chrome’s Cache

A corrupted cache causes Chrome to repeatedly try loading a broken cached version of a page rather than fetching it fresh from the server. This usually manifests as specific sites failing while others work — the cached data for those specific sites is corrupted. Ctrl + Shift + Delete → All time → Cached images and files + Cookies and other site data → Clear data → restart Chrome.

The restart matters — Chrome loads cached resources into memory at startup, and clearing without restarting may not immediately fix pages that were already cached in memory.

Fix 2: Flush DNS and Reset the Network Stack

If pages fail in Chrome AND in other browsers, the problem is Windows’ network stack, not Chrome. The DNS cache stores name-to-IP translations, and when these go stale or corrupt, all browsers fail. The network stack commands reset everything from the socket layer up:

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

Run these in an administrator Command Prompt and restart the PC. In most cases of “Chrome can’t load anything,” running these five commands resolves it — they’re the most reliable fix for network-layer problems that affect all browsers simultaneously.

Fix 3: Extensions (The Most Common Cause of Site-Specific Failures)

Ad blockers, VPN extensions, privacy tools, and developer tools all intercept page requests and can block specific resources that pages need to load. If pages fail consistently in normal Chrome but work in Incognito — or if specific sites that others can reach are consistently blocked — an extension is almost certainly the cause.

The fastest confirmation: open chrome://extensions, toggle every extension off, restart Chrome, and test the failing page. If it loads, an extension was blocking it. Re-enable them one at a time — after each re-enable, reload the failing page. When the page breaks again, you’ve found the culprit. Either disable that extension, update it, or adjust its settings to allow the site.

Privacy Badger, uBlock Origin in strict mode, and VPN extensions are the most common sources of pages loading partially or not at all on specific sites.

Fix 4: Chrome’s net-internals for Precise Diagnosis

When the basic fixes don’t resolve it and you need to understand exactly what’s failing, Chrome has a built-in network diagnostics tool that shows the complete connection attempt in real time:

Navigate to chrome://net-internals/#events in Chrome. Click Record, then open the failing page in another tab. Stop recording and filter by the failing URL. The event log shows exactly which step failed — DNS lookup, TCP connection, SSL handshake, or HTTP response. This five-minute diagnostic tells you the precise failure point, which directly identifies the correct fix.

Also check chrome://net-internals/#dns to see Chrome’s DNS cache state and whether DNS lookups are succeeding or failing. Chrome maintains its own DNS cache independently from Windows — clearing it here is sometimes needed even after flushing Windows’ cache.

Fix 5: Proxy Settings

A misconfigured proxy is a common cause of Chrome not loading pages on machines that move between networks — particularly machines that connected to a corporate network with a proxy, then came home where the proxy is unreachable. Chrome uses Windows’ proxy settings by default.

Settings → Network and internet → Proxy. If “Use setup script” is enabled with a URL, or “Use a proxy server” is on with an address — and you’re not deliberately using a proxy — turn both off. Also check in Chrome: Settings → search “proxy” → Open your computer’s proxy settings (this opens the same Windows settings). A stale proxy configuration after leaving a corporate network explains why Chrome can’t reach anything at home even though the Wi-Fi connection appears normal.

Fix 6: QUIC Protocol Blocking

Chrome uses Google’s QUIC protocol (over UDP) for connections to Google services and some other sites. Some routers, firewalls, and ISPs block UDP traffic in ways that cause Chrome to fail on Google sites (Gmail, YouTube, Google search) while other sites load normally. If you notice this specific pattern, disable QUIC:

Navigate to chrome://flags/#enable-quic → set “Experimental QUIC protocol” to Disabled → Relaunch Chrome. If the previously failing Google sites now load, your network blocks QUIC. Leave it disabled or adjust your router’s firewall to allow UDP on ports 80 and 443.

Fix 7: Hardware Acceleration Causing Blank Pages

Hardware acceleration uses the GPU to render pages. When the GPU driver has a bug in a specific rendering path, Chrome loads the page’s HTML and JavaScript but renders the visual output as a blank white or black page — the page technically loaded but can’t be displayed. This is distinct from the page failing to load at all.

Settings → System → toggle off “Use hardware acceleration when available” → Relaunch. If pages that were blank now display correctly, the GPU driver is the issue. Update the driver from Device Manager → Display Adapters → right-click GPU → Update driver. After updating, re-enable hardware acceleration — the updated driver usually resolves the rendering bug.

Fix 8: Antivirus and Security Software

Security software with SSL inspection or web filtering intercepts Chrome’s connections. When it incorrectly blocks a site, or when its SSL interception conflicts with Chrome’s certificate pinning for specific domains, Chrome shows connection failures that look identical to network problems. The giveaway: the failures are selective (specific sites only, not everything), and they often produce SSL-related error codes rather than network error codes.

Test: temporarily disable your antivirus’s web filtering component (not full protection — just web filtering or SSL inspection if those are separate options). If the blocked sites load immediately, the security software is the cause. Add those sites to the antivirus exclusion list or disable HTTPS inspection for domains you trust.

Fix 9: Reset Chrome or Create a New Profile

When Chrome’s own configuration has accumulated corruption — misconfigured network settings, broken extension data, corrupted preferences — a profile reset or new profile gives you a clean starting point. Settings → Reset settings → Restore settings to their original defaults. This clears extensions (you’ll need to re-enable them) and resets all Chrome settings while keeping bookmarks and passwords.

For a more thorough clean start: create a new profile (click profile icon → Add → continue without signing in) and test loading pages in the new profile. If pages load immediately in a new profile but failed in the old one, the old profile has corruption. Sign into Google in the new profile to restore synced bookmarks and passwords, and rebuild your extensions from scratch — which is also an opportunity to be selective about which ones come back.

Our guide on ERR_SSL_PROTOCOL_ERROR covers the SSL-specific variant of loading failures in more detail. For Chrome not loading specifically on a new Windows installation or after a Windows update, our Windows update guide covers system file integrity issues that sometimes affect Chrome networking. Google’s Chrome network troubleshooting covers the chrome://net-export feature for creating shareable diagnostic logs when remote support is needed.

When Specific Sites Fail but Others Don’t

Site-specific failures (some pages load, others don’t) have a different diagnostic path than universal failures. The likely causes:

Hosts file blocking the domain: Open Notepad as administrator → File → Open → navigate to C:WindowsSystem32driversetchosts → change file filter to All Files → open. Any line that isn’t a comment (doesn’t start with #) and contains the failing domain is blocking it at the OS level. Delete that line, save, and the domain becomes reachable immediately.

Extensions with site-specific rules: Some privacy and ad-blocker extensions maintain their own site blocking lists that are separate from their general rules. Check each extension’s settings for site-specific blocks. uBlock Origin’s “My Filters” section, Privacy Badger’s per-site settings, and custom filter lists in ad blockers are common sources of unexpected site blocks.

Chrome’s Safe Browsing blocking the site: Chrome’s Enhanced Safe Browsing mode occasionally flags legitimate sites. If Chrome shows a “Dangerous site” warning before the page fails, Safe Browsing is the cause. Settings → Privacy and security → Security → switch from Enhanced Protection to Standard Protection to reduce false positives while maintaining reasonable protection.

Chrome Not Loading Pages After a Windows Update

Windows updates sometimes change network configuration in ways that affect Chrome specifically. The most common post-update Chrome loading failure causes are: the WinSock registry entries being reset (fix with netsh winsock reset), proxy settings being cleared or changed (check Settings → Proxy), or a network adapter driver being replaced with a less compatible version (check Device Manager for yellow triangles on network adapters).

Check Windows Update history (Settings → Windows Update → Update history) for the date the update was installed and compare to when Chrome stopped loading pages. If they match, the update is the cause. The network stack reset commands (Fix 2) resolve most post-update network issues. If those don’t help, rolling back the most recent update is worth trying to confirm whether the update is the culprit before spending time on other fixes.

Firewall Rules Blocking Chrome

Windows Defender Firewall maintains per-application outbound rules. Chrome should have these rules created automatically, but they occasionally get corrupted or deleted — particularly after Chrome updates that change the application path. Chrome then can’t make outbound connections and shows connection failures for all pages.

Check: search “Allow an app through Windows Firewall” → Change settings → find Google Chrome in the list → ensure both Private and Public are checked. If Chrome isn’t in the list at all, it needs to be added: Allow another app → browse to C:Program FilesGoogleChromeApplicationchrome.exe → Add → check both checkboxes → OK.

This is distinct from antivirus web filtering — it’s the Windows-level firewall that controls which applications can make network connections. Chrome getting removed from the allowed list explains loading failures that appear suddenly without any change to Chrome itself or its settings.

Chrome on a Corporate Network

On corporate or school networks, Chrome loading failures sometimes trace to group policy settings that were pushed to managed devices. Chrome’s policy settings can restrict which URLs Chrome is allowed to navigate to, force a specific proxy configuration, or block extensions that affect page loading. Navigate to chrome://policy to see all active policies — any URL-blocking or proxy policies appear here. On managed devices, these settings are controlled by IT and can’t be changed by the user; contact IT for exceptions when legitimate work sites are blocked.

Also relevant for corporate users: some corporate networks use SSL inspection that replaces TLS certificates with the corporate CA certificate. Chrome needs to trust this corporate CA to load HTTPS sites without SSL errors. If Chrome shows SSL errors on every HTTPS site on a corporate network but the same sites load fine at home, the corporate CA certificate needs to be imported into Chrome’s trust store — IT can do this through group policy automatically for managed devices.

One more scenario: Chrome loading pages on the first visit after startup but failing on subsequent visits within the same session. This specific pattern — works initially, then breaks — usually points to memory pressure. Chrome is consuming all available RAM over the session, and when memory runs out, it starts failing to load new pages rather than crashing visibly. Open Chrome’s task manager (Shift + Esc) and check total memory consumption — if it’s approaching the total available system RAM, close tabs and enable Memory Saver (Settings → Performance → Memory Saver) to prevent recurrence.