Slowdown When Running Programs for First Time

Anyone?? Am I the only WSA user on Wilders who runs multiple user accounts, or has no-one else been able to duplicate this issue?

 

Hey Zorak, I feel your pain. BUT, I am not having any slowdown issues with WSA Essentials and I user multiple user accounts with Win7 x64 Home Premium on three systems.

I did have slowdows with Prevx (the free Facebook version); my system would scan the same AV files each and every time I booted. That's not all Prevx would scan; the AV files were the first ones that I could think of.

 

Thanks kdcdq. I never had any problems with Prevx, only WSA! Aren't computers wonderful

 

It's kind of like beating yourself in the head with a hammer; it feels so good when you stop...

 

Hi all, for those who are interested here is the latest news:

After submitting various logs, dumps and Process Monitor traces plus a phone call and remote session with two Support Staff (one in the US and the other here in Oz), Webroot have been able to reproduce the context scan issue. The matter has been escalated to Software Development for a fix, and it is hoped this will lead to correction of the slowdown behaviour when opening new programs.

I must give a big to Webroot Support. They were really keen to help and seem to genuinely care about the quality of their product. In fact they initiated further contact even after I had pretty much resigned myself to never finding the answer. Thanks U.S. Joe (not "our Joe" - another one!) and Aussie Angela for all your assistance

Can I ask PrevxHelp ("our Joe") how long do these types of fixes normally take to make it through the works? I realise this is probably low on the scale of priorities, but it does get a bit annoying sometimes, so I am definitely looking forward to a fix!

 

Hello Zorak,

WoW that's fantastic they do go out of their way to try to correct any Issues that users might have! Today's Webroot = Great support and no Crapware, sounds allot like Prevx and I'm Glad they have taken that route thanks to Joe and Mel Morris and the integrated Prevx & Webroot Teams!

TH

 

Hello!

Thank goodness your thread exists. I logged in just to complain about the same exact problem, because it's been 6 days since I've emailed support with zero response.

I noticed the problem happens mainly with Chrome.

Here's a copy of the e-mail I sent to Webroot:

"Hi, I noticed whenever I open a Chrome window, my CPU usage will spike. The past few times, it has been maxed out to the point where I couldnt even use the computer and had to do a hard reboot.

I confirmed this was a problem with Webroot SecureAnywhere because the problem did not persist after shutting the program down, and I could reproduce the 100% CPU usage every time with WSA running.

I suspect it might be the Identity shield, which I have activated. In the "view/edit protected applications", I've set all Chrome .exe's to "allow".

I've tried disabling all Chrome plugins to no avail.

Windows setup: Win 7 64-bit / Intel Q6600 2.4ghz quad core, 8GB ram, 145GB C:\ drive with 80GB free.

Programs installed that may be suspect (but again, I do not want to disable), are : Strokeit (a mouse gesture program, also set to "allow" in Protected applications) and Dexpot (virtual desktop application, which fails to work if I set Chrome to "protected").

My WSA is running version 8.0.1.165, the latest version as of 4/9/12. (Ignore the product selected in the ticket form)"​

As a new user of Webroot SecureAnywhere, I'm pretty disappointed in this hiccup.

I don't know how long they're going to take to fix it, and I don't really feel like waiting. I was a happy NOD32 user before switching, and had zero problems with it. I am most likely going to uninstall WSA and just stick with what WORKS, instead of spending hours fiddling around with this.

Good luck guys! Back to the land of ESET!

 

I'm not sure your issue is the same as mine. I only experience problems after logging off and logging on again, and then only when doing a "right-click" scan or opening a previously unopened program. No CPU spikes - just a long wait for anything to happen.

I can only guess your e-mail got lost or something because they always replied to me within 24 hours. All my correspondence was done directly through the support website - not regular e-mail. They would however e-mail me to let me know when a new support message had been sent so I could check back in on the website.

Sorry to hear of your bad experience, but I'm sure PrevxHelp will be along soon to look into it for you.

Cheers.

 

I was gonna say, sending email doesn't work. Webroot doesn't have any email-based support. Support is acquired by going to the support site at https://detail.webrootanywhere.com/servicewelcome.asp and signing in (or creating your new account there) and then runs entirely on that site. Or to their forums at http://community.webroot.com/, though they often need to send people to the main support site if they need to gather logs or stuff.

Sending an email will only get to an unmonitored mail box or to the old support system that they shut down, but that system sends a message back saying to use the new support system.

What email address did you send it to? Webroot people watch this forum too, and several people who help on the forum can get general answers if they don't already know.

Edit: Took a closer look at the email details. I'd bet that Dexpot isn't well-known, and since it "meddles" with the browser, it's causing the browser to be monitored, which will slow things down because Chrome is weird. ^.^ Get in touch with support via the web site directly and I'm certain they'll respond much more quickly. (I still would like to know what email you sent to though and where you found it.)

 

This will hopefully be included in the next round of updates, due out in the next 1-2 weeks with a number of other improvements.

Thanks

 

Cool - thanks!

Hopefully in some small way I may have helped make a great product even better

 

Thanks for the help guys.

I sent a 'support ticket' by clicking on the Help in the program itself. I did sign in and sent a ticket. I didn't dig up a random e-mail. Sorry for the confusion. I don't blame Webroot for their lack of response. I've grown accustomed to companies not providing support, so it's no biggy. (Thats why I'm on this forum now asking you guys anyway :] )

This also happens on my freshly formatted laptop w/ no software. So it's not any of the programs or plugins.

My mistake if it's not the "same problem" the OP posted. I felt it similar enough to not warrant a new thread.
Slow down is slowdown. Whether it's opening a new program for the first time, switching users, or whatever the cause. It's still slowdown to me. It's still caused by WSA. And it's annoying enough for me to uninstall.

Like I mentioned before, I don't have the time to poke around and play with every setting. I feel that the software shouldn't lock up BOTH my computer and laptop, causing me to have to do a hard reset, it should just work.

With that said, I'm disappointed, but not angry. After all, it was only $10 (I bought two $5 3x licenses out of excitement+hype), so not a big loss. Going to stick with what works for me.

I kept this window open just to read the responses, but I think I can just leave with closure, so I wont be seeing any more replies.

Thanks guys, and good luck!

 

If you could PM me your email address, I'll take a look at what could be going wrong so that we can solve this.

Thanks!

 

Just thought I'd update this thread as the problem I was having seems to have been mostly solved

After running version 8.0.2.14 for a couple of weeks on both PCs I've found that following a log-off event, on-execution scans are now being processed much faster. Any delays are now measured in seconds rather than minutes - except when the "Show Authenticating Files Pop-up" is selected. When this feature is turned on the same old behaviour occurs. This is not a major problem however, as I only really use this function to monitor the slowdowns. As the slowdowns are no longer occurring then I can happily live with this setting disabled!

This setting had been turned off in the past with no luck, so the new version seems to have improved things considerably. Thanks to Webroot Support and the Development Team