Fixing Chrome by hand takes 10 to 15 minutes of repeating the same resets. This page is the whole routine in one place: the actions a repair script runs, what each one actually changes on your PC, what you keep and what you lose, and the honest line where a script stops and real diagnosis begins.
Chrome problems arrive wearing fifteen different masks, but most of them share a small set of causes - a tired cache, a stale DNS entry, a setting that needs resetting, a network stack left damaged by other software. In the video, Technical Anshu shows the custom repair script he uses in his own IT work: one run covers Chrome not opening, Chrome crashing and slow performance, and it resets Chrome settings, clears the cache and temp files, flushes DNS and resets the Windows network stack. Below, every one of those actions is explained in plain words, so you know exactly what the routine does before you run anything - his script, or the same steps by hand.
In the video, Anshu explains why he built it: in his IT support work, fixing Chrome by hand took 10 to 15 minutes every time - the same clicks, the same resets, the same order. So he wrote a custom Chrome repair script that runs the whole routine in one click, in about a minute. The script link is given with the video (a Google Drive link), and the fix list published with it is: Chrome not opening, Chrome crashing, Chrome slow performance, reset Chrome settings, clear cache, clear temp files, flush DNS and reset the network stack. Fifteen common problems, one short list of real actions.
One honest rule before you run any script, his or anyone else's: a script runs with your full permission on your PC, so only ever use one from a source you trust - in this case, the link under his own video, never a random re-upload. And if you prefer not to run scripts at all, every action below can be done by hand in the same order. The script's value is speed, not magic.
This is the heavy lifter of the routine. Chrome's own reset (Settings, then Reset, then Restore settings to their original defaults) puts every setting back the way Chrome shipped: startup pages, the new tab page, the default search engine and pinned tabs all return to defaults, and all extensions are switched off. It also clears cookies and site data, which is why websites ask you to sign in again afterwards.
What it does not touch matters just as much: your bookmarks, browsing history and saved passwords are kept. That split is why the reset fixes so much - hijacked homepages, a search engine you never chose, bad settings left by old software - while costing you nothing personal. The sign-outs are an inconvenience, not data loss, and your saved passwords will fill the login forms back in.
The cache is Chrome's local store of site files - images, scripts and styles it keeps so pages load faster next time. When those stored copies go stale or get damaged, pages render broken, buttons stop responding or a site shows you an old version of itself. Clearing the cache forces Chrome to fetch fresh copies of everything. Done on its own, cache clearing removes cached images and files only - not your logins, not your passwords, not your history.
Temp files are the Windows side of the same idea: the leftover working files in the temp folders that installers and programs abandon. Removing them frees space and clears out half-finished junk that can confuse a fresh install or update. Neither action is a deep clean of your life - both are the digital equivalent of emptying the workshop bin.
Your PC keeps a notebook of DNS answers - which server name lives at which address. When an entry in that notebook goes stale, Chrome drives confidently to a dead address and the page fails while the internet itself is fine. The command ipconfig /flushdns empties the notebook so every name is looked up fresh.
The network stack reset goes one layer deeper. netsh winsock reset and netsh int ip reset rebuild the Windows networking plumbing that VPN tools, proxies and security software sometimes leave damaged. These two need an admin Command Prompt and a restart to take effect. Together, the DNS flush and the stack reset are the pair that fix the classic complaint: everything else online works, but Chrome cannot open pages.
A repair routine only repairs what it touches. It will not fix a profile so damaged that Chrome crashes while loading it, an extension that reinstalls itself, real malware, a failing hard drive, too little RAM, or an internet connection that is down for the whole house. It also cannot undo settings that an office policy enforces - those return by design.
So treat the routine as the correct first move, not a ritual to repeat. If Chrome is still broken after one clean run, stop and diagnose by symptom instead: the case pages in this guide cover Chrome not opening at all, crashes on one website, rogue extensions, office policy locks and the PC-level impostors that pretend to be Chrome faults. One run fixes the known causes. What survives it is information - it tells you the problem lives somewhere else.
The custom Chrome repair script in action - 15 common Chrome problems fixed in about a minute, shown live, step-by-step.
Watch Full VideoIt performs only the standard actions listed on this page - reset Chrome settings, clear the cache and temp files, flush DNS and reset the network stack. Download it only from the link in Technical Anshu's own video description, never from a re-upload or a random site, because any script runs with full permission on your PC.
No. A Chrome settings reset does not delete bookmarks, browsing history or saved passwords. It restores default settings, disables extensions and clears cookies and site data, so websites will ask you to sign in again - and your saved passwords will fill those sign-ins back in.
Then the cause sits outside the routine - most often a corrupt profile, a self-reinstalling extension, an office policy, or a PC problem like low memory or a failing drive. Work through the case page that matches your exact symptom rather than running the routine again.