Nod tmp files

Discussion in 'ESET NOD32 Antivirus' started by davstar, Jun 6, 2008.

Thread Status:
Not open for further replies.
  1. davstar

    davstar Registered Member

    Joined:
    Nov 7, 2007
    Posts:
    21
    Hi,
    Sorry if this has been dealt with before but I couldn't find anything in a forum search. Is it safe to delete the nodxxxx.tmp files which I found in the windows\temp dir? I found nearly 9000 of them! I've also got a lot of httxxxx.tmp files, could they also come from nod32? I am using the default settings for my 3.0.657.0 installation.
    Thanks in anticipation and regards,
    Dave
     
  2. Capp

    Capp Registered Member

    Joined:
    Oct 16, 2004
    Posts:
    2,125
    Location:
    United States
    You can delete everything in your temp folder.

    :)
     
  3. davstar

    davstar Registered Member

    Joined:
    Nov 7, 2007
    Posts:
    21
    Hi Capp,
    Thanks for your reply. That's what I thought but with Windows it's good to get a second opinion ;)
    It would be helpful if nod could clean up these files automatically.
    Regards,
    Dave
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    The temp files are deleted after they have been extracted from an archive and scanned. Could you please observe under what circumstances the files are created but not deleted?
     
  5. davstar

    davstar Registered Member

    Joined:
    Nov 7, 2007
    Posts:
    21
    Hi Marcos,
    I'll try to keep a record. So far I have noticed that this occurs during (most) scans this year. I have always had the latest nod32 english versions installed.
    Perhaps another program is preventing deletion? Does nod32 also produce the httxxx.files?
    Thanks and regards,
    Dave
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    I'm not aware of that. ESS/EAV should only create nod*.tmp files.
     
  7. davstar

    davstar Registered Member

    Joined:
    Nov 7, 2007
    Posts:
    21
    Hi Marcos,
    Ok thanks for that.
    Regards,
    Dave
     
  8. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    You could always run a utility like Filemon to see what is causing disk IO and where and then track down exactly what process is doing this and under what conditions from there.
     
  9. davstar

    davstar Registered Member

    Joined:
    Nov 7, 2007
    Posts:
    21
    That's an idea. Thanks for you suggestion.
    Regards,
    Dave
     
Thread Status:
Not open for further replies.