Google Chrome And Symantec Endpoint Protection Fixed In MR3
- 4
- Add a Comment
Google Chrome has until recently been clashing with Symantec Endpoint Protection (SEP), making it impossible to run Chrome in sandbox mode. It was possible to disable sandbox mode by running chrome with the argument –no-sandbox. Ironic, really, considering both SEP and sandbox mode attempts to protect the user from malware.
On behalf of a company, which owns SEP licenses, I frequently check https://licensing.symantec.com/ for product updates. On September 17, 2008 Symantec published a new maintenance release, MR3.
After installing the MR3 release on top of my existing MR2 installation I found that Chrome would run in sandbox mode. The Chrome-compatible SEP software version is 11.0.3001.2224.

4 Comments
Alex Cohn
October 16th, 2008
at 1:01am
Didn’t work for me. After upgrade to 11.0.3001.2224, I still have to use –no-sandbox parameter.
awarberg
October 16th, 2008
at 2:09am
Hi Alex
I am sorry to hear that.
I’ve tested Chrome and SEP in the mentioned versions on 5 different computers until now and haven’t had problems yet.
They are all Windows XP SP3 with all patches from Microsoft Update.
Best regards
Andreas
Marc
November 7th, 2008
at 6:31am
Did not fix the problem for me either.
awarberg
November 8th, 2008
at 3:39am
Did you try switching to the developer update branch?
http://www.chromeplugins.org/chrome/chrome-developer-updates/