The point here of course is to provide scope for you to pass on your knowledge about issues that may arise when the random user is running the avast antivirus program and other things relevant to that program. Main thing then is that you may speak your knowhow, no matter what empty head curve ball the newb may have pitched you.
So I say this being a bit cheeky but not intended nasty - so what about kernel32.dll, winsock.dll, and winsock32.dll in the chest, they not doing their job? They can do nothing within the chest?
I said my example would be the rare occurrence - I was talking about situation where an important file for the running of the computer had mistakenly been marked as risk because, say by chance, some wrong combo of words and numbers had matched too closely some ID and detection prescript in the vpu stamp of the time. Say happened in a boot scan, so I wasn't there at the time. I expect that the file would continue doing its job (this is what I meant) and so computer would still be smooth running. And you answered my question about whether to click Restore with an affirmative. All good.
Rare occurrence true, or perhaps this would not happen at all. Its just that people have posted in about good system files being sent to the chest, and what if you delete them, and so on. So I was just raising a query about a potential random scenario that would in time require for the user to click Restore.
Silly of me, lol.