It appears that avast is once again detecting its own files as “warnings”.
The results are “some files cannot be scanned” again! ??? :
Cause the access to the files is blocked by Avast itself.
But i dont know why they are listing their own files there.
It happened before during beta testing and with again after the final release.
I’m not that concerned since I know what they are, but a newbie won’t know. 
Pondus
4
Files not found errors are usually gone if you reboot and scan again
DavidR
5
As a regular in the forums you should know that this is, the removal of old defs folders by avast housekeeping 
Had you taken the time to expand the File Name column to see the full paths you would see it is in the defs sub folder and indicates an old VPS folder.
Yes, I do know that. However avast had finished its housekeeping fifteen minutes “before” my weekly scan even started. ???
And only two streaming updates happened during the scan. ???
DavidR
7
I don’t know who you can state when the avast housekeeping completed, as I don’t know if it has a set schedule.
Streaming updates received during a scan have nothing to do with the defs folder housekeeping of VPS folders removed during housekeeping. I had 13102602 VPS and 13102602_stream prior to my scan starting.
I received 5 streaming updates during the rough time frame of my scan, but hours before the oldest defs folder was gone 13102601, as was its 13102601_stream folder. So I haven’t a clue what time avast did its housekeeping.