I installed firefox 40 .
also webroot web filter is active , but show it have some problem .
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Edit: There's now a self-service version of the procedure that you can follow here:
You can also still contact support if you'd like assistance getting that working.
Thanks for the update. Patience I have, particualrly when I know what has transpired.
I expect that, for the time being. any changes I see regarding WPM and Firefox will be part of a work in process. 😉.
I believe that the change is due to the changes Firefox is working on to require that add-ons be 'signed' by them in order to work. The whole point of signing is to verify that the add-on you download is the exact correct one from the provider, and that the add-on is indeed safe and not malware.
Since Webroot and Firefox are still working on getting a working AND signed Password Manager version 3.1.1, the browser will consider the add-on to be insecure simply by lack of being officially signed by Mozilla.
The Password Manger version 2.5.is quite safe, but since the version 2.5 never was, and never will be, signed by Mozilla, it will show that option.
I hope this helps!
There is a problem currently with the 3.1.1 version of the Password Manager, and Webroot is very aware of it, and working to fix it. It gets complicated in that the Password Manager is licensed from LastPass... so Webroot and LastPass must work together to figure out the issue, and THEN work with Mozilla as well to get the corrected version signed and allowed for FireFox.
I expect it will not be much longer before things are corrected, but until then there are a few options.
IE and Chrome both work just fine. The issue is ONLY with FireFox.
If you have automatic update of add-ons enabled, you will want this turned OFF.
Some users have been able to go back to the previous version of the Password Manager. If you have automatic update of add-ons enabled, you will want this turn off. You can try either use of the toolbarfix.exe utility, or a clean re-install of WSA. As soon as you do either of these, check the version of the Password Manager.
These methods have not worked for everyone, though most likely due to not disabling automatic updating of add-ons in Firefox is my guess. Here is a reply that details how one user did get back to the working 2.5 version, and it is working fine.
I hope this helps, and it should not be all that much longer before things are fixed and back to normal.
In the past when this has happened, I've successfully uninstalled and then reinstalled Webroot whichs results in a functioning WPM icon reappearing on my browser tool bar. Unfortunately, when done (uninstall/reinstall) on my recently upgarded Win 10 platform, I get an error message stating that "app does not work on Windows 10". I then have to execute a "restore" to an earlier date to recover a previously installed Webroo image on my laptop.
I've never had this level of problem installing Webroot. I believe Webroot is an excellent product, but for me, "ease of installation" takes a big hit on the reputation of Webroot. This said, maybe it is something that I am do incorrectly.
Ever since I managed to get the Webroot Passwod Manager working again (with WPM 2.5.0), the Webroot Sign In screen (the one that pops up every time I launch Firefox) displayed a new second option below "Remember me". The new option read "Disable Insecure Firefox Password Manager". As of this morning, that option has disappeared.
Curious, I went to the Add-ons Manager page and checked what version of WPM was running. That hasn't changed, it's still 2.5.0.
I then found Webroot Password Manager in the list of add-ons and clicked "Options". The "Disable Insecure Firefox Password Manager" option still appears first in the General section, and, to my great surprise, that option was checked again (I'd unchecked it previously to allow WPM to run).
As a test, I kept that option checked, which would have previously disabled WPM. Then I went to several Web sites that require log-ins, and found that WPM is alive and well and filling in passwords for me, in spite of that "Disable" box being checked.
Could this mean that Firefox no longer considers WPM to be insecure?
My recommendation, if you are already on version 2.5.0 stick to it and turn off 'Automatic Updates' within FF 4.0.2, and wait until WPM 3.1.1. or whatever is next gets the official green light (no pun intended).
I found an old toolbarfix.exe hanging around and used that to first uninstall it.
I looked in FF to see that it was indeed gone. It was - Good.
I again ran that old toolbarfix.exe to repair/install it.
Ran FF and everything went smoothly after that, except that I noticed that the toolbar seemed to be an earlier version 2.5? - Not sure now, because I don't see a version number anymore.
The toolbar now works - hope it works tomorrow...
oops, after comparing the old and newer toolbarfix.exe properties, I see that they are identical. I no longer know what I did right to make it work!
What steps did you take yesterday to get it back to working?
Nobody else I have seen has mentioned this, so I might as well... I THINK that after updating to Firefox 40 it was working FOR A WHILE, but strangely... instead of the icon functioning as it normally did (offering me to autofill or autologin), I would have to right click it and it would list an option for that on the website I was on. Then it stopped working altogeher at some point and hasn't worked since.
At this point im done with the trial and error and will just hope an offical fix comes out quickly.
1. Toolbarfix works sometimes
2. Uninstall and reinstall works sometimes
3. Don't download the extension called Webroot Password Manager that was created by LastPass
3. We're working on getting this whole situation resolved and getting our proper extension signed by Firefox
Apologies for the mess in the meantime.
It looks like LastPass put that up for some reason and we're trying to figure out what is going on. Remove that one and try running the toolbarfix instead: