Does WSA support Firefox 42 x64

  • 7 November 2015
  • 31 replies
  • 649 views

  • Community Leader
  • 516 replies
Hello WRooters,
Does WSA Antivirus support Firefox 42 x64.
Filtering Extension did not populate into nor offer dialog to install Filtering Extension with Firefox 42 x64. 
 
Are we any closer to "filter driver". 
 
Thanks
 
 

31 replies

FWIW ~  Webroot Support (Nov 10, 2015 9:16) RE:1.2.0.19 Signature as VerifiedHello,
Thank you for bringing the issue you are experiencing to our attention. The Webroot Development team has been notified of this issue and is currently working on a resolution with Firefox. This issue is related to the infrastructure that Webroot uses and is not related to the program on your computer nor the computer itself.
Once a fix is deployed, the issue you reported should be resolved. No change to your system is necessary.
Should you have additional questions, please send us a reply in the "Send another message:" section of this page.
Regards,
The Webroot Support Team
 
Based upon TripleHelix info Filtering Extension 1.2.0.19 is Verified. 
Based upon BurnDaddy info Filtering Extension 1.2.0.19 is not Verified. 
Based upon Support info.   No worries. 

Thanks!
 
 
Userlevel 7
Badge +55
@ wrote:
@ wrote:
It doesn't look like we officially support 64-bit yet:

Microsoft Internet Explorer 7.0 and higher, Mozilla Firefox 3.6 and higher (32-bit only), Google Chrome™️ 10.0 or higher

However you can still contact support and they'll do their best to help you get it working, and report any bugs or issues to our developers.
Filtering Extension is working. Search annotations and page blocks as expected. 
UNOFFICIAL was easy to implement with Community help.   Thank you.
I just need to know whether 1.2.0.19 signature has been verified.
I need to know whether I should still observe Proceed with caution.
I'm aware of what Proceed with caution means.  No worries. 
Just that reports as I've heard for 1.2.0.19 as verified vary.  
I looked in Firefox Secure_SocketLayer Properties.
I do not find reference to Signature. 
I'll ask by Ticket.  
Thanks (when I find out I'll markup solution).   
Well in my Firefox 64bit there is no warning but the Password Manager still does so I wouldn't worry as it's doing it's job!
 
Thanks,
 
Daniel ;)
 


 
 

@ wrote:
It doesn't look like we officially support 64-bit yet:

Microsoft Internet Explorer 7.0 and higher, Mozilla Firefox 3.6 and higher (32-bit only), Google Chrome™️ 10.0 or higher

However you can still contact support and they'll do their best to help you get it working, and report any bugs or issues to our developers.
Filtering Extension is working. Search annotations and page blocks as expected. 
UNOFFICIAL was easy to implement with Community help.   Thank you.
I just need to know whether 1.2.0.19 signature has been verified.
I need to know whether I should still observe Proceed with caution.
I'm aware of what Proceed with caution means.  No worries. 
Just that reports as I've heard for 1.2.0.19 as verified vary.  
I looked in Firefox Secure_SocketLayer Properties.
I do not find reference to Signature. 
I'll ask by Ticket.  
Thanks (when I find out I'll markup solution).   
Userlevel 7
Badge +56
It doesn't look like we officially support 64-bit yet:

Microsoft Internet Explorer 7.0 and higher, Mozilla Firefox 3.6 and higher (32-bit only), Google Chrome™️ 10.0 or higher

However you can still contact support and they'll do their best to help you get it working, and report any bugs or issues to our developers.
Userlevel 7
Badge +55
@ wrote:
Hello @,
So, has filter extension 1.2.0.19 signature been validated or not.
WRooters tell me their 1.2.0.19 is not validated.  
Still Proceed with caution. 
One friend tells me 1.2.0.19 is not despite prior rendered as verified. 
Each version requires validation.

So, when you went back to 32bit your Filtering Extension renders verified...?
Has there been Webroot announcement 1.2.0.19 is verified. 
 
I have one other extension Proceed with caution. 

Last I heard, FF42 has warning, 43 will have work around and 44 will block unverified.
So, I have some time. 
 
At some point extensions will need to be verified before release.
At some point we'll go filter driver.
 
re: which makes sense since this work-around is not supported by Webroot
the signature of the extension is verified not the install method
 
Just wait till the Webroot Staff reply and they will let us know as Firefox is changing all the time so the Webroot Staff are keeping up with the changes and this goes with Chrome and when Microsoft will allow Extensions in it's new Edge Browser.
 
Daniel
Hello ?,
So, has filter extension 1.2.0.19 signature been validated or not.
WRooters tell me their 1.2.0.19 is not validated.  
Still Proceed with caution. 
One friend tells me 1.2.0.19 is not despite prior rendered as verified. 
Each version requires validation.

So, when you went back to 32bit your Filtering Extension renders verified...?
Has there been Webroot announcement 1.2.0.19 is verified. 
 
I have one other extension Proceed with caution. 

Last I heard, FF42 has warning, 43 will have work around and 44 will block unverified.
So, I have some time. 
 
At some point extensions will need to be verified before release.
At some point we'll go filter driver.
 
re: which makes sense since this work-around is not supported by Webroot
the signature of the extension is verified not the install method
 
Hi ?,
 
Sorry for the late response.
 
I did not uninstall the 32 bit version of Firefox first, which explains why I did not have the Web Filtering extension either. After manually adding it to Firefox 64 bit it also is listed as not being verified for use in Firefox (which makes sense since this work-around is not supported by Webroot).
 
I simply uninstalled the 64 bit version of Firefox, it interfered with other addons as well. There is no discernible difference that I could see from the 32 bit version. Unless you routinely have hundreds of tabs open at the same time I don't think it's needed and most wouldn't notice a difference otherwise.
 
If you can, let me know if the Web filtering extension does update on it's own with the work-around. I'm curious if it will. :)
 
Thanks,
 
BD
 
@ wrote:
Hello @
 
I had the META-INF folder as well. I did NOT zip it with the others and the Web Filter works fine .
 
Yes, paste to the Desktop, then zip the 5 files.
 
I did not have the WebFiltering extension either using Firefox 64bit. It works now after manually adding it.
 
 
BD :)
Hello BurnDaddy,
Thank you for addressing my concerns regarding Palemoon instructions e.g., META-INF
Some apprehension following instructions that did not verbatim make sense nor mention Firefox.
There was suggest that my FF update did not populate extension because I had installed x64 along side 32bit.  
Since, you did not have the WebFiltering extension either using Firefox 64bit.
 
1) Did you uninstall 32bit before installing 64bit...?
2) Is your WebFiltering extension showing as verified same as TripleHelix >
https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/Does-WSA-support-Firefox-42-x64/m-p/226512/highlight/true#M20437
 
I've returned Filtering Extension 1.2.0.19 with Palemoon instructions to Firefox x64. 
My extension however still shows Proceed with caution...?
 
I ran amtso phishing test and opened anonymzdotcom with page blocks. 
I don't know if Filtering Extension or RTAP threw the page blocks.  ;)
 
So, for now I'm back in business. 
Hoping, extension will auto-update and stay put and Proceed with caution will catch up to TripleHelix.
 
Thanks!!!   TripleHelix, shorTcircuiT, BurnDaddy et al
 
Userlevel 7
Really, just in case, and also to get any possible issue documented by Webroot, the Trouble Ticket is the best route to go.
 
That being said, I would do them in the order in which I suggested them.  (WSA, reboot, FF, reboot).  Do not accept any offers to save settings on either.  We want a 'clean slate'. 
 
Check the status of FF following the WSA install, in case that happens to help the issue by itself.
 
Even if you do end up having to manually force the web filter into FF once, it most likely will keep up to date thereafter.  At least the is the behaviors I have seen up to this point.
"which likely would be fixed by doing a clean install of both WSA and FF".
 
Which one in what order
 
So, forget the manual install...?
Userlevel 7
@ wrote:
So, release has "filter driver" not active makes no difference. 
Not for the presence, or lack thereof, of the extension.
So, release has "filter driver" not active makes no difference. 
 
"which likely would be fixed by doing a clean install of both WSA and FF".
 
Which one in what order
Userlevel 7
@ wrote:
I'm not on Beta
I did not say you are.  I said, plainly and clearly, that the fact that it works for TH and me is NOT due to us being ON the Beta.  Also, over the last two weeks, I have personally been involved in getting a new Beta user up and going, and he had no issues with the 64 bit version working on either Release OR Beta.  Both have been quite totally verified to work.
 
Your issue is not due to the fact that it just plain will not work, it does for most people.  The issue is with something on your computer, which likely would be fixed by doing a clean install of both WSA and FF.
I'm not on Beta
Beta has "filter driver" active.
Release has "filter driver" not active.
Userlevel 7
@ wrote:
Yes, that's possible as anything is possible even that your beta is responsible.
Do we know of WSA non-beta user that updated to FF x64 and retained extension. 
My FF x64 feels same as 32bit and WSA feels satisfied.
 
Unless, you un-installed 32 by some extraordinary method. 
Note that my 64 bit install wo extension was as happy as 32 bit w extension. 
 
I need to know "officially" whether I'll always have to manual install / update extension forward.
 
As always.  Anything is possible. 
THIS IS NOT OFFICIALLY SUPPORTED BY WEBROOT, and therefore this could stop working at any time.
 
YMMV
1) What version of the extension do you have in Chrome and FireFox?2) You should not have to manually update the extension in FireFox regardless of FF version or which version of the Web Filter you have (Release or Beta).  I have been on the Beta for a VERY long time, and I have not had to manually update FireFox.  I have done several clean installs recently, and have encountered no issues of it being missing or not working in FF.3) It is NOT due to any Beta code.  I have recently talked a new Beta user thorugh the upgrade from Release to Beta... his extensions updated quite fine and automatically, as have mine.    He is on Win7 Pro, 64 bit and has not had any issues with the FireFox Web Filter not working either on the Release OR after upgrading to Beta Code.I have no clue just why you are having the issues, but I would suggest first a clean install of WSA, followed by a clean install of FF if you continue to have problems with the extension being missing or refusing to work.  If these do not fix it, perhaps someone at Webroot could shed some light, and for that you would want to submit a Trouble Ticket.
Hello ?
 
I had the META-INF folder as well. I did NOT zip it with the others and the Web Filter works fine .
 
Yes, paste to the Desktop, then zip the 5 files.
 
I did not have the WebFiltering extension either using Firefox 64bit. It works now after manually adding it.
 
 
BD 🙂
Question about the instructions.
Instructions refer to three folders and two files.
I find four folders and two files.
Do I copy META-INF and presume three folders means four folders. 
 
"Select all three of the folders and both of the files, then right click and select copy".
Following above I'll have four folders. 
 
"Copy them to your desktop".
Should that be paste.
 
"...it is very important that you either copy them to your desktop, because this will not work if you put them in a folder.."
either copy has no or copy.......what does either refer to
 
Yes, that's possible as anything is possible even that your beta is responsible.
Do we know of WSA non-beta user that updated to FF x64 and retained extension. 
My FF x64 feels same as 32bit and WSA feels satisfied.
 
Unless, you un-installed 32 by some extraordinary method. 
Note that my 64 bit install wo extension was as happy as 32 bit w extension. 
 
I need to know "officially" whether I'll always have to manual install / update extension forward.
 
As always.  Anything is possible. 
THIS IS NOT OFFICIALLY SUPPORTED BY WEBROOT, and therefore this could stop working at any time.
 
YMMV
Userlevel 7
Badge +55
@ wrote:
Hello Triple Helix,

Maybe next week Webroot will add relevent info here.  
@ wrote:
It's working here and I didn't have to do anything to Firefox 42.0 x64
_______________________________
Thanks 
@ it could be you as you had both the 32bit and 64bit installed so make sure the 32bit is gone and reinstall Firefox 42.0 x64 then. As I uninstalled the 32bit first and then installed the 64bit version so no issues here.
Hello Triple Helix,

Maybe next week Webroot will add relevent info here.  
@ wrote:
It's working here and I didn't have to do anything to Firefox 42.0 x64
_______________________________
Thanks 
Userlevel 7
Badge +55
@ wrote:
Well, I had tried the unintall install thingy yesterday.
So, I did the uninstall install thingy again. 
Dialog reports Fully Compatible and All Shields and Firefox goes to Application Protection.
 
Only thing missing is Filtering Extension.
Maybe, you guys are running Beta
I had Filtering Extension with Firefox 32bit.
:(
 
Try this as it does work on Firefox as well! https://community.webroot.com/t5/Webroot-SecureAnywhere-Complete/Unofficial-Webroot-filtering-extension-in-Palemoon-Unofficial/ta-p/142217
Well, I had tried the unintall install thingy yesterday.
So, I did the uninstall install thingy again. 
Dialog reports Fully Compatible and All Shields and Firefox goes to Application Protection.
 
Only thing missing is Filtering Extension.
Maybe, you guys are running Beta
I had Filtering Extension with Firefox 32bit.
:(
 
Userlevel 7
Badge +55
@ wrote:
@ wrote:
@ wrote:
32bit uninstalled shortly after 64bit install.... I thought both were causal to no Filtering Extension.
I did not know at the time.  32bit only.
Then do a clean reinstall of WSA and that should install the extensions.
 
Daniel
Oh, maybe I misunderstood.  When I was pointed to [Unofficial] and pointed to reference "32bit only".
I thought I had to manual install and update. 
So, x64 works but, not officially supported....?
Correct and the same for Chrome x64. So since it's not installed the easiest is to do a clean reinstall of WSA.
 
Please follow the steps closely!
 
  • Make sure you have a copy of your 20 Character Alphanumeric Keycode! Example: SA69-AAAA-A783-DE78-XXXX
  • KEEP the computer online for Uninstall and Reinstall to make sure it works correctly
  • Download a Copy Here
  • Uninstall WSA and Reboot
  • Install with the new installer, enter your Keycode and don't import any settings if asked to as you can set it up as you like once it's done
  • Let it finish it's install scan
  • Reboot once again
 
 
@ wrote:
@ wrote:
32bit uninstalled shortly after 64bit install.... I thought both were causal to no Filtering Extension.
I did not know at the time.  32bit only.
Then do a clean reinstall of WSA and that should install the extensions.
 
Daniel
Oh, maybe I misunderstood.  When I was pointed to [Unofficial] and pointed to reference "32bit only".
I thought I had to manual install and update. 
So, x64 works but, not officially supported....?
Userlevel 7
Badge +55
@ wrote:
32bit uninstalled shortly after 64bit install.... I thought both were causal to no Filtering Extension.
I did not know at the time.  32bit only.
Then do a clean reinstall of WSA and that should install the extensions.
 
Daniel

Reply