This is on Windows 7 SP1 64 bit using the free version of SiteAdvisor. I don't know what else I can do, but within reason I'm prepared to work with you to sort this out. If I ignore the prompt then SiteAdvisor is still listed in the Chrome Extensions tab but is not enabled and Chrome works fine. If I click on Remove from Chrome then SiteAdvisor is removed and Chrome works fine. If I click on Enable extension then SiteAdvisor is added to Chrome but still doesn't work, and worse, when I close Chrome it doesn't close properly and leaves an instance of chrome.exe running and then Chrome can't be restarted. uninstalled SiteAdvisor, restarted my PC, gone through all my Chrome profiles and made sure that the SiteAdvisor extension had been removed, reinstalled SiteAdvisor. uninstalled Chrome, restarted my PC, reinstalled Chrome - SiteAdvisor still didn't work Today, after a discussion with McAfee support yesterday, I have: I am having problems with SiteAdvisor in Chrome as well and there are still problems. If just some sites are grey (while others show green, yellow or red), then these grey sites are probably sites that have not been rated - in that case, I'd suggest requesting the site get rated. If you haven't done this already, I'd suggest checking that the SiteAdvisor is Enabled inside Chrome (Settings > Extensions).Īs for ALL sites showing as grey, this typically means that there is no connectivity to the SA servers, so the SA client cannot retrieve site ratings - in this case, there may be some problem with either you internet connection or some application on your system interferring with the SA connection. To continue to function with Chrome, we have implemented a new Chrome plug-in which uses a Native Messaging technique in this approach Chrome runs our host from a hidden cmd and this is the way we communicate with Chrome.Īs for the extension not showing up in Chrome, I've tested this on my own systems both the suite-installed 3.6.4 (build 176) and the standalone 3.6.5 (build 131) and it works fine in both on Chrome ".102 m". Hayton is correct - Chrome (as Firefox did a while ago) is making changes in how it deals with plug-ins ("Extensions").
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |