Webroot SecureAnywhere Discussion & Update Thread

Not using password manager? Get a rope....

 

I am exactly the same Triple, I always saved my passwords in Firefox and I find it hard to change over, it is the extra password I need for the Webroot Password Manager - I can never remember what it is.

 

Well I just installed Webroot again to see if the spiking issues, and explorer bugs have been fixed.

They haven't. This is a clean machine with only FOUR installed things. Webroot bloats explorer up to over 300mb+, when on machines without it, explorer runs less than 20-30mb tops. Also the CPU spikes on explorer return immediately with Webroot installed.

What gives? Don't say it's a conflict, it does this on totally clean machines with a fresh Win 8.1x64 install. Unacceptable.

 

interesting, do you have the same results with the web filter and toolbar disabled? i leave the toolbar out and on my personal systems i also dont use the web filter from it because i find it to sensitive. but even on clients machines i dont see this type of issue. i know when you first open ie webroot can cause a slight slowdown due to the extensions. but otherwise it runs great after that.

 

Thank you Trip..awesome update as always!!

 

Windows Explorer.exe is a system process, not the web browser. It's core to the windows itself.

Windows Explorer should rarely be over 30-40MB of ram, and never spike CPU/HD.. But with WSA installed, regardless of the settings, explorer balloons up to insane proportions, and spikes CPU/RAM/IO very frequently. Uninstalling WSA, rebooting, fixes the problem immediately.

 

ahh sorry i was reading quickly on my cell phone i thought you wrote internet explorer. ill check my machines tomm and let you know what i see.

 

If you don't use a master password in Firefox, your passwords are saved in plain text.

 

Are those clients running Win 8\8.1\8.1U1 x64? If not, you probably won't see it.

 

It's not only Windows Explorer. This is what WSA does with Windows Firewall Control.

551.3 MB versus 17 MB.

Windows 8.1 x64

See attached.

 

As already said it's using Pagefile RAM https://www.wilderssecurity.com/threads/wsa-v8-0-4-63-beta.360461/#post-2346421 & it's still on the list to be fixed and I will post here as soon it is.

TH

 

Then I have a few questions;

1) Why is it using pagefile on a machine with 16GB of ram?
2) Why is it bloating Windows Firewall up to half a gig of ram as well on a machine with 16gb of ram?
3) Why has this not been fixed after almost a year of reporting it? I recall personally reporting this sometime in September of last year!

It looks like WSA is trying to hide itself in the page file, to make it appear like it is using less resources, when in fact it isn't. So people see WSA files and think 'wow its only using 15mb of ram!', but in reality it's using up to a GIG, regardless if it is offloading that into the page file.

This is unacceptable.

 

Why don't you Submit a Support Ticket and ask Webroot Support Directly or go over to the Webroot Community to post your question as there is no Official Support on Wilders anymore!

Thanks,

TH

 

As you know all tried to convince the OP to submit logs to support but there are privacy issues that prevents OP to contact support but not to complain.... aside from the joking, I see major improvements, now its just RAM before all systems were collapsing...

 

Here is the response I received regarding WSA and memory. I asked this back on December 14, 2013.

https://www.wilderssecurity.com/thre...plorer-and-windows-firewall-control-4.357260/

 

Looks like it won't be fixed then.. A full GIG for Webroot eh?

 

TripleHelix said a few posts above it's on the "to-do"-list.

 

From early 2013? Ok.

 

As I said I will post here as soon it's fixed!

Thanks,

TH

 

okay i see what you are talking about. i did test this today. i see the page file use etc. but i have to say i just dont feel it. webroot just feels crazy light 99.9% of the time. there is the very rare occasion when i feel its there but not normally. i do hope this gets fixed but otherwise i find webroot still very light on the system.

 

AGREED.. It still FEELS very lite, no question about that!

But it actually ends up using between 600mb-1GIG of Ram on a system. Also if you examine the processor use of Pagefile/Explorer/WF you will see WSA actually uses a good bit of processor power. Those constant pagefile swaps - even on systems with 16, 32GB of ram will have an impact over time. There is no reason to use explorer for pagefile use without checking on the system ram unless you are attempting to hide the actual weight of the product itself. At least I cannot see a reason for it, and haven't run into any other product that does this.

I wonder.. With pagefile/caching OFF, what would WR do? I need to test this, and see how it behaves when I get some time.

 

im testing that right now actually. i have shut down the pagefile on this system and ill give it a few days and let you know how it works out.

 

Shutdown pagefile, reboot, and the results should be immediate. It doesn't free up from WSA until a reboot. Let us know what happens. Also try shutting down Windows Firewall manually via Services, and see if WSA drops off it's bloating of the WF application. I would be interested to see how a machine acts when both of these are done.. WSA should be extremely light.. With 12, 16, or higher ram the pagefile isn't an essential thing anyway so disabling shouldn't cause any issues.

 

SOME programs require a pagefile for some reason. Even if they don't use it, they check for it. I'd be curious to see where WSA fits in here, and in fact I may test this right now as my curiosity is overwhelming. Another alternative is to make the pagefile 16MB (minimum) in Windows 8.1x, and see how WSA handles things then.

My questions would be;

1) Does WSA bloat up to 500mb-1GB when the pagefile is restricted?
2) Does WSA function when the pagefile is eliminated?
3) Does the Windows Firewall Control being disabled cause WSA any issues?

It would be interesting to see a system with WSA, WindowsFW disabled, Pagefile Disabled. Then turn on pagefile, but limit the size, and see how WSA is impacted.