PDA

View Full Version : nua05.temp


beethoven
March 5th, 2007, 02:16 AM
I was working on my pc when suddenly I got an alert from Process Guard that a file was being updated asking for permission. Somehow I thought it was NOD (unfortunately do not remember what the pop up said exactly at the time) but as i did not see any reason for the alert (never happened before with respect to NOD) and I was busy, I denied the request.
Later I checked Processguard and found the following details:
file: nua05.temp was blocked from starting and full details referred to
c:\windows\temp\nua05.temp and commandline: nsetup.exe/siletmode/noreboot/settings="c:\windows\temp\nxa04.temp"

I checked my windows temp folder but cannot find these files. However, the reference to temp makes me very nervous. :blink:
I did a scan but nothing popped up.

Does anyone know if this file could have originated from NOD and if it is legit? Of course any other info is also appreciated.

beethoven
March 5th, 2007, 07:49 AM
Having checked NOD's log file I noticed a failed update attempt at the time in question. I have now forced a manual update and changed to Version 2.70.32.
I am still baffled though about the strange temp files listed in Process Guard's logs and the fact that this update was quite different than the normal upgrades running completely in the background.

Bubba
March 5th, 2007, 09:23 AM
-{ Quote: "Does anyone know if this file could have originated from NOD and if it is legit?" }-Even tho I am not at my Nod32 installed PC....all I can offer at the moment until others come along is that a previous thread from a couple years back alludes to this type behavior.

Very Large Update 9-20-04 update (http://www.wilderssecurity.com/showthread.php?t=48580)

-{ Quote: " just downloaded a very large Nod32 update and during the download this wanted to install
Nu54.tmp nsetup/exe/silentmode/noreboot
What is it and should i allow it " }-

Carver
March 5th, 2007, 12:40 PM
I got a popup saying something about a component update for NOD32 so I allowed it, the result was NOD32 2.70.32 and it was a large download.