Hi,
I have been using the free Avast 4.8 which worked fine, scanned all files on my montly “Thorough Full Scan”, sanning C/D/E all files.
I upgraded to the new Free Avast 5, but now when I do the same scan it says “some files could not be scanned” on the “Scan Results” it says:
File Name Status
C:\wind…\BIT4.tmpI>_sfx_manifest error: Reached the end of file (38)
Just concerned something is amiss, if anybody can advise I would be obliged.
Thank you.
jrjr
No I would say you have nothing to worry about all that avast is doing is reporting it couldn’t scan the file (that error is a windows file system error), not that it is infected or suspect.
Hi David,
Thank you for replying.
Pleased it’s not an infected one.
Would it be possible to remove the offending file ???
I do like things to be neat and tidy.
lol
JRJR
Why would you want to get rid of it, I haven’t the slightest idea what this file is "C:\wind…\BIT4.tmpI>_sfx_manifest " the location to start with is concatenated C:\wind…\ the bit in bold indicates there is more to the path.
If you start removing files that can’t be scanned just to be neat and tidy, sooner or later you will remove an important file.
Hi,
Thank you both for replying.
I suppose I am just interested as to why it wont scan all files now when it did before, not desperate to remove it but if there is/was an error I would just like to correct it. :-[
The path is:
C\WINDOWS\SoftwareDistribution\Download\c2115p16bd3c291aedde6441eb8cc984\BIT4.tmp>_spx_manifest
Thank you both again for your time, wishing you both a great weekend.
JR
Yes, it is a ms update. Seems to be incomplete, as usually temp files are removed from SoftwareDistribution after a successful update… If your system runs well and all microsoft security updates are installed you can safely delete the folder: c2115p16bd3c291aedde6441eb8cc984 For security you can make a system restore point first, so you are able to restore if problems occur. (but there shouldn’t be any!)
Also a great weekend to you…!
asyn
Armed with the full information it shouldn’t be an issue to remove it, though you should always investigate fully before deletion. Delete in haste repent at your leisure ;D
The file may not have been there on the last scan you did or the settings you used in the scan didn’t encompass that file.
: