Google Chrome error: The application failed to initialize properly (0xc0000005)
Written by Patrick on September 2, 2008 – 9:17 pm -Update: I have confirmed that Rizal’s suggestion in the comments fixes the problem. Add a “--no-sandbox” argument to the Chrome shortcut and Chrome should start working. To do this right click on the Chrome desktop icon. In the Target box add “--no-sandbox” without the quotes to the very end of the box.
Update2: Chrome’s sandbox is an additional security feature that restricts each browser process from accessing anything on the system that it is running on. So disabling it is usually not a good idea. But in this case the browser is so new that people are mostly using it as a test and to verify website compatibility so I think most people are ok with disabling it. As far as I know using the “no sandbox” argument is no worse than browsing with the current version of Firefox or Internet Explorer. Google or Symantec will fix the problem in a future release and you can re-enable the sandbox at that time.
Original post:
I installed the new Google’s new Chrome browser within minutes of being released. It installed ok but it wouldn’t run at all. As soon as it started up I would get this error:
The application failed to initialize properly (0xc0000005). Click ok to terminate the application.
This appears to be caused by Symantec Endpoint Protection (SEP). Unfortunately I am running this on a corporate machine and there is no way for me to disable or configure the Symantec software.
Uninstalling SEP is always an option to get Chrome to work. Another less drastic method that was posted online:
I was able to go into SEP - Change Settings - Centralized Exceptions,
click Configure Settings, and add c:\documents and settings\<username>
\Local Settings\Application Data\Google\Chrome\Application\chrome.exe
to the list. However I had to reboot the machine to be able to open up chrome w/out the error message.
For more information read this thread: http://groups.google.com/group/google-chrome-help-troubleshooting/browse_thread/thread/41ef35857180e154/.
Tags: chrome, google
Posted in Software |
September 3rd, 2008 at 1:30 am
please perform the step below :
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.
September 3rd, 2008 at 2:53 am
Add a registry entry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant
Change the dword START to 4
And then restart the system.
It works for me.
September 3rd, 2008 at 3:09 am
[...] everyone who is using Symantec Endpoint Protection is facing the exact same issue. I tried to configure SEP to ignore chrome.exe, but in vain. So now I have to run chrome.exe with the –no-sandbox flag, [...]
September 3rd, 2008 at 12:32 pm
Thanks, guys. Editing the registry setting worked for me.
September 3rd, 2008 at 6:11 pm
This works with –no-sandbox not -no-sandbox after the quotation marks. 2 dashes and instead of 1.
September 3rd, 2008 at 6:12 pm
even in my post only 1 dash should up. 2 dashes seems like it will do it
September 3rd, 2008 at 6:16 pm
(–no-sandbox)
September 3rd, 2008 at 7:58 pm
So what exactly does the –no-sandbox argument do? Mine is working now but I wonder what functionality I am missing as a result…? Anyone know?
December 22nd, 2008 at 4:52 am
Like magic: –no-sandbox can fix the 0xc0000005 , error message for google chrome.
Add :–no-sandbox at the end of the line in the Target box , in properties ,by right clicking on the google chrome icon!
thanks
December 29th, 2008 at 8:22 am
zbobvlkpbkyersxgwell, hi admin adn people nice forum indeed. how’s life? hope it’s introduce branch