Same here in Vista SP1. Want to compare notes?

I'm getting the same error message for Windows XP SP2.

Same here with Windows Vista Ultimate SP1

Same. Windows XP SP2.

Also, a friend/co-worker has same problem.

Same on my Windows XP box, both have Symantec Endpoint btw

Well I have Symantec Endpoint too...

Interesting.  I am running Symantec Endpoint as well!

Same issue (xp sp3).  Also running Symantec Endpoint.  

Error occurs every time you try to load any web page. XP SP3 with Symantec Endpoint.

Unauthorized NT call rejected by protection driver. 
Caller Process:
chrome.exe

Parameter:
FuncID=74H, RetAddr=17005CH 

as u see symantec is blocking the processes from executing with its protection driver

And so symantec it is...let's see....

Confirmed. 

I tried adding chrome.exe to the exceptions list, but that didn't seem to work.

I've disabled Endpoint Protection completely and it still doesn't start.

I am using a similar setup to the other users (XP3, Sym Endpoint Protection), but
disabling SEP didn't resolve the issue. Attempted multiple uninstalls, epic fail.

I see the same problem, with FuncID=BAH.

You must uninstall application protection within add/remove programs for chrome to 
work

Unfortunately, uninstalling application protection is not always an option in an
enterprise environment...

Same situation here. Win XP SP3, Win 2008 Srv.
Symantec Endpoint Protection v11

Unauthorized NT call rejected by protection driver. 
Caller Process: chrome.exe
Parameter: FuncID=74H, RetAddr=17005CH 

Same issue.
Windows XP, SP 2
Symantec Endpoint Protection also

Same issue as original poster.  XP SP3, SEP v11

Same issue, XP SP3 symantec endpoint protection

Adding a global exception in SEP didn't fix.

You can try running Google Chrome with --no-sandbox (you need to edit the properties 
of the shortcut you use to launch it).

It looks like a conflict between some DLL injection or hooking that Symantec is doing 
(probably to monitor the app in the name of security) and the sandbox.  

If --no-sandbox does not fix things, another theory is that Symantec's monitor has 
some rule along the lines of "unknown software that tries to use the network should 
be terminated." I'd expect a notification to the user in that case, though.

In any event, this looks like a but we'll have to talk to Symantec about resolving. 
I'll take it and see what I can do.

Keyword: C0000005
(I am just trying to assist people in finding this issue - it seems like the search 
does not search by substring, so searching for C0000005 (without the 0x prefix) would 
not reveal this issue).

I am facing the same problem! and i have Symantec too

I'm using symantec too and had same error
but I resolved the problem with --no-sandbox as above.

I am running Vista SP1 and SEP11. Modifying the shortcut with --no-sandbox is
allowing me to start the browser now. I am not sure what the setting does, but would
be interested to learn more.

Hello,

The same error "The application failed to initialize properly (0x00000005).  Press on
Ok to terminate application."

what is --no-sandbox 

+1 Also running XP with SEP and the --no-sandbox fixed the issue for me.

Hello,

what is --no-sandbox 

Hello,

How to use --no-sandbox 

I asking for help .
Could you help me to solve the problem with chrome.exe

what is --no-sandbox 

Adding --no-sandbox at the end of the "target" line in the Google Chrome shortcut on 
the desktop icon.  This work around works for my PC w/ XP, SP3, SEP 11.0.2010.25.

Right click your shortcut to "Google Chrome" and click Properties.  In the target
text field, add a space then --no-sandbox right after the ending quotation mark.  Run
using this shortcut and it should work :)

it works....but not sure about the role of --no-sandbox. need more info....

Thank you it works

Thank you it works.
could you explain the role of --no-sandbox

No joy..
I am using Vista Business SP1 with Symantec SEP11
Running chrome --no-sandbox doesnt seem to fix this for me.

(No comment was entered for this change.)

works like a charm..

I have window's vista business SP1, Symantec version 11.0.2000.1567
running chrome with --no-sandbox works fine. 
Make sure you submit a space after the .exe target

If you are having trouble making the sandbox workaround work - make sure you closed
out of Chrome, then relaunch. 

Thanks, --no-sandbox worked.

thanks, this helped!

Symantec says these steps will fix this issue:
https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=15816

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.

The fix from symantec I assume will only work for unmanaged clients. A managed 
client would reset the reg key on the next policy update.

The no sandbox parameter worked for me.  But it seems that disabling a security 
feature of the application to run it is completely unacceptable.  Am I now more 
susceptible to plugin malware or viruses?  It seems like compatibility with the 
nation's largest anti-virus software company would have been tested before release.  
But I do like the browser and the effort to increase competition out there.  I'm 
sure I will love what's to come with the browser.  But until this is fixed, I'm 
saying 'no' to using it for any secure transactions or browsing anything out of the 
ordinary.  Please don't be the new MS and blame Symantec.  There's got to be a way 
to resolve the issue kindly.  Thanks!!!!

The   --no-sandbox    fix works fine!  Thank you!

create a .reg file and put inside the following text and execute it.


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
"Start"=dword:00000004


enjoy chrome !!

Hi there, I have created a simple Windows GUI (2 buttons) that let you choose how to
fix the problem. Please read more in this post
http://webreflection.blogspot.com/2008/09/google-chrome-fix.html

Kind Regards

Thanks Andrea - your little app works like a charm.

Hi,

The --no-sandbox option disables the sandbox for the renderer process. That means 
that a flaw in the HTML rendering or Javascript engine could possibly affect your 
system since these 2 modules are not running inside the low-privilege sandbox.

We do not suggest to use this option, this is mostly used for testing.  That said, 
you can use it if you want. Just be careful about what pages you are browsing... and 
don't forget to stop using it when this bug gets fixed.

This option does not change anything for the plugins.

Running the no-sandbox option disables a special security feature of Chrome, so this 
might not be the best way to fix it.

http://blogoscoped.com/google-chrome/26

Thanks Andrea!!!

regarding the comment from beanjosh...

"It seems like compatibility with the 
nation's largest anti-virus software company would have been tested before release."

This is a beta version - problems like these are exactly why it is released!  To find 
bugs and fix them.

exactly, it would be kind of hard for google to test Google Chrome on thousands of 
different computer configurations and thousands of types of software, this is the 
best time for testing 

I add to the last comment of Chorton95.  Chrome looks simple, fast, sleek, and light.
 I completely love the vision of Google and hope that this browser reaches its full.

The registry modification in comment 50 (Via the program linked in comment 55) fixed 
this issue and  issue #124  for me.

the --no-sandbox worked for me, thnks a lot

 Issue #124  was marked as a duplicate of this issue.  However, I do not have
Symantec/Norton on this machine, I do not have a SysPlant key in the registry, and I
do not get the same error messages listed here.  While the --no-sandbox option does
seem to make things work, I'm not comfortable doing any further real-world testing
without the sandboxing environment operational.  I'll be anxious to see a fix for
this and to see what it was in the code.  Thanks.

The --no-sandbox worked for me. I also have Symantec End Point on my laptop with 
Windows XP SP2.

Symantec Doc:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008090310121448

The --no-sandbox also worked for me. I also have Symantec EndPoint, HP DX5150, XP
Professional, SP3

Priority 2? Come on . . . it makes it impossible to install Google Chrome on 
thousands of machines. Surely this is worth an escalation!

its beta ~~ this is expected

Are Google products ever *not* beta?

Google isn't too blame for this... SEP is.

It's BETA, these kind of problems are going to happen. No-one is to "blame" for this,
it's BETA. Symantec protects your machine from rogue software hooking onto the stack
, chrome is a piece of malware in symantec's eyes, and rightfully so. Symantec will
be releasing an update to address this issue or google will stop violating whatever
rules it is breaking with the "Protection" software. It's beta...get over it. The fix
will come. However , you should not be bypassing security protocols to surf the web
on a beta browser on a machine unless you are willing to expose the machine
completely to the internet.

i have no Symantec software. and i dont even have any such registery key as hiven in
comment 50-53 
but i do have comodo firewall, and antivir. are they responsible?

The problem is SEP - see the article here on how to fix it form SEP's site:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008090310121448

Worked for me (running xp pro with SEP 11)

I have Windows XP, SP3 - Running Trend Micro Client/Server Security Agent which 
causes an "Ah Snap" message on any web page.  Chrome worked the first time I tried it 
and then the error every time.  The "--no-sandbox" allows Chrome to run.  

super thanks... no sandbox helped !!


D

the "--no-sandbox" works brilliantly. THANKS!!!!!!! just don't go to sites you don't
know/trust. and here I thought my IT dept @ work had killed Chrome.

The issue of running Google Chrome with Windows XP SP3 is because of a process 
"ctfmon.exe"

To resolve the issue of Google Chrome running with Windows XP SP3 can be resolved by 
following steps:
- Goto Run
- Type "regsvr32 /U msimtf.dll"
- Click on OK
Again,
- Goto Run
- Type regsvr32 /U msctf.dll
- Click on OK

- Now, Reboot the Machine

This will resolve the problem and Google Chrome will start working normally.

For the record this problem has been solved (for me) with a new release of Symantec 
Endpoint 11.0.3001_MR3. Which was released Sept.17, 2008

I am running Windows XP SP3 and Google Chrome 0.2.152.1.

Thanks,
Jonathan

I also updated to Symantec Endpoint 11.0.3001_MR3 but this did not solve the problem
for me. Running Vista SP1.

Changing to Area-BrowserBackend plus a dedicated AppCompat label because 
there are too many Area- labels.

(No comment was entered for this change.)

The --no-sandbox also worked for me. I also have Symantec EndPoint, HP , XP
Professional, SP3

Same issue.. Have XP SP3 and Chrome does not work!

(No comment was entered for this change.)

I just installed SEP 11.0.3001.2224 in combination with Chrome 0.3.154.0.  I can 
finally say that I no longer need the no sandbox option.  If anyone else has a chance 
to verify, this is a first for me.  I will be installing on other machines today to 
see if this behavior is consistent.

The issue with Symantec Endpoint Protection should be resolved by their MR3 release: 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=2733

If you see similar symptoms, but do not have Symantec's software installed, please file a separate issue.

issue is NOT fixed for me with MR3 update on Windows Vista

I am not able to use Chrome..... I tried even by disabling Symante...but things do 
not work. I have Win XP with SP3

Hi,

I'm using MSWindows Vista 64 (SP1) with Symantec Endpoint 11.0.780.1109 and Chrome
runs perfectly. No workarounds, not a single change I did to get it running.

i've update the SEP to MR3. It's fixed and NO NEED to use --no-sandbox anymore. I'm 
used XP3 and SEP 11.0.3001.2224

 Issue 4770  has been merged into this issue.

"--no-sandbox" its working for me also thanks for comment

I am having the same problem also. 
Windows XP SP3 Norton Internet Security 2009
Using the --no-sandbox workaround worked, but i really do not trust that. 

Jason,

Have you tried uninstalling or disabling NIS 2009 ?

You are the only report of this situation so far. 

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=9733 

------------------------------------------------------------------------
r9733 | cpu@google.com | 2009-02-12 18:01:41 -0800 (Thu, 12 Feb 2009) | 8 lines
Changed paths:
   A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/compat_checks.cc
   A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/compat_checks.h
   A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/compat_checks_unittest.cc
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/installer_unittests.vcproj?r1=9733&r2=9732
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/util.vcproj?r1=9733&r2=9732

Test for Symantec SEP
- Versions before 11MR3 crash chrome
- Still need to wire the code.

BUG=38


Review URL: http://codereview.chromium.org/24015
------------------------------------------------------------------------

Guys, this is fixed after SEP MR4

how do i change and apply the --no-sandbox to my google chrome so it works.

Chukay

 Issue 13405  has been merged into this issue.

its not just symentec, it can also happen
if u r infrcted by

Internet worm W32.Netsky

chrome was working fine, until i got infected. the issue happened again after i 
formatted the system and i got infected again.
symentec and virus are related?/trying to start the same information sending 
process??
enlighten me!