Installing NOD32 A/V when machine is infected ?

Hi - I have a licence for "ESET NOD32 Antivirus Business Edition for Microsoft Windows Win XP/2000/2003/Vista/Win 7" and I'd like to go ahead and install it but I have a problem !

It's a Vista Ultimate machine on which I have run MalwareBytes (quick scan) and S+D as Administrator in Safe Mode and come up clean (actually it didn't come up clean initially but I cleaned, rebooted and then rescanned).

The problem is that when I now logon as a normal user every .exe I try to run generates the dialog "Please choose which program you wish to use to open this file".

I've seen various fixes for this problem but none fill me with confidence.

Would it be OK / possible to install the NOD32 Antivirus as Administrator and then allow the to fix the problem with the "Please choose which program ..." problem ?

Thanks

 

Well things are a little better ! But I'm interested to know whether it's now OK to install NOD32.

I ran MalwareBytes as the user who was originally infected and that found a Broken.OpenCommand . Once that was removed then the user interface began to work normally again (ie no prompting for 'Which Program would you like to open this file with' when attempting to execute a file).

However I now want to go ahead and install NOD32 but I'm not sure if the machine is sufficiently clean ? What (if anything) should I do before installation to establish this ?

Thanks.

 

Hi,

Unfortunately NOD32 will not repair file association. Run the following:

For XP
http://www.dougknox.com/xp/fileassoc/xp_exe_fix.zip

For Vista/7
http://tinyurl.com/y3m77w7

Let me know how this goes,

Regards,
Jesus

 

Open a ticket with ESET support and PM me your case number. Support can assist in making sure it is ok to install NOD32 on your workstation.

http://www.eset.com/support/contact#

Regards,
Jesus

 

Hi Jesus - Thanks for your help. I've opened the ticket. Unfortunately when I try to PM you there's a message saying that 'Personal Messaging is currently unavailable'. I take it you would rather that I didn't quote the ticket number in this forum ?

In the meantime as the file association problem seems to have been resolved by finding and removing Broken.OpenCommand I'm not sure if I should you follow your suggestion at https://www.wilderssecurity.com/showpost.php?p=1831996&postcount=3 ? Would be interested to hear what you think.

In the meantime I will try the PM thing again shortly.

Regards

Richard.

 

I just PMed you,

Reply to me with your ticket number.

My suggestion adds an entry in the registry that replaces the current values and sets them to its default settings.

Regards,
Jesus