Sounds like a damaged entry in the Windows Installer database. I
would try using "MSICUU" to delete the database records for NOD32, and
then attempt reinstallation.
Run MSICUU.exe (MSI Cleanup Utility) directly from the following share:
MSICUU is a old graphical front-end to the still-maintained "MSIZAP"
tool. MSIZAP is a bit of a pain to use, so I still recommend using
"MSICUU", but providing it with an updated MSIZAP in the same directory
(which you will find in the above mentioned file share).
J. Greg Mackinnon | ETS Systems Architecture and Administration | x68251
On 9/7/2010 12:52 PM, Larry Kost wrote:
> Still no luck. Whether I start in Safe Mode or not, ESET shows up in
> the Start/ALl Programs and if I click uniinstall it says that this is
> intended only for currently installed applications. If I go to
> Control Panel/Uninstall, it doesn't even show up.
> Any other advice would be appreciated. I would just let it be, but
> something seems amiss.
> On 9/7/2010 10:07 AM, Carol Caldwell-Edmonds wrote:
>> we have the best results using the uninstaller for Eset in safe mode.
>> Then reboot to regular mode and install the new version. Then update it.
>> Carol Caldwell-Edmonds,
>> Enterprise Technology Services: Client Services
>> Manager, UVM Computing Helpline and the Computer Depot Clinic
>> University of Vermont
>> [log in to unmask]
>> avatar by Shannon Edmonds
>> never take yourself TOO seriously...
>> artwork by Shannon Edmonds
>> On 9/7/2010 10:02 AM, Larry Kost wrote:
>>> I tried installing the latest NODE32 64 bit on my 64 bit Windows 7
>>> machine. It starts off and then pops up a window saying "The Installer
>>> has Insufficient privileges to modify this file ..." where the file is
>>> in program files ESET ...If I click Ignore, another and another pop
>>> up. If I pick stop, it says that the installer will continue if I
>>> reboot, but nothing happens on reboot.
>>> I tried to uninstall the older version using it's own uninstall, but
>>> it now thinks it has been uninstalled. Thought might be some Ownership
>>> problem, but when I try to take ownership of the ESET folder, I get an
>>> I finally gave up and did a system restore. Any suggestions??