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.

Google chrome not opening