![]() ![]() I'm just trying to sort out the reason why these error files suddenly appeared with the installation of 8.0.143 and ONLY in Full Scan. I think I made it clear my AVAST Free is doing it's job as far as the protection goes. Quote from: Cranky on March 12, 2013, 09:14:01 PM Paranoid, thanks for the input. I incorrectly dispatched this message as part of a reply yesterday.to God knows where. I've been happier than heck since joining the AVAST family. 143 and reinstall '142 to see if the file error quirk also exists? Just passing this along for what its worth. ![]() With the prior version installed March 1st I only ran a couple of Quick Scans. I'm guessing this quirk is connected to the newest AVAST upgrade. No threats, no errors, and my protection appears to be running 100%. And, 'This file can not be accessed by the system (1920)' I ran three Full Scans to triple check. All prefaced with 'Windows/$NTUninstall'.followed by a different number code for each. ![]() While threat free, the log produced the following: 'Some Files Could Not Be Scanned'. After I upgraded to AVAST Free 8.0.143 March 8 I ran a Full Scan. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |