You can reverse this method if you want to try and retain as much as possible of your profile (i.e., if you have a ton of extensions installed that you don’t want to redownload–though to restore those you can technically also simply copy the subfolders within the Default folder as well that relate to them). In my case, it was Cookies, which you’ll notice I didn’t even list above because I bet that’s what your problem is too! If you copy a file and the behavior reappears, that’s obviously your culprit.Close Chrome (if it isn’t already) and copy over the following user data files within this folder one at a time, opening and closing Chrome in-between each time to check for a hanging chrome.exe process after the file is copied:.Open another folder browser window and navigate to the new profile data here: % LOCALAPPDATA%\Google\Chrome\User Data\Default.Navigate to %LOCALAPPDATA%\Google\Chrome\User Data.old\Default to get to the old corrupt profile data that you are no longer using.But if you aren’t, you’ll need to manually copy over the data from the corrupt profile. If you’re simply using a roaming Google Chrome profile (such as one where you sign in while opening the browser) to retain your settings, it’s as easy as signing in again to repopulate your stuff. The new profile doesn’t have any of your previous data in it (as you probably noticed).
#Google chrome not opening up Pc
Open up a folder browser window (a Windows Explorer window) on your PC and navigate to the folder %LOCALAPPDATA%\Google\Chrome.This is the most surefire way of correcting the issue as it involves working from the ground up with a new profile and reintroducing customizations (such as Bookmarks, Preferences, etc.) until you find one which is a problem (in my case, it was Cookies). The first approach involves recreating a new User Data store for your Chrome profile. If this still doesn’t work, now that you’ve ruled out any plugin/extension issues, you’ll need to employ this final phase of the fix, which involves locating corrupt User Data and fixing it. Repeat the close/open process to see if the behavior persists. If this doesn’t work, reenable all plugins, then navigate next to chrome:extensions and disable all extensions next.If the behavior persists, reenable the plugins one-by-one to narrow down the one which is responsible. You may have to kill chrome.exe manually once and then reopen/reclose the browser to test this.
Disable all plugins and restart the browser. First, open Chrome and navigate to chrome:plugins.Here is the process by which I propose you approach the solution in your particular case: In light of this, there is a relatively easy way to solve either. But, of course, this is no long-term solution.įortunately I have found the long-term solution! Keep in mind it may be different in your case depending on the cause, but it appears that this problem is always a product of one of two conditions:įor sake of justification, in the case of my customers’ machines, the first one was caused by a problematic QuickTime plugin (disabling it fixed the problem), and the second one was a corrupt Cookies store–one which could not be cleared using the Clear Browsing Data dialog. Two workarounds exist: either reboot the machine or open Task Manager and kill the hanging chrome.exe process that is responsible for this problem. This happens regardless of whether the Continue running background apps when Google Chrome is closed checkbox is checked in Settings. A frustrating issue that I have encountered on multiple recent customers’ PCs is an inability to completely close all Google Chrome processes–and, even more frustratingly, a consequent inability to reopen Chrome once it has been closed on the machine.
0 kommentar(er)
