Avast Free - Quick Scan Cancels @ 99%, Full Scan Not Working

system · 2017-04-26T12:45:21.000Z

Program version: 17.3.2291
Build: 17.3.3443.0
Virus definitions: 170425-2
Platform: Windows 10

(Values correct when email drafted today. Conceivably I was on slightly earlier versions when starting the problematic scan yesterday).

These problems are still unfixed. Surprising, as I read above that they were known problems at the beginning of the month.

I started a full scan yesterday. It stayed on 0% for several HOURS, so I left it running overnight (I have a lot of disks).
In the morning it had finished with a message saying that the scan had been cancelled at 98% complete.
Having said that, the results appeared to be complete.

These bugs aren’t just a minor irritation for experienced users. Try putting yourself in the shoes of an inexperienced user who is worried s/he has just been infected. S/he starts a scan and nothing happens (ie, progress stays at 0% for ages), so s/he worries that the infection is preventing the anti-virus software from running. Then s/he sees a message that the scan has been cancelled - s/he didn’t cancel it, so the infection must be to blame. And what do you do if an infection has bettered your anti-virus software? - you switch to another vendor’s product.

Avast developers… in my opinion leaving glaring bugs like this unfixed for weeks will cause you reputational damage, so I suggest you fix them pronto.

DanTheMan · 2017-04-30T15:41:18.000Z

I have been having this problem too for a few months. I schedule a full scan to run very early every Sunday morning. It should be completed by the time I get up, but often doesn’t seem to have run yet. When I check later in the morning, I get the Scan Failed - 99% message. If you click on Details, another full scan immediately starts. What’s up here?

Related to this is that, after this full scan has run, the computer will not restart correctly - either manually or as part of an application update. It gets partway, then just locks up. I need to do a hard power-down, then restart. Once this has been done, the computer will restart correctly when invoked.

DavidR · 2017-04-30T15:54:00.000Z

dknauer post:14:

I have been having this problem too for a few months. I schedule a full scan to run very early every Sunday morning. It should be completed by the time I get up, but often doesn’t seem to have run yet. When I check later in the morning, I get the Scan Failed - 99% message.

If you click on Details, another full scan immediately starts. What’s up here?

Both of these are acknowledged bugs, yet to be squashed in the current versions 17.3.2291.

Also see https://forum.avast.com/index.php?topic=201589.0.

system · 2017-05-13T08:32:03.000Z

Hello I’m running Avast Premier Version 17.4.2294 (build 17.4.3482.0) and I’m still getting the bug that says 99% canceled on both quick scan and full scan. When is the bug going to be corrected?

system · 2017-05-15T22:44:10.000Z

Hi,

I see that this is a bug. (Encountering it on a Windows 7 machine.) However, before finding this thread, I ran a repair and was notified of a conflict with Malwarebytes. That was really odd, b/c I’ve been running MB and Avast together for ages.

Just thought I’d mention it, in case it helps to further pinpoint a problem.

I ignored the conflict because I felt it just couldn’t be true! ;D

DavidR · 2017-05-15T23:12:04.000Z

@ jpbernhards
It has been a recognised bug and one that was supposed to have been squashed, but it appears to be back.

MBAM 3.x has changed much and is also checking for things outside of its traditional malware scan. I stopped using MBAM as it became too much of a resource rather than a good companion for avast.

system · 2017-05-17T08:11:37.000Z

I have the latest version of “Avast Free” installed on 3 PCs, all running Windows 10 and I’ve been having the same problem for months. One of my PCs had a HDD failure. I replaced dive, reinstalled Win10 & downloaded Avast onto a clean system, but still get the same problem.

No reassurance is provided by “technical” explanations such as it’s just a GUI problem. Being told every time I run a scan that it has not completed is causing me to loss confidence in the program.

I certainly would not upgrade to a paid version (which I have been considering) while this problem continues. From the posts on this forum I’m beginning to get the impression that the developers are no longer interested. If the issue/bug isn’t fixed soon I don’t think I will feel “safe” continuing to use the product. A great shame for an otherwise great program.

frank479 · 2017-05-20T20:26:58.000Z

C’mon Avast… let’s get this fixed. I started noticing this back when you updated the app in March, came in here and found out that it was a known identified bug, you’ve updated the app twice since then (in April and May) and this bug is STILL there. I wouldn’t think that this is more than just a GUI problem… it can’t be that difficult to fix!

Asyn · 2017-05-20T20:34:33.000Z

Should be fixed in the next version.

system · 2017-05-21T12:09:11.000Z

Updated Avast to latest version and bug still there.

Asyn · 2017-05-21T12:10:46.000Z

zonkeroo post:22:

Updated Avast to latest version and bug still there.

See Reply #20.

system · 2017-05-22T04:50:03.000Z

I’ve been getting this message, too (full scan cancelled – 99%). I have Windows 10, paid version of Avast, and MalwareBytes. Just started happening a little while ago. Only recent change I’ve made is to download CCleaner, but I haven’t used it for a registry clean yet (got enough problems!).

system · 2017-06-01T11:08:37.000Z

Any idea when the update is being released? It is inexcusable that this bug has existed for so long.

Eddy · 2017-06-01T13:19:28.000Z

Keep an eye on the beta development.

Jerry8 · 2017-06-01T13:43:09.000Z

I have been getting this issues for several months… and NOW its showing up on other PCs once an programmed a Schedule to scan daily overnight… for Both Full and Quick… This is going on STUPID. it been an issue for several versions yet no-one can fix it… Whats up Avast… You guys/gals were always top notch in my mind, but now it just getting worse. The interface is gotten worse and “STUPID”, a circle with a % of completion… Where my DETAILS of what is currently being scanned or at the least an button to show what is currently being done… but now… DUMB down the interface and take away and import info that’s going on… ugh!

system · 2017-07-01T10:25:17.000Z

The GUI for the Full Scan shows 0% on the latest version 17.5.2302 too although it was completed. Will this ever get fixed?

Asyn · 2017-07-01T13:57:42.000Z

legaldeejay post:28:

The GUI for the Full Scan shows 0% on the latest version 17.5.2302 too although it was completed. Will this ever get fixed?

No problems here, it works for me.

Alikhan · 2017-07-01T14:08:38.000Z

legaldeejay post:25:

Any idea when the update is being released? It is inexcusable that this bug has existed for so long.

Is if fixed if you are running the latest version. 17.5.2302.

Also, to clarify, the scan did not cancel and worked as intended. It was just that popup was showing wrong information that the scan was cancelled when it wasn’t.

frank479 · 2017-07-14T22:05:14.000Z

I’m sitting here in disbelief. I upgraded to the latest version, 17.5.2302, rebooted, the automatic quick scan ran and completed and the dialog box actually showed the scan completed! I was about to give Avast kudos on a job well done and I clicked on the details button and instead of taking me to the page with the scan results, it starts doing another scan. Sort of like how the previous dialog box worked when you clicked on the dialog box. I just can’t believe this. Then, I launch the program, I click on the red notification bell, see the listing of the scan results there, clicked on DETAILS and it starts another scan. I don’t know what to think right now. Can it really take a good portion of a year to get a dialog box working correctly? It almost seems like the problem was never fixed- they only changed the dialog box behavior. Shaking my head right now…

Com’on Avast!!

system · 2017-07-16T07:59:35.000Z

This issue has existed for a very long time and although stated to be being worked on I am not convinced that Avast are interested in resolving it.

Too many bells and whistles seem to have been incorporated in AVAST with every update.

After many years of use I have to consider moving to another AV program to avoid the continual Avast irritating problems.

Announcements