Full virus scan stops before finishing

Avast Free Antivirus / Premium Security
1

For the past full weeks my weekly full scan has reported that it has stopped before finishing. This has been happening to other Avast users. Although I’m using Avast Business Cloudcare, it’s also affecting users of Avast Fee a/v and also Premium security. So I’m posting this as being of general interest to Avast users.

I have identified one specific file which is causing this message.The pathway is:
C:\Users\myname\AppData\Local\Microsoft\Edge\User Data\GPUPersistentCache\DawnGraphiteCache\lengthy list of letters and digits\cache.db
I use Windows 10 Home version.. The message started with the issue of Edge v 149 in early June but the message remains after the issue of Edge v 150.

Another community member who uses Premium Security also tracked down the file responsible. It’s the same file as I identified other than in a different location. The title of that topic is “AVAST Premium Security has a problem with scanning a cache.db file” and was posted on 13 June. The pathway shown there was:
C:\Users\DummyUser\AppData\Local\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\LocalState\EBWebView\GPUPersistentCache\DawnGraphiteCache\QFRPRRKRKWZNTFMPUJZIPW2HOZ5QE2WL\cache.db

Repairing Edge and repairing Avast has no effect.

My version of CloudCare is v 26.4.2896. It is possible that a later version has dealt with this.

2

If you enable the report file for the particular scan and scan that file again - do you see a line with an error for that particular file there (the report would be located in c:\ProgramData\Avast Software\Avast\report)?

3

The error line for that file ends with:
The process cannot access the file because another process has locked a portion of the file (33)

4

This seems to be just an incorrect display in the Scan history panel. I simulated it on my computer and the report file shows that the scan finished successfully (there were other files scanned after that cache.db one), just the one file couldn’t be scanned because it’s locked by the owning process.

1 Like
5

I thought it would be just an incorrect display in the Scan history. I had realised that the scan continued after that file as I could see on the progress screen during a scan that after dealing with the c drive it went on to deal with an external drive.

Hopefully, Avast can rectify this so that the incorrect display doesn’t continue so making people think there’s a problem where there isn’t.

1 Like