How did my webroot password manager end up declared as a legacy extension?
I just logged onto firefox a little while ago and it claims my Webroot password manager is considered a legacy extension now, when it did not claim so last night. When and why did this happen, and how can it be fixed? Firefox thankfully does not consider the webroot filtering extension as a legacy or I'd be very upset. I got randomly bounced up to version 61 of firefox last night and I've decided— for now— to stick with it since it seems just the same as version 58, which I was using prior. But this is still an odd development to say the least. Can anyone help?
Alle antwoorden (3)
You should contact Webroot, they can help you update your password manager. Please make sure to always use the latest version of firefox, which as of now is 62
Tyler Downer said
You should contact Webroot, they can help you update your password manager. Please make sure to always use the latest version of firefox, which as of now is 62
Yeah, I'm on version 62 now. Seems it did another update today, which I only just noticed. I'll contact Webroot about the password manager extension and tell them it needs to be updated.
I would assume that older versions of Firefox won't be affected. I have an Windows XP machine that, due to age, can only run an older version, and the password manager works fine there. My laptop runs windows 10 and has no problem keeping up with the new versions, thankfully.
Webroot has been silent about Password Manager except to say " rollback to an earlier version of Firefox " OR use another browser. Webroot has become totally unprofessional and after being with them for years I am considering dropping them like a hot potato.
I seriously doubt that they have any intention on fixing the issue and their total silence on the issue is their way to tell all of their 50,000 customers to go take a hike.