The internet is clearly alive - other apps work, the Wi-Fi is connected - yet Chrome cannot open a single page. That contradiction is the clue: the fault is in one specific layer between Chrome and the website.
When pages fail but the internet is fine, the failure sits in one of three places: DNS (names are not turning into addresses), a stuck proxy (Chrome is being sent through a dead middleman), or Chrome's own network settings. Guessing wastes the evening; the split test below names the layer in about two minutes, and each layer has its own short fix. Notably, two of the fixes - the DNS flush and the network stack reset - are exactly what the repair script in the video automates.
Chrome tells you what failed; most people never read it. ERR_NAME_NOT_RESOLVED and DNS_PROBE_FINISHED_NXDOMAIN mean your PC could not turn the site's name into an address - a DNS fault. ERR_PROXY_CONNECTION_FAILED means Chrome is trying to talk through a proxy that is not answering. ERR_CONNECTION_RESET or ERR_TIMED_OUT mean the name resolved but the road to the server was blocked or dropped. Write the code down - the next steps follow from it, not from guessing.
Open Edge or Firefox and try the same site. If they fail too, the fault is the PC's network or the connection - not Chrome. Then check your phone on the same Wi-Fi: if the phone also fails, it is the router or the provider; if the phone works, the fault lives inside this one PC. Two minutes of testing here saves an hour of fixing the wrong thing. Only when other browsers work and Chrome alone fails do you suspect Chrome's own settings - its secure DNS option or a proxy extension.
This is the pair the repair script in the video runs automatically. By hand: open Command Prompt as administrator and run, in order:
ipconfig /flushdns - empties the saved name-to-address notebooknetsh winsock reset - rebuilds the Winsock cataloguenetsh int ip reset - rebuilds the TCP IP stackStale DNS entries and a stack damaged by old VPN or security software are the two most common causes of the internet-works-but-Chrome-does-not complaint, and this is their fix.
In Chrome: Settings, then System, then Open your computer's proxy settings. If a manual proxy is switched on and you never set one, that is your fault found - leftover VPN tools, office configurations brought home and some unwanted software all leave dead proxies behind, and Chrome obediently sends every page to a server that no longer exists. Turn the manual proxy off (or set detection to automatic) and test. While there, check chrome://settings/security - the Use secure DNS option: if only Chrome fails while Edge works, try a different secure DNS provider or switch the option off as a test.
If the flush fixed nothing and the errors are DNS errors, your provider's DNS server may itself be failing or slow. Set the network adapter's DNS to a public resolver such as 1.1.1.1 or 8.8.8.8 and test. Honest framing: this changes who answers name lookups - it fixes name failures and can make pages start sooner, but it does not make a slow connection faster. And on an office PC, ask IT first: internal names - servers, printers, intranet - resolve through the office DNS, and a public DNS can fix the internet while quietly breaking the office.
The custom Chrome repair script in action - 15 common Chrome problems fixed in about a minute, shown live, step-by-step.
Watch Full VideoYour PC cannot turn website names into addresses - a DNS failure. Flush the DNS cache, reset the network stack, restart, and if it persists, set a different DNS server such as 1.1.1.1.
Inside Chrome's own settings. Check Chrome's Use secure DNS option, look for a proxy extension, and if needed reset Chrome settings - the PC's networking is proven healthy by the other browser.
It can make pages start loading sooner when your old DNS was slow or failing, because the lookup finishes quicker. It does not increase your connection speed itself.