Author: mttp Date: 2014-06-14 14:00:40 +0000 (Sat, 14 Jun 2014) New Revision: 26837
Modified: website/trunk/docs/en/faq.wml Log: Provide Webroot users with an actual solution.
Modified: website/trunk/docs/en/faq.wml =================================================================== --- website/trunk/docs/en/faq.wml 2014-06-14 11:51:00 UTC (rev 26836) +++ website/trunk/docs/en/faq.wml 2014-06-14 14:00:40 UTC (rev 26837) @@ -83,8 +83,8 @@ </a></li> <li><a href="#SophosOnMac">I'm using the Sophos anti-virus software on my Mac, and Tor starts but I can't browse anywhere.</a></li> - <li><a href="#XPCOMError">When I open the Tor Browser Bundle I get an -error message from the browser: "Cannot load XPCOM".</a></li> + <li><a href="#XPCOMError">When I start Tor Browser I get an +error message: "Cannot load XPCOM".</a></li> <li><a href="#TBBOtherExtensions">Can I install other Firefox extensions? Which extensions should I avoid using?</a></li> <li><a href="#TBBJavaScriptEnabled">Why is NoScript configured to @@ -1193,16 +1193,17 @@ <hr>
<a id="XPCOMError"></a> -<h3><a class="anchor" href="#XPCOMError">When I open the Tor Browser Bundle -I get an error message from the browser: "Cannot load XPCOM".</a></h3> +<h3><a class="anchor" href="#XPCOMError">When I start Tor Browser I get an +error message: "Cannot load XPCOM".</a></h3>
<p> -This problem is caused by the Webroot SecureAnywhere Antivirus software. -Consider switching to a different antivirus program. We encourage affected -Webroot users to contact Webroot support about this issue. -<a href="https://trac.torproject.org/projects/tor/ticket/10789">Ticket -10789</a> has some suggestions for other workarounds; please let us know -if you find better fixes! +This <a +href="https://trac.torproject.org/projects/tor/ticket/10789%22%3Eproblem</a> is +specifically caused by the Webroot SecureAnywhere Antivirus software. +From the Webroot control panel, go to Identity Protection → Application +Protection, and set all the files in your Tor Browser folder to 'Allow'. +We encourage affected Webroot users to contact Webroot support about this +issue. </p>
<hr>