That file looks like it’s related to Visual C++ probably 2008 installation.
You can always try crap cleaner aka CCleaner. It’s pretty good at removing stuff like this.
You wouldn’t need anything more than a simple delete of the vcredist_x86.exe.part file, if he decision is to delete it. If it was corrupt then it wouldn’t have installed anything, so probably no remnants to remove. Plus if there are no reported problems I go with the old adage if it isn’t broken don’t fix it.
Even if it weren’t corrupt you wouldn’t want to go trying to remove any installation as there is no indication that it is infected, just that that file can’t be scanned.
I tracked them down and found them all in the re cycler folder in my C:drive. I opened the folder and everything in it was several failed and partial downloads. I deleted everything in the folder and ran a boot scan and no more corrupt files. Once I was informed that the part in the file name meant it was a partial download it was fairly easy to find following the location Avast gave me during the boot scan. thank you all again for all the effort and help. I truly appreciate it.
You’re welcome.
I would question why Avast is scanning for corrupted files in the Recycle Bin. I am in the camp of minimizing confusion for the average PC user.
As I said “it isn’t scanning for corrupt files” all that it is doing is telling you which files couldn’t be scanned and why they couldn’t be scanned. If that happens to be because the archive is corrupt, that is the reason given, period, it isn’t scanning/looking for corrupt files.
That is what I understand now that Avast does not scan for corrupt files it was just telling me it encountered corrupt files that it couldnot scan and at what location it encountered them.
Correct.