I did an aVast! forum search for “Dc1142.exe” & nothing showed up, but am hoping someone can tell me if I should have any cause for concern. I did an online search for this file name (quoted) & only 3 items were found, none of which really explained what this file might be used for / associated with.
I’m using free aVast! 7.0.1466 (vdefs up-to-date) on a laptop running Windows XP Media Center Edition (all fully updated) - this Dc1142.exe file in C:\recycler folder has been showing up since Sept. 19th 2012 indicating “some files could not be scanned.” Over 110 elements of this archive are listed every aVast! scan I’m concerned because I know of nothing which would have caused this (Windows update, application upgrade, new install, etc.). Is anyone else experiencing this with the same specific file name or perhaps some other archive that can’t be scanned because it’s password protected? I did find an indication in online search that implied the C:\recycler folder is NOT related to the C:\recycle folder associated with Windows recycle bin.
files that can not be scanned are just that…no more no less…it does not mean they are infected
avast just give you a scan error report, telling you it could not scan it and the reason why
what is the full path to the file?
can you attach a screen shot of the scan result?
This file name and others with the same file name format (see below and image) is associated with malware, Trojan-Dropper.Win32.Small (and others), but only one very old hit on a Yahoo search.
In that hit there were other files in the recycler in the same format as Dc1142.exe e.g. Dc9999.exe where the 9999 is another numeric value in the Dc9999.exe file name. Do you have any others in that file format Dc9999.exe in the recycle bin ?
As Bob said clear the recycle bin and that will hopefully remove it/them.
I rarely use the recycle bin, but checked per Bob’s recommendation & found a file that had been sent there on or near the date avast started reporting the “some files could not be scanned” message. It was a flash player update file for a new version that wouldn’t update on my system. Since I didn’t put it there, I’ll assume Macromedia includes this procedure in the update file. I deleted it from recycle bin & no more “some files could not be scanned” message.
Thanks to all who responded to my call for help! Problem solved.
…will try to contact avast forum mod in a few days to report this thread complete so they can close it, if it hasn’t been already. Perhaps I’m responsible for closing it - I better do some reading here, to find out.