Posts Tagged ‘(0xc0000005)’

Chrome Error Symantec
Chrome it is!
I just downloaded it and tried to run it with this disappointing message:

The application failed to initialize properly (0xc0000005). Click on OK to terminate the application.

Some googling around brought me to this blog that had all links neatly ordered.

Seems the problem exists for users of Symantec Endpoint Protection (aptly abbreviated SEP).

Even without this activated, there is an underlying default rule that prevents Chrome from spawning process threads for it’s sandboxing (*). Just google around for Sysplant.sys and you will notice that Chrome isn’t the only one to suffer from this problem.

There are 2 solutions to this issue:
1) disable the sandboxing, but this basically defeats some of the strongest points of the browser. How to do it : Right click on the desktop icon (or menu icon) that launched Chrome and choose properties. Then add at the end of the target string (after the quotation marks) a blank and then –no-sandbox.
This turns off the sandbox behaviour of Chrome.

2) Disable Symantec’s behaviour as described here on the Symantec forums (you need admin access to your PC for this and this will also not work where the policies for Symantec Endpoint Protection are set centrally by your sysadmin.

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.

I personally prefer solution 3: Remove Symantec entirely and install a decent anti-virus/system protection system, but if you are stuck with the vile piece of crap that Symantec is, then option 2 is the preferred one untill Google launches an official solution (not workaround) for this issue.

(*) Chrome makes a separate operating environment for each process (group) it starts. Basically every tab ends up in its own micro environment thus preventing crashing tabs from taking your entire browser with them. More on this in Google’s explanation I mentioned in the post before.


Read Full Post »