I do a boot scan and keep getting these results. Typically I fix the results myself and move on but this is a repository file so before damaging something I wanted to ask. Are these results as concerning as it seems?:
01/14/2021 22:36
Scan of all local drives
File C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_8f19d27853828a49\igdumdim32.dll Error 42102 {Exception in macro viruses code.}
File C:\Windows.old\WINDOWS\Temp_8AA3A98E-10AE-4A62-BCF5-8EF7EED62B86\WindowsUpdate.20201204.140907.166.1.etl Error 42102 {Exception in macro viruses code.}
Number of searched folders: 131209
Number of tested files: 956029
Number of infected files: 0
It seems this link is directing to an article about the error code not the specific files that showed up in the scan and explains how Avast had a break in the scanning process. yes I know this already with a simple google search. What I need to know is are the files showing up, in conjunction with the break, potentially corrupted which causes a break in the process so the infection or alteration become unreadable? Every reply says oh this isn’t a big deal and explains how its just a break in the process of scanning but that seem counter intuitive and basically moronic. If I was testing a locks capabilities by putting a very small camera in it and going through the process of viewing the functionality of the lock and its effectiveness because of this process being done and the camera cut out twice during the viewing and we couldn’t say for sure that what was missed is secure and not a security flaw, then we wouldn’t say oh just don’t worry about it. Maybe that’s a bad analogy but you get what I am says. So please explain in detail how not effectively scanning these areas or processes or whatever is “not something to worry about”.
some years ago it was said that scan error messages would be removed from scan results in a later version because this is info that homeusers can do nothing about and do not need to know
