Troubleshooting Steps
- Restart Chrome completely — close every Chrome window and check Task Manager for lingering
chrome.exeprocesses, since a stuck background process can cause this on relaunch. - Disable hardware acceleration — go to
chrome://settings/systemand turn off “Use hardware acceleration when available,” then restart Chrome. GPU driver issues are a common cause of crash-on-launch. - Disable extensions — launch with
chrome.exe --disable-extensionsor check viachrome://extensionsin a working profile; a misbehaving extension can crash the browser on startup. - Create a new Chrome profile — a corrupted user profile is a very common cause. Create a new profile and see if it opens cleanly; if it does, your original profile’s data is the problem.
- Reinstall Chrome — uninstall completely (including leftover data in
%LocalAppData%\Google\Chrome, backing up bookmarks first if needed) and reinstall the latest version.
At Scale (Group Policy)
If this is hitting multiple users at once, check whether a recent Chrome auto-update or a Group Policy change (particularly around hardware acceleration or extension allow/block lists) rolled out around the same time — a policy pushed via GPO that’s incompatible with the current Chrome version is a common cause of a fleet-wide, simultaneous onset of this issue.Still Current in 2026
All five steps above remain valid, current troubleshooting guidance — Google’s own support documentation still lists disabling extensions and a full uninstall/reinstall as standard fixes for this class of crash. Chrome’s current stable channel is version 152 (released August 2026), so if you’re troubleshooting a machine running something noticeably older, updating first is worth trying before working through the rest of this list — an out-of-date build is itself a common cause of crash-on-launch behaviour.Resources
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.