I would tend to rename the file first, rather than delete (especially if avast is not reporting it), you can always delete it if after some time there is no ill effect.

But that’s just it, this is exactly the file in the System32 folder that I mentioned earlier which Avast IS reporting as infected. It’s reporting c:/WINDOWS/System32/crashlog.tar.gz/crashlog.tar/crashlog.tar/Memory.dmp and c:\WINDOWS/System32/crashlog.tar.gz/crashlog.tar as the two infected system files - each and every time. Double file extensions like that always ring warning bells for me.

The crashlog.tar.gz and unp files are the ONLY ones which are coming up labelled as infected now. I just checked again on rebooting and again there are at present no unp files in my C:\Documents and Settings\Gillie2tat\Local Host\Temp_avast4_ folder at all, infected or otherwise.

I can’t tell you where it came from though I do have quite a lot of third party software on my system so it is possible that it came from a third party tool.

I will await your further advice :slight_smile: I hope I’m coming to the end of my journey too.

I did a search on Google for crashlog.tar.gz and crashlog.tar and it didn’t come up with anything which suggests to me it’s not a system file. If it were it would probably be listed at least on Microsoft.com.

If you still think I should rename the file should I move it to a folder in My Documents or should I leave it in my system folder and just change the file extension - and if so what should I change the file extension to?