Smart Home & Tech

Chrome Is Not Loading Pages: A Practical Troubleshooting Guide for Windows

By Tech Home Tips Editors Published October 5, 2026 Updated October 5, 2026 5 min read Report a correction

When Google Chrome stops loading pages on Windows, the cause is often a network hiccup, a misbehaving extension, or a corrupted cache. This guide walks through a logical sequence of checks — from connection basics to browser-specific resets — so you can restore browsing without guesswork.

Direct answer

Google Chrome on Windows fails to load web pages, showing errors like 'This site can't be reached,' blank tabs, or endless loading spinners.

Before you start

Verify the issue is Chrome-specific by testing with another browser. Some steps clear local browsing data; sync critical passwords/bookmarks to your Google account first. Network reset commands require Administrator privileges.

Diagnostic checks

  1. Do other browsers (Edge, Firefox) load pages on the same device?

    • If yes

      Proceed with Chrome-specific steps (Incognito, extensions, cache, DNS, profile, reinstall).

    • If no

      Troubleshoot the network layer first: restart modem/router, check ISP status, test with another device. See internal guide: Connected to Wi-Fi but No Internet? 12 Ways to Fix It.

  2. Do pages load in an Incognito window (Ctrl+Shift+N)?

    • If yes

      Cause is likely an extension or cached data. Disable all extensions, then clear cache and cookies.

    • If no

      Cause is deeper: DNS/system network stack, Chrome flags, hardware acceleration, or profile corruption. Continue to DNS flush and Winsock reset.

  3. Does a new Chrome profile load pages?

    • If yes

      Original profile is corrupted. Migrate data to the new profile via Sync.

    • If no

      Try disabling hardware acceleration and resetting chrome://flags. If still failing, perform a clean reinstall.

Ordered fixes

  1. Verify Network Layer

    Restart modem and router. Confirm other devices work. Disable VPN/proxy. Run a speed test.

    Expected: Other browsers and devices load pages normally. If not, fix network first.

    Do not proceed with Chrome steps if the network itself is down.

  2. Test in Incognito Mode

    Press Ctrl+Shift+N. Try the failing sites.

    Expected: Pages load → extension or cache issue. Pages fail → deeper Chrome or system issue.

    Incognito does not test hardware acceleration or profile corruption.

  3. Disable Extensions and Clear Browsing Data

    Visit chrome://extensions/, toggle all off. Reload. If fixed, re-enable one by one. Then clear cache and cookies for 'All time' at chrome://settings/clearBrowserData.

    Expected: Pages load after clearing data or identifying the bad extension.

    Clearing cookies signs you out of sites. Ensure passwords are synced or exported.

  4. Flush DNS and Reset Winsock

    Open Command Prompt as Administrator. Run: ipconfig /flushdns, netsh winsock reset, netsh int ip reset. Reboot Windows.

    Expected: Chrome resolves domains and connects normally after reboot.

    Commands require Admin rights. Run in order; reboot is mandatory after netsh int ip reset.

  5. Reset Chrome Flags and Toggle Hardware Acceleration

    Go to chrome://flags → 'Reset all'. Go to chrome://settings/system → turn off 'Use graphics acceleration when available'. Relaunch.

    Expected: Pages render without GPU-related blank screens or crashes.

    Disabling acceleration may increase CPU usage on video-heavy sites.

  6. Create a New Chrome Profile

    Click profile avatar → Add → 'Continue without an account'. Name it. Test in the new window.

    Expected: New profile works → original profile corrupted. Migrate via Sync.

    Local-only data (unsynced passwords, history) stays in the old profile.

  7. Clean Reinstall Chrome

    Uninstall via Settings → Apps → Installed apps → Google Chrome → Uninstall. Optionally check 'Also delete your browsing data'. Download and install fresh from google.com/chrome.

    Expected: Fresh install loads pages without errors.

    Deleting browsing data removes local profile files permanently if not synced.

Provider or service issues

If Chrome works on other networks (hotspot, neighbor Wi-Fi) but not yours, the issue may be ISP DNS, captive portal, or router firmware. Set public DNS (1.1.1.1 or 8.8.8.8) in Windows adapter settings or router. Update router firmware. Contact ISP with specific Chrome error codes (ERR_NAME_NOT_RESOLVED, ERR_CONNECTION_TIMED_OUT) if the problem persists across devices.

Understanding the Problem

Google Chrome on Windows may fail to load pages for several reasons. The browser might be unable to reach the internet, a specific site could be blocked by an extension or security software, or Chrome's own data (cache, cookies, or profile) may have become corrupted. Because the symptoms look similar — blank tabs, "This site can't be reached," or endless spinning — a step-by-step approach helps isolate the cause quickly.

Before You Start

Confirm the issue is specific to Chrome. Open Microsoft Edge or Firefox and try the same sites. If they also fail, the problem is likely your network or internet service, not Chrome. In that case, start with Connected to Wi-Fi but No Internet? 12 Ways to Fix It to rule out router, modem, or ISP issues. If other browsers work, continue with the Chrome-focused steps below.

Caution: Some steps clear browsing data or reset settings. Bookmarks and saved passwords synced to your Google account will remain, but local-only data may be lost. Export passwords or note critical site data before proceeding if you are unsure.

Step 1: Check Network Basics

  • Restart your modem and router: unplug both, wait 30 seconds, plug in the modem first, then the router.
  • Verify other devices on the same network can load pages.
  • If you use a VPN or proxy, disable it temporarily. Corporate VPNs often split-tunnel traffic in ways that break Chrome's DNS resolution.
  • Run a quick speed test to confirm the connection is active. For a structured approach, see How to Test Your Home Wi-Fi: A Practical Step-by-Step Guide.

Expected result: Other devices and browsers load pages normally. If not, resolve the network layer first.

Step 2: Test Chrome in Incognito Mode

Press Ctrl + Shift + N to open an Incognito window. Try the problematic sites. Incognito disables most extensions and uses a separate cookie jar. If pages load here, an extension or cached data is the likely culprit.

Expected result: Pages load in Incognito → proceed to Step 3. Pages still fail → proceed to Step 4.

Step 3: Disable Extensions and Clear Cache

  1. Open chrome://extensions/.
  2. Toggle every extension off.
  3. Reload the page. If it works, re-enable extensions one by one, testing after each, to identify the offender.
  4. If no single extension is to blame, clear browsing data: chrome://settings/clearBrowserData → choose "All time" → check "Cached images and files" and "Cookies and other site data" → Clear data.

Expected result: Pages load after clearing data or disabling the problematic extension.

Step 4: Flush DNS and Reset Winsock (Windows)

Open Command Prompt as Administrator (right-click Start → Terminal (Admin) or Command Prompt (Admin)). Run each command, pressing Enter after each:

  • ipconfig /flushdns
  • netsh winsock reset
  • netsh int ip reset

Restart Windows after the last command. This clears the system DNS cache and resets the network stack, which can fix "DNS_PROBE_FINISHED_NXDOMAIN" or "ERR_CONNECTION_RESET" errors that only appear in Chrome.

Expected result: Chrome loads pages after reboot.

Step 5: Check Chrome Flags and Hardware Acceleration

Type chrome://flags in the address bar. If you have ever enabled experimental features, click "Reset all" at the top. Next, go to chrome://settings/system and toggle "Use graphics acceleration when available" off. Relaunch Chrome when prompted. Hardware acceleration can conflict with certain GPU drivers, causing blank pages or crashes.

Expected result: Pages render correctly with acceleration disabled.

Step 6: Create a New Chrome Profile

A corrupted user profile can break page loading while leaving the browser otherwise functional. Click your profile avatar (top right) → Add → "Continue without an account" → give it a name. Test in the new profile window. If it works, your original profile has damaged preferences or databases. You can sync the new profile to your Google account to restore bookmarks and passwords.

Expected result: New profile loads pages → migrate data to the new profile.

Step 7: Reinstall Chrome

If nothing above works, uninstall Chrome via Settings → Apps → Installed apps → Google Chrome → Uninstall. Check "Also delete your browsing data" if you want a completely clean slate. Download the latest installer from google.com/chrome and install fresh.

Expected result: Fresh install loads pages normally.

Common Mistakes to Avoid

  • Skipping the Incognito test and jumping straight to reinstall — wastes time if the cause is a single extension.
  • Clearing only "Cached images" but leaving cookies — some site breakage persists until both are cleared.
  • Running network reset commands without Administrator rights — they silently fail.
  • Assuming the problem is Chrome when the router's DNS is failing — usually verify with another browser first.

When to Seek Help

Stop and contact your IT department or a qualified technician if:

  • Chrome crashes immediately on launch (possible malware or corrupted binary).
  • Pages load but show certificate errors on every site (system clock wrong, MITM proxy, or antivirus TLS interception).
  • You are on a managed device and Group Policy prevents changes to Chrome settings.
  • The issue returns after every reboot, suggesting a deeper OS or driver problem.

Provider or Service Issues

If Chrome works on other networks (phone hotspot, neighbor's Wi-Fi) but not yours, the issue may be your ISP's DNS, a captive portal, or router firmware. Try setting a public DNS (e.g., 1.1.1.1 or 8.8.8.8) in Windows network adapter settings or in the router. Check the router admin page for firmware updates. If the problem persists across devices, contact your ISP support and reference the specific error codes Chrome displays (e.g., ERR_NAME_NOT_RESOLVED, ERR_CONNECTION_TIMED_OUT).

Last reviewed October 5, 2026. Suggest a correction

Sources and methodology

Claims that depend on an outside authority are tied to the references below. Product details change. Confirm the current specification sheet before you buy or install anything.

  1. Securing Wireless Networks — CISA (government), accessed October 5, 2026. General guidance on securing wireless networks, relevant when ruling out network-level causes for Chrome page-load failures.
  2. Guidelines for Securing Wireless Local Area Networks (WLANs) — NIST (government), accessed October 5, 2026. NIST guidelines for securing WLANs, useful context for router firmware and DNS configuration steps mentioned in the provider issues section.

Information on this site is for general educational purposes and is not professional advice.

Parent topic: Smart Home & Tech