Thinking something might be wrong with my Chrome installation, I uninstalled Chrome this morning, deleted all the Chrome folders under my profile folder, and did a fresh installation but it's still not working. I would have thought that they would have made this a priority to address.Ī comment in the Mozilla thread by “Marcel”: Everyone using Webroot should open tickets, this is what I just did, if they get zillion tickets on the same subjets, they might put a bit more efffort in handing their product.For the Atera site, I only have "" in the URL field. It has been over a week since this was reported to Webroot. This is what you would expect for a free product, not something we are paying for.Ī comment in the Mozilla thread by “Dalacor”: I must admit I am a bit surprised at the very slow response and lack of communication from Webroot in addressing this issue given the severity of the impact on Firefox and as result the Internet. I hope that it doesn’t take another 10 months for Webroot to fix this bug as well. What this means is the bug still exists in Webroot and if they release a new version of WRusr.dll without the bug being fixed that this same issue may reoccur. Newer releases should be unaffected by this change”. They also noted that “this block only applies to the current version of WRusr.dll. He (and others) then approved for WRusr.dll to be added to the blocklist in Firefox to work around the problem. You can read the Mozilla bug ticket 1752466 where Toshi installed Webroot and analysed its behaviour and debugged the issue. My understanding is that Mozilla fixed the problem with no assistance from Webroot. I did a clean reinstall of WSA and so far FF 97 is working fine.īut hopefully Webroot working with Mozilla and I find the issue gone since 97.0.1 came out. You loose the Identity Shield when you allow from protect. It also fixed my problem with Chrome that I’ve had for a year. But, I’m wondering, does changing the application setting from Protect to Allow open to any threats? This is certainly a simpler fix then an uninstall/reinstall. My Firefox started working immediately after this change.Īfter you uninstall and reinstall Webroot, what does the Application Protection entries for Firefox look like in Webroot Identity Protection → Application Protection? I did the solution above and it worked without uninstalling Firefox or Webroot. Then click Add protection at the bottom and navigate to firefox.exe and add this. If not then go back into Webroot Identity Protection => Application Protection and right click on the firefox entry and delete it. First thing to try is click on the Allow radio button. I fixed this by opening Webroot, going to Identity Protection => Application Protection. I had the same problem that as soon as I updated Firefox to 97 it stopped working and I do have webroot and I am running Window 10 64-bit. Webroot® Legacy Products (2011 and Prior) 33.Webroot® SecureAnywhere™ - Antivirus for PC Gamers 553. Webroot® Security Awareness Training 53.Webroot® Business Endpoint Protection 1129.Webroot Mobile Security for Android 936.Webroot® Consumer/Business - for Macs 367.Webroot® SecureAnywhere™ - Complete 3821.Webroot® SecureAnywhere™ - Internet Security Plus 2467.Webroot® SecureAnywhere™ - Antivirus 6968.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |