Hi
Can anyone check my computer hijackthis and tell me if there’s anything I should delete?
Logfile of Trend Micro HijackThis v2.0.2
Scan saved at 10:46:44 PM, on 7/10/2007
Platform: Windows XP SP2 (WinNT 5.01.2600)
MSIE: Internet Explorer v6.00 SP2 (6.00.2900.2180)
Boot mode: Normal
This shouldn’t be running, it is the file that is used to create the avast.setup for avast auto updates but I have no idea why it would be a running process.
Unless you have had a problem with auto update and then I would have thought that it would be setup.avast running. Other than that I don’t see anything obvious, log is very short though.
Why is it that you think something needs to be deleted ?
Thank you guys.
First, I think I reinstalled Avast because Its log showed a
long list of files which said unable to scan next to them.
By the way, why all those files are unable to scan?
My question if there is anything to delete is because this is the
computer that a-square destroyed and
my son took home and restored part of it. So this is a computer
which came back from a coma and I want to check if it is fine.
Thats why the hijackthis log is so short.
That isn’t a reason to reinstall as those files it couldn’t scan will still be there when you reinstall avast. You didn’t mention’why avast couldn’t scan the files’ this is given in the list.
Many programs (usually security based ones) password protect their files for legitimate reasons such as AdAware and Spybot Search & Destroy, there are others (and avast doesn’t know the password or have any way of using it even if it did know it).
When you run scans with the above programs and you delete harmful entries that they detect, a copy is kept (in quarantine/restore/backup) in case you need to reverse what you did. These are usually password protected, you should do some housekeeping and delete old backup/recovery/quarantine entries (older than two weeks or so), this will reduce the numbers of files that can’t be scanned.
By examining 1) the reason given by avast! for not being able to scan the files, 2) the location of the files, you can get an idea of what program they relate to. You may need to expand the column headings to see all the text.
Files that can’t be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.
This shouldn't be running, it is the file that is used to create the avast.setup for avast auto updates but I have no idea why it would be a running process.
Do you think that that’s why this file has become a running process?
Should I delete it?
It is the only possible reason I can think of, but I can’t understand how it could get to be displayed as a running process.
You should get out of the habit of saying should I delete it every time you come across anything out of the ordinary or one time you will delete something important. Deletion is never a good first option.
You should however end the process in Task Manager if it is still there, but leave the file there ii is essential.
After ending the process, try doing a manual update and see if that works, to confirm the update process is working and not stalling.
ashDisp.exe > Icon on system tray
ashMaiSv.exe > Mail
ashServ.exe > The resident protection
ashWebSv.exe > WebShield
aswUpdSv.exe > The automatic update service
The problem is that the HJT logs interpretation of a running process may differ from Task Manager. If it existed it would be in the Image Name (really pathetic naming by MS) column as setup.ovr, though I don’t believe you will find it, just checking the bases.
I didn’t find one better… I’m not convinced that I’ll ‘stop’ with it… but there are tons of ugly avatars on Internet… it’s not easy to find a pleasant one…