Win 2000.
This path is correct (had mistakenly added a backslash before - sorry !!!):
C:\WINNT\system32\i
That is better, though it is also unusual for single character folder names (or is that the file name with no file type, which is also suspect), is there anything else in that folder ?
The file properties show it has been in place pretty much ever since I had the computer.
I had the file in the chest for nearly 2 months, but it still is identified as being infected.
I sent it to the Avast support two times, never received a reply.
File properties aren't entirely reliable as a) it depends on if this value is creation or the last modified date. Signatures are constantly added and updated so it isn't unusual to see a file that wasn't previously detected now detected. This is why it is important to send to the chest (rather than delete) and confirm the detection at VT and in this case it confirms a good detection.
You will not normally receive a reply unless they need more information, they will analyse the submitted sample and if it was an FP would correct the VPS so it would no longer be detected. Obviously if it is still considered infected then there would be no change to the VPS
Also sent the file to the Avira support (including the VT results), but they insist it is clean.
So really don't know who and what to believe and what to do 
They would obvious still say it is clean as they still don't detect it, but in the face of the VT results, I'm afraid I couldn't accept that assurance.
I still don't know the file name that was detected, you gave a folder location and a malware name but no file name, so there is no way to know what the file is associated with using google, etc. and give any advice/assurance ?
