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. 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.
