AVAST Premium Security has a problem with scanning a cache.db file

Avast Free Antivirus / Premium Security
1

Hi,

I am an AVAST user.

It appears that AVAST Premium Scanner is having a problem scanning the file below on my system.

C:\Users\DummyUser\AppData\Local\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\LocalState\EBWebView\GPUPersistentCache\DawnGraphiteCache\QFRPRRKRKWZNTFMPUJZIPW2HOZ5QE2WL\cache.db

This problem appears to have started around 10th June 2026.

The “Full Virus Scan”, “Explorer Scan” and “Targeted Scan” all complete and find no threats but they state “The … Scan stopped before it finished. We suggest running it again.”.

The “Boot Scan” completes without any errors that I can see.

I have narrowed the problem to this cache.db file. This file is not locked or in-use and I can successfully delete it.

All the scans complete properly, without the message “The … Scan stopped before it finished. We suggest running it again.”., if I delete this file and then clear the “Recycle Bin”.

This file is recreated by Windows upon reboot and the error reappears.

I have Reset and Repaired AVAST Premium Security several times but this does not resolve the problem scanning cache.db.

Doe anyone have any idea how to resolve this?

1 Like
2

I have the exact same, except Avast says at the end: We were unable to scan some files, but no threats were found in the files we scanned.

3

Hi Zango.

Thank you for you response. Yes, I am getting the same message as you in the AVAST scan completed window.

The messages that I stated are shown in the AVAST Scan History.

I have done some further investigation and the “cache.db” file mentioned appears to be related to the Windows 11 “Search” functionality. Specifically the Web Search component.

This problem seems to have started following the Microsoft Update for June 2026 which was released on Tuesday, 9th June 2026 at 18:00.

I am not sure if Microsoft released any patches or updates to the Windows 11 Search functionality as part of these recent monthly patches that may have caused this AVAST problem.

Thanks.