Who does nod32 operate in this situation (file locked only cleaned after reboot)??

HI There!

I get this problem now and then not often. And wonder how effective nod32 is in this type of situation. For example when I try to download the core temp application from alcpu.com/coretemp Nod32 kicks in. It says "a variant of Win32/InstallIQ potentially unwanted application, encountered by FireFox". So as a good boy I let Nod quarantine and disconnect. But then Nod says 'files to be cleaned were locked by another program, to clean reboot, reboot now?" So then I reboot.

So what happened here.

Firefox locked the file while it was downloading, so Nod 32 couldn't quarantine and delete it. Only after reboot can Nod delete the file. But between 'not able to clean the file' and 'reboot' This file could've done damage right?

I don't get how effective Nod32 is in such a situation, someone care to explain?

 

What version of OS and ESET NOD32 Antivirus do you use? Do you use any additional Firefox plug-ins that might affect the download, such as download managers?

 

HI There!

I use Windows & 64 and firefox 8.0

Was my system compromised?