Fix For Google Chrome: The application failed to initialize properly (0xC0000005).


After doing some research it looks like the issue I mentioned previously is caused by Symantec Endpoint Protection. While there is currently no official fix from Google there are three known ways that you can solve this problem. None of which is a great solution, but until Google and Symantec can come up with a solution, these three should resolve the issue:

Option #1

1) Back up the registry on an affected system.
2) Open the registry on the Agent system by entering regedit from a run prompt.
3) Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant.
4) Open the Start DWORD.
5) Change the value to 4 to disable the drivers.
6) Reboot the system to commit the changes.

Option #2

1) Navigate to Control Panel and Add/Remove Programs for XP or Programs and Features for Vista.
2) Scroll down to Symantec Endpoint Protection and hit Change or Modify.
3) Choose Modify from the Symantec menu.
4) Uninstall Application and Device Control from the menu.
5) Restart your computer.
6) Attempt to reinstall Google Chrome.

Option #3

1) Go to the following website and look at the latest registry files to download to automate this process for you. The fix has been mentioned in a few message boards as successfully working for those of you who don’t want to mess with Option #1 or Option #2.

If anyone has any additional methods to resolve this issue please let me know and I will update this post.

Tags: ,

Thursday, September 4th, 2008 Online Marketing

4 Comments to Fix For Google Chrome: The application failed to initialize properly (0xC0000005).

  1. Another way is by running Chrome with the optional parameter –no-sandbox (that is no sandbox)

  2. Augusto Ponce de Leon on September 10th, 2008
  3. [...] Has anyone else had any issues with Google Chrome, either during installation or while utilizing the browser? Update: This issue has been somewhat resolved and you can read about it here. [...]

  4. Google Chrome Crashes and Burns - Sonicko Consulting on September 11th, 2008
  5. I receive the same error upon opening chrome but I don’t have that registry value in my registry. I uninstalled symantec antivirus and don’t have SEP so it seems another app is causing this same issue . . .

  6. Chris on September 24th, 2008
  7. Good for people to know.

  8. Tina on October 28th, 2008

Leave a comment