Version: 24.11. 9615
I opted to run a manual FVS and, after it completed (and I hovered’ over the ‘Info’ button), it stated:
‘FVS Was Stopped Before It Finished. We Suggest Running It Again.’
Is this a glitch?
Thx.
This issue did not occur with previous versions.
Is this the forum for Avast Free Antivirus-related questions?
The layout looks different but no one has replied. Consequently, I wanted to ensure that my post was placed on the right website.
The forum was updated to different software. It is still a work in progress and many things are different now. Some of them quite broken.
The subforum for Avast Free is:
Hello Rundvleeskroket-Thx for the update.
Do you know the answer to my post and.or can you replicate my issue please?
Sorry I don’t have the answer. I just ran a full scan on my PC and it finished without issues.
FYI: this is a user forum where users like myself try to help each other. There are Avast employees about but only occasionally. Maybe another user can help you more.
Have you tried running the scan again?
Are you using the ‘free’ version and the same version that I am using?
Version: 24.11.9615
No software has been installed or removed.
Hello.
I opted to run a manual FVS and it completed without any error messages.
When the scan finished, it stated ‘No Malware Found: We Were Unable To Scan Some Files But No Threats Were Found For The Files We Scanned.’
Q: ‘Why’ weren’t some files able to be scanned?
Answer:
After that, I went into ‘Scan History’ and, subsequently, hovered’ over the ‘Info’ button and it stated:
‘FVS Was Stopped Before It Finished. We Suggest Running It Again.’
Q: Again, ‘why’ would that message appear when the scan ran quickly and completely?
Answer:
The above ‘wording’ did not occur with previous versions.
Consequently, am I missing a detail here?
There could be locked files. Files in use by the OS or other software so that Avast can’t scan them. Although mostly that shouldn’t even be an issue, especially for reads. Can’t you see which files couldn’t be scanned?
I’m running a slightly older version of Avast Free: 24.9
This is because of several issues not yet resolved by Avast, of which there are long threads on this forum. (icarus.exe firewall issues and Avast Cleanup forcing Software Updater on everybody)
In ‘that’ case, upgrade to ‘my’ version and, consequently, you will have the same issues that I am having.
No I most certainly will not, because of said issues. And also there is no reason to assume your problems are due to the version differences. That is an untested assumption.
Incidentally, how do I check which files couldn’t be scanned? As mentioned, it stated:
‘No Malware Found: We Were Unable To Scan Some Files But No Threats Were Found For The Files We Scanned.’
Under 'Scan History-> Info button: ‘FVS Was Stopped Before It Finished. We Suggest Running It Again.’
The scan ran ‘completely’ so, consequently, the above wording is inconsistent with the scan result.
Well, as a ‘heads-up,’ this ‘hidden file issue’ only started with the ‘current version,’ which is, yet, ‘another’ good reason to avoid installing newer versions.
I don’t know how to see those files. Maybe you can’t. They’re probably some system files that are in use. It might be completely benign. Hopefully someone else can give you more specifics.
It could also be password protected archives, like zip/rar/7-zip. The contents of those files would not be accessible to Avast without their passwords. If Avast doesn’t tell you what files it couldn’t scan, I’m not sure there is a solution.
Well you could manually scan subfolders on your drive and see what scan doesn’t complete or says it couldn’t scan everything. If that way of scanning even reports failed files. I don’t know. Maybe that’s a way to narrow it down. Just spitballing. Probably it’s nothing but if you have to know, wait for somebody from Avast or a user who knows more about the inner workings of Avast.
Well, as a ‘heads-up,’ this ‘hidden file issue’ only started with the ‘current version,’ which is, yet, ‘another’ good reason to avoid installing newer versions.
OK. So you have correlation. Maybe if more users do a full scan and report back you could have something approaching causation.
‘Another’ good reason to stick with your current version then.
Like I said, for other reasons I’m still on 24.9
I never auto-update the main program. Only definitions.
Let other people be guinea pigs.
I hadn’t paid any attention to it before because avast said “analysis completed without finding any threats”.
When I saw this topic, I went to the scan history and indeed, I see the same thing (see screenshot).
I used to see such a message during a bootup scan, but it was specified that some files had not been scanned (protected archives)… Here, that’s not the case, it just says “scan interrupted before completion”, which is strange.
I’ve just redone the scan, unchecking “scan archives”, and the problem is still the same. 
It would be nice if avast could clear things up.