I did a boot-time scan with Avast and it detected several corrupted files located in the local settings.I am not sure what I should do with these corrupted files and is there any way to repair them. :-\
If you can give some examples of the file names that avast thinks are corrupt ?
It may just be that for some reason avast is unable to unpack them to scan and nothing to worry about unduly.
These are some of the files Avast thinks they are corrupted:msg 46, msnmsgs, msi, msgrcore.cab, skcti.This is the first time Avast is saying they are corrupted during scanning.
Well the only one that looks like a file name is, msgrcore.cab and is the only one that could be an archive that avast has to open, which if it failed to open it might indicate it was corrupt, though avast should have no problem in opening a .cab file.
So I’m at a bit of a loss as to what the problem might be, remember that files that can’t be scanned are just that and not suspect or infected, which is why I said it isn’t much to be concerned with.
If the file/s were truly corrupt then you would possibly get error messages when running the program associated with it. Corruption can happen at any time, so it is entirely possible that avast wouldn’t have mentioned it before.
I haven’t recived any error messages.I have also done disk checking to repair any errors.But Avast still reports they are corrupted.
Sorry I can’t say why that might be only that it really isn’t something to be overly concerned about.
You are also probably doing a Thorough Scan or a scan with archives enabled, Personally I never scan archives (with the exception of my first on-demand scan when I wanted to confirm my system was clean) as they are inert and would need to be extracted and run to present any danger and avast should scan files either as they are extracted or before they are run.
I do a weekly on-demand scan, Standard, without archives.