Google Chrome error: The application failed to initialize properly (0xc0000005)

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\
\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:

This entry was posted in Software and tagged , . Bookmark the permalink.

34 Responses to Google Chrome error: The application failed to initialize properly (0xc0000005)

  1. jennyburger says:

    None of the above worked for me…and too many entries from folks having the same issue said that the –no-sandbox wasn’t a “safe solution”. But here’s what I did that seemed to fix the issue:
    ~right click Google Chrome Icon
    ~under Shortcut, go to Open File Location (at bottom)
    ~locate “old_chrome”, right click
    there it was!

  2. Da Shovel says:

    Here is how to fix the Error ! Go to Google Chrome ICON on your DeskTOP, Right click on it & go to Properties ! Now go to the Compatibility Box & Click On it ! Now make sure it is running in Combatibility with the Version of Windows you Have ! Example : I had also been getting this message, I have tried fixing it all day ! Then it hit me, My Combatibility Mode was Checked for Windows 7; Service Pack 2 ! I have Windows Vista ; Service Pack 1 ! All I had to do was Check Mark the Right System & BAM ! No More Error Message : 0xc0000135 No longer exists & Google Chrome Works Perfectly !

  3. sad says:

    try using no sand trick giving a space like chrome.exe” -no-sandbox

  4. pralay says:

    i got it. thanks. –no-sandbox works.

  5. pralay says:

    after using “no sandbox” still the error occurs. please help me to work with my google chrome.

  6. rahul says:

    my camera doesnt start in gtalk and it gives an Dummy:chrome.exe error “The instruction at 0x1c415849 referenced memory at 0x00000000.The memory could not be read.” What do i do?

  7. procedure#02
    step:1 First go to control panel /Administrative Tools/computer management.
    step:2 clickon computer management then on right side goto local user and groups and click on
    user an create password for administrator.
    step3:Now at dektop Right click on google chrome and Run as administrator type password and chrome will work properly.

  8. jayesh says:

    please can anyone tell me how to use that “no sandbox” trick.

  9. jayesh says:

    it doesnt working for me

  10. waniz says:

    binoop :
    Add a registry entry at
    Change the dword START to 4
    And then restart the system.
    It works for me.

    i m unalbe to find sysplant option in the services in the below commands

  11. bagusee says:

    if it’s not valid try to check the “run as administrator” check box. At first i also can’t input the sandbox thing. but after i did this, the error messsage didn’t appear.

  12. mga says:

    Will this work for a “oxc0000022” error?

  13. abdul says:

    i have installed fresh copy of windows xp and install the chrome i am facing the same issue and not able to fix after adding “–no-sandbox

  14. Tim says:

    Thanks to everyone on this thread for fixing the problem. But only Bigv2007 pointed out the crucial point that a SPACE is required before the “-no-sandbox” argument, otherwise it won’t be accepted. I recommend this fix to anyone having crash problems with Chrome: it’s well worth a try.

  15. DEV says:

    Adding –no-sandbox worked for me!!!!!

    i did not try the regedit solution

  16. Dogmeat says:

    Thanks everyone for the advices,especially calva14 and binoop 🙂

    There is 1 thing about sandbox thingy and it just affects the shortcut of it anyways it doesnt work for other links..

  17. Bigv2007 says:

    –no-sandbox worked for me but there has to be a space before it which had me stumped for a while. Also marjanHAK, i figured it is a virus related problem in my case, as i have had chrome for a while and was working fine until this morning. I searched for the installer but could not find it anywhere. I see no sandbox as a temporary solution, until i can use yours. Thanks guys.

  18. Jibinjim says:

    Thnx a lot….
    the –no-sandbox worked for me aswell in vista ultimate….

  19. luke says:

    The “SEP – Change Settings” solution did not work for me ( XP, w SEP installed )

    Adding “–no-sandbox” worked for me!!!!!

    i did not try the regedit solution

  20. Syed Mustafa S says:


    Rizal has provided the exact solution for this problem.

    Thanks a lot Rizal


  21. marjanHAK says:

    I had same error but after some dinging i find other solution, there is version of virus that insert code in Chrome file and with that code visit web pages and download other viruses and blocking work of Chrome. Trick is to go in Chrome install folder example C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\Application\\Resources\Inspector ( make backup copy of Inspector file) and open inspector document with notepad and delete rows that have …………….. (try typing ura in notepad search because virus puts @%& or something else betvin c and ura ) in my case i had 5 rows of that code and they were the same that is how you can recognize or maybe other version like Last thing of good Chrome code is …..class=”status-bar-item”> it is end of 5 row, everything after that you can delete. When you done click save. Reopen after that and if code is back you did not delete all try with search an delete what is left. I repeat that this is solution if virus mess up with your Chrome code.

    Hope it will help somebody.

  22. Aleria says:

    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.

  23. ameen says:

    -no-sandbox works

  24. YES LIKE MAGIC –no-sandbox CAN FIX THE EROR 0XC000005

  25. Tim Miller says:

    Neither work for Me Vista 32. I have no sysplant in my registry as I am not running symantec and no sandbox argument gets me the same error

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

  27. Joeboo says:

    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?

  28. Ondrei says:


  29. Ondrei says:

    even in my post only 1 dash should up. 2 dashes seems like it will do it

  30. Ondrei says:

    This works with –no-sandbox not -no-sandbox after the quotation marks. 2 dashes and instead of 1.

  31. Rob Robinson says:

    Thanks, guys. Editing the registry setting worked for me.

  32. Pingback: Rizal Almashoor’s Blog » Blog Archive » Google Chroming, but Missing the Point

  33. binoop says:

    Add a registry entry at
    Change the dword START to 4
    And then restart the system.

    It works for me.

  34. calva14 says:

    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.

Leave a Reply

Your email address will not be published.