I found this item (below) in my boot scan this morning. My operating system is Windows 7. How would I find this on my system? Can and should I delete it?
File Volume{14df3986-bb20-11e0-8416-806e6f6e6963}\D2D\IMAGES\POP010EJ0OX01C7115.SWM|>DemoVideo Error 42127 {CAB archive is corrupted.}
The short answer is there is nothing you need do.
Longer answer - Corrupted Archive file, this could simply mean that avast is unable to unpack it to scan the contents of the archive and assuming it is because it is corrupt. Even if it were corrupt there is nothing that a user can do to resolve any corruption, short of replacing the file. This I wouldn’t recommend (especially if this is for archives in the \System Volume Information folder, part of the system restore function) unless you are getting problems relating to that file outside of the avast scan.
What I didn’t mention is that I found the exact same listing (only the key between the brackets is different) on two separate systems - both the same brand, running Windows 7 and sharing the same internet connection.
This listing has never appeared in previous boot scans.
I am fine to leave this as is. I just want to confirm this is not a potential threat. It seems it is not. Thanks for the quick answer.
This listing has never appeared in previous boot scans.why do you run boot scan ?
Yes same drill, it is a notification of a file that can’t scanned and gives the reason why, many AVs keep you in the dark and don’t report files that can’t be scanned.
So it is a file that can’t be scanned, it isn’t an indication that the file is infected or suspect, just that it can’t be scanned and why. The why is important and in this case possible corruption is not a problem.
I ran boot scan on the one system because it was running slow. The browser was corrupted, so I ran virus scan, boot scan, then reinstalled the updated the browser. There were several corrupt files, which I removed - only this one was left. I didn’t remove it because I wasn’t sure where to find it or how to remove it.
The second system I ran the boot scan on simply because it was easy to do both systems simultaneously. The second system was clean with the exception of this one file.
I thought it strange that the same file would be on both systems.
I run boot scan every month or so as a regular part of my system maintenance procedures. Between home and work, I have several systems that I maintain.