This has happened to me a couple of times in the last week, and I wanted to know if it was something I should be concerned about. When I run the recommended deep scan, WebRoot freezes up when it reaches 81% completion. The system events counter will continue to increase, but the actual progress of the scan appears to halt. If I try to run another scan during this time, it will make it to 100% without any problem. If left alone, the scan will eventually unfreeze (although the total scan time may take 6 or 7 minutes as opposed to under 1 minute under normal cisrcumstances). Even when it doesn't freeze up, there often seems to be a "pause" when it reaches 81%.
I also ran a Full Scan to see what would happen. It scanned slowly, as expected, but once it reached about 80% or 81%, it quickly finished and informed me that the scan was finished.
I haven't experienced any other problems on my computer, but I wanted to ask about this just to see if it was anything to worry about. The other times I've run the deep scan (or it's run automatically), it has performed fine and told me that everything is in order.
Best answer by RetiredTripleHelix 8 December 2013, 20:33
The e-mail I got was from firstname.lastname@example.org. There was a link at the bottom
which leads to a different page, without a phone number.
I replied to her, declining to carry the conversation any further because I didn't lose any money and am not using Avast any more. But I offered to tell my story formally if they're engaged in any action against iYogi and it would help.
At my work place, iYogi is VERY well known as a scam outfit that appears to be the support for quite a few different companies. Most often people google search looking for a legit phone number for a company like Avast and get sucked in. I have seen people get them when they were trying to get Webroot, etc etc etc.
A bit more adventure to my interaction with Avast. Their customer service got back to me after I griped about their tech support guy. Instead of looking to solve the Avast problem, he found the now-empty conduit directory, claimed it was a sign that my system was badly infested, and offered to clean it for the bargain price of $169. Flat refused to look at the actual problem unless I paid up. Turns out Avast's phone support number takes you to an outfit called iYogi that has a track record of that kind of thing.
Also, you may find this interesting: Antivirus Remover. (Information is available here) Don't let the name scare you; it is just a program that lists all the cleanup / removal tools available for all the common AVs and has the web links for the tools.
But if you google "avast cleanup tool" the link to it, and to a bunch of sites that talk about it, pop up.
It doesn't clean all of the stuff out of the registry, but it gets rid of enough of it and nukes the installation directory so the flotsam has stopped.
I think my original hangup was the external drive. Whe I ran a separate scan on it, it went very slowly: 25% done after 6 hours. I killed it, and will scan it later on a newer machine. The original scan probably got to 99% when the internal drive finished, then it went to work on the external drive.
Last night's final adventure was when my previous virus program, Avast, got in its last licks by not fully uninstalling. I made the tactical error of calling the phone support listed on the Avast web site. All is well after I taught the tech/salesman a few new words, hung up, and found their actual cleanup tool.
It is a relatively recent addition to Webroots detection engines, as Webroot has historically not acted on this type of annoyware. I am very glad that the 2014 version of WSA now includes some PUA detection, and more are being added in regularly!
Grab a chair and stick around with is.. we don't bite 🙂 and this is a great place to learn more!
I'm now kind of in a loop as it finds malware, cleans it, then rescans. Malware has mostly been conduit searchprotect components. Not exactly the John Dillinger of malware, but I'm very pleased that webroot hates it while my prior virus program let it be.
Since you got the install scan done stop the scan and do a reboot to set the drivers also make sure you got a good internet connection if you still have issues post back for further instructions.
We are not too picky, and we are easy to get along with: it is fine to add to an existing thread with the same problem OR to start a new one of your own! (The Moderators will sometimes move things around if they think it has nothing to do with the original thread, but don't worry yourself about that!)
That scan time would appear to be far far too long: while the first scan does take longer, we are usually looking at times measured in several minutes for that as opposed to the normal scan time of under a minute. An hour is way too long.
If you have an external drive connected, I would go ahead and cancel that scan. Disconnect the external, maybe reboot, and try the scan again. If the scan then completes OK, reconnect the external and scan ONLY it.
Let us know what that does.. and we will go from there 🙂
I'm also having trouble with a scan freezing. It's the initial scan after installation on an XP machine. It's been at 99% for an hour or so. It says "Performing Central Analysis..." There's a green check next to all items in the dialog.
Should I kill the scan and look for some of the issues discussed in this thread? Maybe disconnect an external drive? Or let it sit longer?
Thanks for any help.
Now that the issue is solved, pull up a chair and hang around a while. This is a good place to learn about a lot of related topics!
Inquiring minds want to know!
You mention that on a Deep Scan it freezes at around 81%, and around the same on a full scan.. I am not the most knowledgeble person here, so hopefully Webroot will reply soon as well, but I wonder if it might be a file issue on the hard drive. Possibly something that hard drive utilities such as a defrag or scandisk might help with?
I have seen this happen on a few computers so it's not unique and I would not be concerned at this point. However, I'd appreciate it if Webroot could chime in with a technical explanation.