If Chrome closes or freezes just after you choose a profile, the problem may be in that profile’s data, an extension, graphics settings, or the browser installation itself. These ten fixes move from quick tests to more involved recovery steps, and are for anyone trying to get Chrome working again without accidentally erasing bookmarks or other important data.
1. Test with Guest mode or a new profile
If Chrome’s profile chooser appears, try Guest mode if it is offered; Guest uses a temporary browsing session rather than loading the affected profile’s usual data and extensions. If Guest works, or a newly created profile opens successfully, that is a useful sign that Chrome can run and that the problem is more likely tied to the original profile than to the whole installation. Create a separate profile from the chooser and test it before changing anything in the damaged one. Do not delete the old profile just because the new one works; you may still need its local bookmarks, settings, or files.
2. Start Chrome with extensions disabled
An extension can crash the browser while Chrome is loading a profile, even if you cannot keep the affected window open long enough to remove it. Close Chrome completely, then try launching it with the --disable-extensions command-line switch; the exact way to add a switch depends on your operating system and how Chrome was installed. If Chrome stays open this way, visit chrome://extensions, turn extensions off, and restart normally. Re-enable them one at a time, restarting between tests, so you can identify a particular extension instead of removing them all permanently.
3. Update Chrome and restart the computer
A browser update can fix a crash caused by a bug in an earlier Chrome release, while a computer restart clears stuck Chrome processes that may remain after a failed launch. If you can open Chrome using Guest mode or a test profile, go to chrome://settings/help and let it check for updates; restart the browser if prompted. If no profile will stay open, use Google’s official Chrome download page to obtain the current installer for your operating system, then install over the existing app without choosing an option to erase browsing data. Also install pending operating-system updates, especially if the crashes began after a system or graphics-driver change.
4. Check whether graphics acceleration is involved
Chrome uses the computer’s graphics hardware for some page rendering, and a graphics-driver or hardware-acceleration problem can make a browser window crash or go blank. If you can open Chrome with another profile, go to Settings, then System, and switch off Use graphics acceleration when available; relaunch Chrome to test the change. If the setting is unavailable because the affected profile will not open, a technically comfortable user can test a launch with the --disable-gpu switch, then remove that switch after the test. A successful test points toward the graphics path, but it does not prove the graphics card is faulty; update the driver through the computer or graphics-card maker’s supported method.
5. Back up the profile, then test a fresh copy
If the crash follows one profile, damaged profile files are a possibility, but changing them without a backup can make recovery harder. Close every Chrome window and process first, then copy the Chrome user-data folder to a separate location: on Windows it is usually under %LOCALAPPDATA%\Google\Chrome\User Data, on macOS under ~/Library/Application Support/Google/Chrome, and on Linux under ~/.config/google-chrome for Google Chrome. After confirming the copy exists, you can rename the affected profile folder, commonly Default for the first profile or Profile 1 for another, and let Chrome create fresh profile data for testing. Keep the renamed folder and backup; do not overwrite them, and remember that locally stored passwords or other protected data may not transfer simply by copying files.
6. Clear rebuildable cache folders
Temporary cache files can occasionally be part of a launch problem, and Chrome can rebuild its ordinary cache after those files are removed. With Chrome fully closed, locate the affected profile folder inside the user-data folder and, if present, remove only its Cache, Code Cache, and GPUCache folders. Do not delete the entire profile folder or files such as Bookmarks and Login Data as a cache-cleaning shortcut. If you are unsure which profile folder belongs to the affected account, make a separate backup first and use a newly created profile as the safer diagnostic test.
7. Reset Chrome settings from a working profile
If Chrome stays open in Guest mode or a separate profile, you can test a settings reset in the profile that is having trouble by opening chrome://settings/reset and choosing the option to restore settings to their original defaults. This turns off extensions and resets settings such as the startup page, search engine, and content settings, so it can undo a harmful configuration without requiring a full reinstall. Chrome’s reset does not remove bookmarks or saved passwords, but it is still sensible to keep a backup before troubleshooting. If you cannot open the affected profile at all, this step cannot be applied to it from another profile; do not assume resetting a different profile repairs the one that crashes.
8. Check storage space and access to the profile folder
A nearly full system drive can prevent Chrome from writing temporary files, and changed folder permissions can stop it from reading or updating profile data. Check that the drive containing Chrome’s user-data folder has free space, then confirm you are signed into the same computer account that normally uses that profile. Avoid changing permissions across the whole drive or running a cleanup tool that deletes Chrome data; those broad changes can create new problems. If the computer is managed by work or school, ask its administrator before changing folder access or security settings, because policies may intentionally restrict browser profiles.
9. Look for a wider crash or software conflict
If every profile crashes, including a fresh one, the cause may extend beyond one profile. On Windows, Reliability Monitor can show whether Chrome failures began alongside another application or driver change; on macOS, Console can show crash reports around the time of the failure. Chrome’s chrome://crashes page may also show reports when crash reporting is available and enabled, but it is not useful if Chrome cannot remain open. If you suspect recently installed security software or another background utility, update it or ask its vendor about Chrome compatibility rather than turning off protection or uninstalling it blindly.
10. Reinstall Chrome without deleting user data
Reinstalling is worth trying when Chrome crashes with multiple profiles and updating or testing a clean profile has not helped. Uninstall the Chrome application using the normal process for your operating system, then download the installer from Google and install it again; keep the separate user-data folder unless you have already backed it up and intentionally want a clean start. Be careful with uninstall prompts or cleanup utilities that offer to remove browsing data, because that may erase the local copy of profiles you are trying to recover. If the same crash returns after reinstalling, focus on system-wide causes, profile recovery, or support from your device administrator rather than repeatedly reinstalling.
How to Choose
Start with the test that changes the least: try Guest mode or a new profile, then see whether Chrome opens with extensions disabled. Those results help separate a profile-specific problem from a browser-wide one before you touch saved data. If a clean profile works, prioritize extension checks, a settings reset, cache cleanup, or a backed-up profile recovery; if all profiles fail, look at updates, graphics, available disk space, software conflicts, and reinstalling. Back up the user-data folder before renaming or removing profile files, and avoid deleting the whole folder as a first step. If the device belongs to an employer or school, or the profile contains important data that is not synced, get administrator or technical support before making changes that may be difficult to undo.
Frequently Asked Questions
Why does Chrome crash only after I select one profile?
Chrome loads profile-specific settings, extensions, and local data after you choose an account. A problem in one of those areas can make that profile crash while Guest mode or another profile still works; testing another profile helps narrow down the cause.
Will creating a new Chrome profile delete my old bookmarks?
No. Creating a separate profile does not itself remove the old profile or its bookmarks. Keep the old profile and back up Chrome’s user-data folder before renaming or deleting profile files, and check whether bookmarks are synced to your Google Account.
Can I recover bookmarks if the old profile will not open?
If you made a backup, keep it unchanged while testing recovery. Chrome stores local bookmarks in a file named Bookmarks inside the profile folder, but replacing or copying profile files can have side effects; make another copy first, and avoid experimenting on your only backup.
Should I delete the entire User Data folder?
Not as an initial fix. That folder contains profiles and local browser information, so deleting it can remove data that is not synced; use a new profile for diagnosis and back up the folder before any profile-folder changes.
What if Chrome crashes with every profile, including a new one?
That makes a single damaged profile less likely. Update Chrome and the operating system, test graphics acceleration, check free disk space, and look for a related system or application crash; consider reinstalling only after protecting the user-data folder.
Final Thoughts
When Chrome crashes immediately after profile selection, first find out whether the failure is limited to one profile. A Guest or fresh-profile test, followed by careful extension and data checks, can point to a fix while preserving the original profile for recovery.