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

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

September 4th, 2008


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.

Jeff Lawrence Online Marketing ,

  1. Augusto Ponce de Leon
    September 10th, 2008 at 08:30 | #1

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

  2. Chris
    September 24th, 2008 at 08:32 | #2

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

  3. October 28th, 2008 at 10:53 | #3

    Good for people to know.

  4. DrJacks
    February 5th, 2009 at 12:17 | #4

    I am using Windows Server 2008 x64 and Symantec Endpoint Protection 11, I do NOT get that error.. however I do get that error on Windows XP (Regular x86) or Windows Server 2003 x86 and on those versions I am also running that same Symantec Endpoint Protection 11.

  5. Tim Miller
    February 6th, 2009 at 08:48 | #5

    I am not running symantec. I have Vista 32 ultimate, Mcaffee and AdAware. Registry edit does not work as there is no sysplant in my registry as I am not running symantec and I continue to get the error with the no sandbox arguement

  1. September 11th, 2008 at 15:09 | #1