Best answer by explanoitView original
Best answer by explanoitView original
Already have an account? Login
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.
I believe that is correct unless one is suffering from the issue where the installer is unable to determine the correct path for a browser (in my case FF) and no number of uninstalls/reboots/clean installs will result in a successful install of FF (in my case). Support have advised me (as I stated in another thread) that this is a known issue and that it should be rectified shortly.
For me it affected FF whilst IE has installed originally 188.8.131.52 successfully and since then this has silently been updated to 184.108.40.206. What I do not know is whether the installer issue, which apparently is not general, affects only FF or if in soem cases it can also affect IE instead of or even also.
Although from what yeoldfart is reporting it looks like he may be suffering from this too but IE-wise.
Anyway, am waiting patiently for the rollout of the fix which should be in the next release (but I do from time to time check FF to see if I am prompted for the addons install, and once a week I uninstall/reboot/clean install WSA...also just in case...but so far no change.
I just keep saying to myself..."patience is a virtue", etc.
Do you know the HTTP link to the source CAB file that the WSA client is downloading and extracting?
I have distributed the URL via private message. Please respond to this thread if it resolves your issue and Send me a Private Message if I missed you in its distribution.
Regarding the update that has been mentioned in recent posts to fix this problem in IE 11...Does it cover both 64 and 32 bit versions of IE11? And if so, when will it be rolled out, as ive just uninstalled/reinstalled WSA again as suggested and it still doesnt work?
If you have the new Web Shield and listed in IE11 as far as I can see now that IE runs both 32bit & 64bit processes at the same time and it works with my Win 8.1 x64 IE11 but as far as I know 32bit Browsers are only supported unless things have changed maybe a Webroot Staff member can confirm that would be great.
Have just tried to replace the contents of the CAB into the WRDATA folder and whilst IE still works, albeit with v220.127.116.11 FF is still not showing or recognising the Webroot addons.
I still believe that Lucas (in Support) is correct when he says that the FF issue is related to an installer issue that will be fixed in the next release. May be worth having a quick word with him if you can on this. :D
You must put the Firefox files into a ZIP then rename it to a .XPI file. Then you can drag it into the Firefox window to install the plugin.
I have absolutely no idea how I knew to do this...
Thanks but I have absolutely no idea what you mean...;)
What files into a .zip that is then renamed to 'what'.xpi...if you do not mind me asking?
Will give this a try shortly and post back the results...fingers crossed. ;)
Yup, that worked. :D
First time I created the .zip/renamed to .xpi from the wrong level of the .cab contents but eventually managed to create 'WebrootSecure_SocketServer.xpi', dragged to FF main browser page and sure enough it was recognised and installed. Restarted FF and had a bit of a fright when the Google banner appeared to be over large???? but closed down FF, restarted, ran a Google search and hey presto! Little green ticks to the left of the proposed urls.
Excellent. I think that we have a solution here (at least for FF but presume that something similar, i.e., extract the relevant elements and name the resulting .zip in the cases of IE & Chrome...if required?
explanoit...many thanks for that. Nice one, mate.
For Chrome, drag the .crx file into the Chrome window. I haven't tried this in a long time but it should work?
For IE that will require a Webroot installer as WRSA.exe maintains a lock on some of the files. Trust me you don't want something I hacked together, I barely understand IE addon registration - only enough to be dangerous :cathappy:
It is OK...I don't use Chrome but was interested as I believe there are a couple of user here who have had issues in that area. As for IE...I believe you...but luckily for me the IE version is working perfectly on my system.
Thanks again, Baldrick :catwink: