Comments on: The application failed to initialize properly (0xc0000005):Google chrome

By: Muniraj

Muniraj — Tue, 03 Nov 2009 04:31:21 +0000

Thanks ,

Its working with adding –no-sandbox in shortcut.

By: Chitral

Chitral — Sun, 01 Nov 2009 11:10:20 +0000

Heyy it worked well!!!!!!!
Thanx a lot for all respective ppl who gave the sandbox solution.
Good Bye Safari!!!!!!!!

By: jongskii

jongskii — Thu, 08 Oct 2009 15:33:55 +0000

i just add no sandbox in the shortcut and i can now browse without problem.

thanks a lot.

By: febri

febri — Sun, 04 Oct 2009 06:21:41 +0000

its works great!!! thanks!

By: scott

scott — Mon, 29 Jun 2009 14:39:21 +0000

another thing i found on vista. if you get this error right click on google chrome icon and run it as administrator.

By: Raghu

Raghu — Wed, 10 Jun 2009 16:53:38 +0000

I had the same problem, fixed it.

1. Open Symantec Endpoint Protection
2. Click on options under Network Threat Protection
3. Select Configure Firewall rule.
4. Add new rule to unblock, by selecting google chrome under applications tab.

I don’t know whether it is secure to do this. But works.

By: Sinthu Raja

Sinthu Raja — Fri, 29 May 2009 13:59:15 +0000

hai really it is working after adding –no-sandbox this to my short cut really thanks guys

By: Rika

Rika — Sat, 16 May 2009 07:15:09 +0000

Thanks for the tip!! Yes, I have the Symantec anti-virus installed and am not allowed to fiddle with it, so this workaround really helped.

By: Mukesh

Mukesh — Mon, 11 May 2009 10:27:18 +0000

Thanks a lot ! The sandbox thing worked in My Xp sp 3 Viena edition ! Cheers to u !
Will this allow any malware to install in the system here after ?

By: nav

nav — Mon, 27 Apr 2009 00:48:15 +0000

THANK YOU SOO MUCH THE –no-sandbox THING WORKED!!!

By: Enzo

Enzo — Tue, 21 Apr 2009 14:34:27 +0000

Thank you I just reinstalled from a virus and thought it was another virus problem. It’s funny because my older computer run chrome perfectly but the new computer I’m on gives the error. Thanks for the registry hack too.

By: Mark R

Mark R — Mon, 13 Apr 2009 14:48:21 +0000

I’m using Symantec Endpoint Protection and I can confirm that adding –no-sandbox to my Chrome shortcut worked around the problem on my Windows 2003 Server box. Thanks!

By: Chris

Chris — Wed, 01 Apr 2009 15:23:09 +0000

FIXED!!!!

thanks for posting the solution

By: bonyka

bonyka — Sat, 14 Mar 2009 23:53:44 +0000

Thank you so much. It does work.

By: ally

ally — Wed, 11 Mar 2009 15:31:39 +0000

Omg thank you so much. My Chrome works again!

By: Bila

Bila — Sun, 01 Mar 2009 20:57:00 +0000

Thx a lot for this trick. It works for me

By: Zubiar

Zubiar — Sat, 21 Feb 2009 08:03:23 +0000

hey u really solved my gr8 problem with chrome.thanks

By: amit

amit — Sat, 14 Feb 2009 11:00:33 +0000

yes yes man it worked thank u very much

By: Aleria

Aleria — Thu, 12 Feb 2009 20:21:52 +0000

I was running into this problem and did not have any symantec software installed.
Creating the –no-sandbox shortcut fixed the problem if I were opening Chrome from that shortcut to use it. But I have a few different programs that open a page in the default browser and do not access it using the shortcut. So this obviously meant that any pages these programs pulled up would still generate the error.
I dug around in the registry and found out after trying a few different tweaks that there is a simple change that will make all chrome windows open in “no sandbox” mode. If people are happy with having to go without sandbox for now until Google can fix it, then this is a much heavier fix to make sure all Chrome windows that open will not get the error.

In the registry you will need to use Find and locate a string listed as:
“C:\Documents and Settings\jwaller\Local Settings\Application Data\Google\Chrome\Application\chrome.exe” — “%1″
There will be many of them, so once you find the first one, double click on that string and replace it with:
“C:\Documents and Settings\jwaller\Local Settings\Application Data\Google\Chrome\Application\chrome.exe” –no-sandbox — “%1″

Just hit f3 to find the next one in the list and continue replacing them all with the –no-sandbox string.
This will add the no sandbox rule to all Chrome windows no matter how they are being opened. Hope this helps.

By: Yianis

Yianis — Fri, 23 Jan 2009 19:43:18 +0000

The registry solution worked for me like a charm.
I am using WinXP SP2 and have Symantec Endpoint installed
No problems with the machine afterwards (do shut-down and then restart)