Discussion in 'other anti-virus software' started by Triple Helix, Jun 6, 2014.
Manually protecting the Edge Browser does indeed show the gold lock, but it has dramatically slowed down opening the browser. Deleting the entries corrected the slowdown.
Well I have not experienced any slow downs on my 2 PC's and not heard of any other complaints.
Hey there BMW I haven't been using WSA for a while so I thought I'd ask if there's been any change regarding WSA Identity Shield and HMPA keystroke encryption?
I had noticed something as well as I use WSA with HMPA.All settings default on HMPA and WSA.I had noticed that when I go to type in login credentials into https pages like some banking sites I use,random letters and such would appear instead of what was typing.I have contacted HMPA support on the matter.I did not contact Webroot support because I believe this to be an issue on the surfright end.I had no issues in previous versions of HMPA when used in conjunction with WSA.I removed HMPA for the moment. Sounds like my problem might be similar to the above.Will keep the thread here informed of the result of my exchange with surfright support.
In the past when I had WSA on my Win 8.1 machine, I didn't have this issue, only that the HMP.A keystroke encryption indicator would not show unless WSA Identity Shield was turned off.
Others (like @Victek in the post above) also experienced this. See this and this.
But keep us posted.
I don't use HMP.A but WSA's Identity Shield is all you need for online protection so I can see why these two would clash in these cases.
But it doesn't hurt to contact Webroot Support and ask them. Webroot Customer Service
TH - I did try and pursue my issue with them, but unfortunately they couldn't reproduce it
Yes, the conflict is understandable.
I haven't heard back from surfright support yet,but I have reinstalled HMPA and disabled keystroke encryption and all is well.No issues that I can see.I cannot reproduce what was happening.That is a good thing.I purchased HMPA mainly to help support the excellent work the Loman brothers have done.It's another layer that gets along well with WSA overall.I know I do not need it.I haven't had anything get by WSA since the beginning.I now use it on 1 windows 10 tablet,1 android tablet,and 2 windows 10pcs.All is well on all fronts.
Actually I didn't report about the keystroke issue, though HMP.A's indicator works intermittently here.
What I did report about was the fact that HMP.A was not able to block all exploits with the exploit test when the process being exploited was protected by Identity Shield. I contacted Webroot support about this, but that went nowhere.
Thanks for the clarification.
You mean HMP.A was not protecting due to WSA protecting you or both failed?
WSA didn't block it either, so yes both failed, but I don't think WSA's exploit protection is as advanced as EMET/HMP.A/MBAE.
True as they concentrate on the payload then WSA reacts.
hey TH had a couple more laptops with the uac issue show up today at the office and these are 2 that i fixed after the last time already (reset uac after the update to resolve that issue) so the uac got jacked back up to max again somehow on these 2 systems. totally different people really not much else the same except win 10 x64 and webroot and libre office. otherwise very different systems. just wanted you to know. hopefully it will not be a major issue this time. im crossing my fingers it was only these 2.
If it continues contact Webroot Customer Service and they will look into it.
SecureAnywhere™ Mobile for Android
Version 126.96.36.19961 (Released March 7, 2016)
Improved performance: longer battery life, faster, lighter footprint.
Enhanced protection with definitions that are now fully cloud-based. Definition updates are no longer needed, as they are always up to date.
Various bug fixes.
Webroot's Android Security App is now Full Cloud: http://www5.nohold.net/Webroot/ukp.aspx?pid=10&app=vw&vw=1&login=1&json=1&solutionid=1039&
i would test it, but i guess i will need a beta-tester key?
@guest look for a PM.
Not sure if anyone is having this problem. I am getting alert from Windows action center sometimes everyday that Webroot is turned off. May be it is getting upgraded too frequently?
I had this issue too.
I gave up running HMPA with WRSA a while ago, there were several conflicts which I could not pin down. Clearly the two are not designed to co-exist, although they might, but I would not want to trouble Webroot support with such a conflict, it's my problem not theirs, I don't want them wasting time on trying to make WRSA compatible with everything out there, just focus on them becoming the best product.
I also had problems with HMPA with Windows Defender 10, with on a new machine with video drivers crashing. I'm coming to the conclusion that sometime less is more. What I mean is thatless features or less layers can give better results or less hassle.
Now just trying to run WD 10 and WRSA side by side but needed to the registry tweak to achieve that. I uninstalled HMPA and just run a regular scan with HMP.
I think this is a known issue, there seems to be a thread on the official forum
Being I was able to pin down my issue I was having with HMPA and WSA,Lisa in support has passed it along to the development team at surfright.I was able to eliminate an issue I had by 1)disabling keystroke encryption in HMPA or 2)disabling Identity shield in WSA.They both have some mirrored functionality,and it's only logical that having 2 programs that were encrypting keystrokes,that something like my issue was bound to happen.And there can also be clashes or instability between programs if they are using wfp.SO many programs are using wfp anymore.HMPA uses 1.Adguard can use 1 if you want to filter edge.And quite a few suites use them.Typically if your suite uses a wfp driver,whatever you layer with it probably should not for sake of stability.I blame MSFT in this.It's not a guarantee of issues,just that there is potential there.
At the risk of being OT, regarding multiple drivers, yes, I asked that here. I wonder if mutual exclusions of each others processes helps with this.
If I had your issue running WSA and HMPA together, I would probably be inclined to keep WSA Identity Shield enabled, and disable only the Keystroke Encryption in HMPA, as I believe the Identity Shield does more than that.
Does WSA use a WFP driver?
HMP.A keystroke and protection border seem to cause issues on some specific systems.
@paulderdash - gives good advice. WSA protects against keylogging in the browser - but that is it. However, browser is most vulnerable to keylogging. WSA won't protect against embedded webpage script keyloggers - and neither will HMP.A.
Separate names with a comma.