Google Chrome Crashing with Symantec

But Don’t Worry We Know How To Fix It

I’ve been sitting at work trying to get the new browser from Google – Chrome, to work on my office PC. And it didn’t work I kept getting an initialisation error. After some swearing, some throwing things etc I found the fix.

Getting Google Chrome working if you have Symantec Installed

Right Click on the ‘Google Chrome’ program icon and open the properties section. at the end of the target string add “-no-sandbox”. And bingo the new version of Firefox – sorry Google Chrome will be up and running on your PC.

Oh and I just did this post with Google chrome – and it worked ok. And it looks pretty clean – unfortunately I dont know when my toolbars will work with it but will have to keep waiting.

Book Marking Buttons: Get Clicking! These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Blue Dot
  • Bumpzee
  • De.lirio.us
  • Fark
  • Ma.gnolia
  • MisterWong
  • Propeller
  • Reddit
  • SphereIt
  • StumbleUpon
  • Technorati
  • TwitThis
  • Webnews.de
  • YahooMyWeb

3 Comments

  1. Posted September 3, 2008 at 5:48 pm | Permalink

    i’m willing to try it out just to see if it works more efficiently than FireFox… if it’s faster than Firefox and isn’t IE, then i’ll use it

  2. jr MonsterID Icon jr
    Posted September 28, 2008 at 2:02 pm | Permalink

    thanks man

  3. Sarah MonsterID Icon Sarah
    Posted October 25, 2008 at 1:39 pm | Permalink

    Thanks for this fix.

    Google Chrome stress that you shouldn’t disable sandbox but it doesn’t seem to work properly otherwise if you have some secure browser software programs running, or even installed.

    I think as long as you have some decent browser protection, you should be ok to disable Chrome’s sandbox.

    FYI – I only started having problems after I installed Zonealarm’s Force Field browser protection. Disabling sandbox has restored full functionality to Chrome.

    Thanks again! :)

One Trackback

  1. [...] mentioned in previous post you can turn off the sandboxing in Google Chrome to stop it conflicting with Symantec Endpoint Protection. However this is really a bit of a hack [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*