How Do I Fix Google Chrome Crashing on Startup?

Issue type: Software — Google Chrome closes immediately when launched, with no window appearing and no error message shown

SEO focus: If you are looking for google chrome crashing on startup, this guide starts with the fastest diagnosis, then moves to the exact fix that matches the symptom.

Short answer: Chrome crashing on startup is almost always a corrupted user profile or a broken extension that loads at launch — not a problem with the Chrome installation itself. Both can be fixed without uninstalling Chrome or losing your bookmarks. Start by launching Chrome with extensions disabled, then if needed, swap to a fresh profile temporarily to confirm the cause.

Google Chrome Crashing on Startup: Quick Diagnosis

Three different failure patterns all look like “Chrome crashing on startup” but have different fixes:

Chrome icon flashes briefly then disappears with no window appearing: The Chrome process is starting and crashing immediately during initialization. This is almost always a corrupted user profile or a broken extension trying to load before the browser window is rendered. The profile rename fix below is the targeted resolution.

Chrome shows a window briefly then closes within 1–2 seconds: A startup tab is causing the crash — usually because the page was last open in a state that crashed Chrome, and Chrome tries to restore it. The browser opens, attempts to load the saved session, and crashes again. Holding Shift while launching prevents session restore.

Chrome opens and runs for several seconds before crashing: A specific extension is causing the crash after it finishes loading. Launch Chrome in safe mode (no extensions) to confirm.

Open Task Manager (Ctrl + Shift + Esc) and look at the Processes tab while you try to launch Chrome. If multiple chrome.exe processes appear and then disappear within seconds, Chrome is starting and crashing in a loop. The Windows Event Viewer also logs the crash — go to Event Viewer > Windows Logs > Application and filter for “Application Error” with chrome.exe as the source.

What to do first

1. Launch Chrome with extensions disabled to test for an extension conflict. Right-click the Chrome shortcut > Properties > in the Target field, add --disable-extensions at the very end (with a space before the two dashes). Click Apply. Try launching Chrome — if it opens successfully now, an extension is causing the crash. Go to chrome://extensions and disable all extensions, then re-enable them one at a time, restarting Chrome between each, until it crashes again. The last extension you enabled is the culprit.
2. Rename the Chrome user profile to test for profile corruption. Close Chrome completely (check Task Manager for any remaining chrome.exe processes and end them). Press Win + R and type %LocalAppData%GoogleChromeUser Data and press Enter. Find the folder named Default — rename it to Default.old. Launch Chrome. It creates a fresh Default folder automatically and launches with a clean profile (no bookmarks, no extensions, no saved passwords). If Chrome opens normally with the new profile, your original profile is corrupted.
3. If the new profile works, recover your data from the old profile. Open the renamed Default.old folder. Important files to recover: Bookmarks (no extension — just the file named Bookmarks), Login Data, History, and Preferences. Copy these one at a time into the new Default folder, restarting Chrome between each to verify it still launches. The file that causes Chrome to crash when copied is the source of the corruption — leave that one behind.
4. Disable hardware acceleration if Chrome crashes after a few seconds of running. Launch Chrome (with the –disable-extensions flag if needed). Go to chrome://settings/system and toggle off “Use hardware acceleration when available.” Restart Chrome. A faulty GPU driver or a Chrome update with a graphics rendering bug commonly causes crashes that look like a startup issue but actually happen during the first frame render.
5. Disable Chrome’s startup tab restore. Launch Chrome with the –disable-extensions flag, then go to chrome://settings/onStartup and select “Open the New Tab page” instead of “Continue where you left off.” This prevents Chrome from trying to restore the previous session, which can be the source of a crash if any of the previously open tabs were in a broken state when Chrome last closed.
6. Reset Chrome to default settings if the above steps don’t help. Open Chrome (with –disable-extensions if needed) and go to chrome://settings/reset > click “Restore settings to their original defaults.” This disables extensions, clears temporary site data, resets your startup page and search engine, but keeps bookmarks, history, and saved passwords. If Chrome is also showing the broader “not opening” issue, this reset addresses both patterns. Also check Chrome’s RAM usage — extreme memory consumption from a runaway extension can trigger crashes on launch as Chrome tries to restore tabs.

Common mistake

Uninstalling and reinstalling Chrome immediately when it crashes on startup. The standard Chrome uninstaller deliberately leaves your user data in place — the Default profile folder, including any corruption causing the crash, survives the reinstall. When you reinstall and launch Chrome, it loads the same corrupted profile and crashes again. A reinstall only works as a fix if you also manually delete the %LocalAppData%GoogleChromeUser Data folder before reinstalling — which destroys all your bookmarks, passwords, and history. The profile rename approach above achieves the same isolation without that data loss.

Best next step

If Chrome still crashes after disabling extensions and creating a fresh profile, the issue is likely outside Chrome itself — antivirus software interfering with Chrome’s sandbox process is the most common cause. Temporarily disable real-time protection in Windows Security and try launching Chrome. If it opens, add Chrome’s installation folder (typically C:Program FilesGoogleChromeApplication) and the User Data folder to your antivirus exclusion list. Specifically problematic with Chrome: Avast, AVG, and Webroot have all caused documented Chrome startup crashes through their browser protection modules. If a third-party antivirus is installed, check its settings for a “browser protection” or “web shield” feature and disable it as a test.

Official reference: For official Windows troubleshooting guidance, check Microsoft’s Windows support page before downloading third-party repair tools or changing advanced settings.

Quick Q&A

Chrome crashes only on my user account but works fine on another Windows account. What does that mean?

It confirms the Chrome installation itself is healthy — the problem is specific to your user account’s Chrome profile or user-level settings. Since each Windows user has their own Chrome user data, your corruption is contained to your account. Use the profile rename method described in step 2 to create a clean Chrome profile within your account. You don’t need to switch Windows accounts — just rebuild the Chrome profile under your existing user.

I see “Chrome didn’t shut down correctly” every time I launch. Is that related to the crash?

Yes — it’s both a symptom and a contributor. Chrome detects that the previous session ended unexpectedly and offers to restore tabs. If the tabs that crashed Chrome last time are loaded again, Chrome crashes immediately and the cycle continues. When you next see this message, click the “X” to dismiss it without restoring tabs. If the dialog itself appears too briefly to interact with, launch Chrome with the --no-startup-window flag temporarily, then change the startup setting to “Open the New Tab page” before allowing Chrome to handle session restore again.

After fixing the crash, my saved passwords and bookmarks are gone. Can I get them back?

If you renamed the Default folder to Default.old (as in step 2), your data is still there — just not loaded in the new profile. To restore: close Chrome, navigate to %LocalAppData%GoogleChromeUser Data, copy the Bookmarks file from Default.old into the new Default folder. Do the same for “Login Data” (your saved passwords) — but copy it while Chrome is fully closed. Launch Chrome and your data should appear. If you signed into Chrome with a Google account before the crash, your passwords and bookmarks are also stored in Google’s sync — sign in to recover them.