Smart Home & Tech
Chrome Is Not Loading Pages: A Practical Troubleshooting Guide for Windows
If every device fails, fix the network. If only Chrome fails, test Incognito before you touch DNS or reset Windows networking.
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
-
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.
-
If yes
-
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.
-
If yes
-
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.
-
If yes
Ordered fixes
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
Chrome not loading pages means the window is open and a site never arrives: a spinner, an error, or a blank document. A window that will not appear is Chrome not opening. A page that arrives slowly is slow Chrome. A black painted window is a black screen. Before you reset anything inside Windows, find out whether any other device can load the site.
Do not flush DNS, reset Winsock, or edit a proxy in the registry from this page. Those repairs are easy to run and hard to undo, and they are the wrong tool when only one browser fails. A VPN your work requires stays on unless the employer says you may pause it.
Step 1: One site, or every site, and not only Chrome
- Try a second public site in Chrome. One site failing may involve that site, Chrome’s stored data, or an extension. Every site failing calls for the next test.
- Try the same site in another browser on the PC, and on a phone with Wi-Fi and then with cellular data if you have it. Turn cellular off when you mean to test Wi-Fi.
- If many public sites fail on the phone over the same Wi-Fi and in another browser, stop and use connected but no internet. If only one site fails even on cellular data, that site may be unavailable; do not reinstall Chrome for it.
Step 2: Incognito, then extensions
If other browsers work and Chrome does not, open an Incognito window. Incognito turns most extensions off. If the site loads there, an extension or stored site data is a likely cause. Turn extensions off at chrome://extensions and test again in a normal window, one extension at a time, as in extensions not working. A VPN-style extension you do not remember installing is a prime suspect. Remove it. Do not “fix DNS” while Incognito already proved the network works.
If Incognito also fails and other browsers work, the Chrome profile is next, not the router.
Step 3: A proxy or a VPN you are allowed to change
If you personally turned on a VPN, pause it only if you are allowed to, and reload. If the page loads, the VPN path was the failure. Turn it back on if you still need it, or leave it off if you do not. A proxy you did not set, visible in Chrome’s current proxy or system-proxy screen, should be turned off only on a PC you administer. A work proxy stays. Ask the administrator. Do not delete proxy settings in the registry to get around a work network.
Step 4: A new profile, not a Windows network reset
Create a new Chrome profile and try the site before you uninstall. Export bookmarks if sync is off and the old window still opens. Reinstall from Google’s own download page only if the new profile also fails while another browser on the same PC succeeds. Hardware acceleration and Chrome flags do not belong in a page-load failure. Flags stay at their defaults. A Windows Security scan is appropriate if an extension you do not recognize was the cause. Protection stays on.
Where the failure actually is
- One site versus every site, written down.
- Another browser and a phone tested, so a dead network is not treated as a Chrome bug.
- Incognito tested before any DNS or Winsock command.
- A VPN paused only if you are allowed to pause it.
- A work proxy or a managed browser left for the administrator.
Example: only Chrome fails, Incognito works
A news site will not load in Chrome. Edge loads it. A phone on the same Wi-Fi loads it. Incognito in Chrome loads it. They turn extensions off and the normal window loads. Turning one “privacy” extension back on breaks the site again. They remove that extension. They do not reset Windows networking and they do not change DNS. The extension is this failure. If the phone had failed too, they would have followed the network guide and left Chrome installed as it was.
Related guides
Last updated: October 28, 2026
Last reviewed October 22, 2026. Suggest a correction
Questions readers ask
Should I flush DNS or reset Winsock?
Not from this page. If every device fails, use the network guide. If only Chrome fails, Incognito and extensions come first. A networking reset is not the Chrome repair.
Incognito works. What does that mean?
The network and the PC can load the site. An extension or data in the normal profile is the likely cause. Test extensions one at a time.
Every browser fails, including my phone. Is Chrome broken?
If many sites fail in another browser and on the phone over the same Wi-Fi, check the connection. If only one site fails on cellular data too, that site may be unavailable. Reinstalling Chrome is not the first step.
I use a work VPN. Should I turn it off?
Only if the employer allows that. A required VPN stays on. Ask them if pages fail only while it is connected.
Will a new profile delete my passwords?
The old profile remains until you remove it. If sync is off, the new profile starts empty. Check your saved-password and sync status before deleting anything; follow Chrome’s current export guidance only if you need a backup.
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.
- Fix connection and loading errors in Chrome — Google Chrome Help (documentation), accessed October 27, 2026. Official sequence compares sites and connection, then Incognito, extensions, browsing data, security software, and profile/reset paths.
- Get help with common error messages in Chrome — Google Chrome Help (documentation), accessed October 27, 2026. Distinguishes site, connection, and page crash symptoms; a failed page alone does not prove an ISP outage.
Information on this site is for general educational purposes and is not professional advice.
Parent topic: Smart Home & Tech