Purchased NOD32: Installation Errors

WinXP 32 bit computer.

I downloaded and installed NOD32 trial. It worked.

Then I purchased NOD32 and downloaded the software from the link provided
in the email.

I unistalled the trial version but the uninstall failed with this error message.

I then tried to install NOD32 using the downloaded file and recieved the
same error message.

Then I deleted the ESET directory in "program files".

I then tried to install NOD32 using the downloaded file and recieved the
same error message.

Question.

1. Why can't I uninstall the NOD32 trial software?
2. Why can't I install the purchased NOD32 software ?

 

Trying to install again, new error message.

 

Insteresting.

Thereinlies one bad assumption by ESET. My Windows default is not
drive letter "C". I have a simple raid setup and the default is drive
letter "F". There is no "C" drive on my system, therefore it's not the default.

Oh, the comedy of Eset.

How does one proceed to fix this ? LOL

 

Update.

I installed a spare hard drive and it's called drive "C".

Made a directory tree c:\windows\installer
an copied the eav_nt32_enu.msi to the installer folder.

I also copied the "eav_nt32_enu.msi" file to the F:\Windows\Installer folder.

When I run ESET uninstaller, I do not get the original error message,
but the new error message is.

If I try to install the product, I get the same error message.

I can't uninstall nor install NOD32 right now.

What next to try ?

 

I did a google search on error code 2753 and got some hits going back a few years. Seems like the solution was to kill any eset processes, delete the eset
directories, and edit the registry and delete any eset entries.

ok did that.

Ta'da!

I was able to install NOD32.

It seems to be working now, sweet.

So... what is the root cause of all this mess ? the only thing different
from my computer is that it has a two drive raid setup, but this setup
didn't create a drive letter "C" as the default. I wonder is this is confusing
the Eset software ?

Considering this error code goes back a few years, it might be time that
Eset looks into this as it still exists.