Google Chrome - Crashing with Symantec (Part 2)

As 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 and as the sandbox is one of the cool things in Google Chrome turning it off isn’t really a great solution. As sandboxing means if the page running in one browser tab crashed the whole browser doesn’t crash. By using the previous hack you’re simply going to experience FirFox style crashes with your nice new Google browser.

The Elegant Solution to fix Google Chrome

The best solution would be to get rid of Symantec altogether and get a better anti-virus system - I don’t like it in the first place. But this isn’t going to be appropriate for everyone so instead…

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.

Have fun getting your Google browser working with Symantec. Let us know how you get on.

TY to The Art of Foo for the heads up

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

One Comment

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

    Interesting. I added this to my short but growing list of Google Chrome issues.

Post a Comment

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

*
*