For the first time, after a 'Deep Scan', Avast One says it did not find any problems, but there were files it could not scan

For the first time, after a ‘Deep Scan’, Avast One says it did not find any problems, but there were files it could not scan. But - I how do I find out which files it could not scan? - so I can make sure these 'unscanned files aren’t in any way a threat?

First, I’m an Avast user and not an Avast Team member.
Plus I’m not using Avast One where the components and customisations are different.

That said I don’t believe this has changed in all of the time I have been using Avast Antivirus Free (21 years).

Files that can’t be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.

  • Many programs (usually security based ones) password protect their files for legitimate reasons, there are others (and avast doesn’t know the password or have any way of using it even if it did know it).
  • Others could be very large and or highly compressed highly compressed and would be impractical to unpack to scan.
  • With an on-access scanner like Avast these files should they become active or are unpacked would be scanned by the File System Shield.
  • A long very long time ago there used to be a means of checking log files, but I can’t remember it.