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

[REDACTED]

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?

[REDACTED]

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!

[DavidR]

@     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.

[REDACTED]

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]

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]

Should be fixed in the next version.

[REDACTED]

Updated Avast to latest version and bug still there.

[Asyn]

Updated Avast to latest version and bug still there.

See Reply #20.

[REDACTED]

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!).   

[REDACTED]

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

[Eddy]

Keep an eye on the beta development.

[Jerry8]

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!

[REDACTED]

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]

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]

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.