ESS 4.2.58 upgrade from 4.2.40 disaster

Been happily running with 4.2.40 for quite a while now on W7 64.

Downloaded the 4.2.58 installer and intended to do an upgrade on the installed version - process comes about halfway and then pukes with the attached message ..................

Now the problem:

1. This machine already ONLY runs with the actual ADMINISTRATOR account with full administrator rights and 4.2.40 was installed by Administrator

2. So how do I give it sufficient privileges?

3. After canceling out of this and restarting the system, I am no longer able to uninstall the current installed and running version - I am told that the ESS uninstaller in the programs list is only valid for installed components.


Any idea if something is corrupt here and how to go about solving this?

 

first step http://kb.eset.com/esetkb/index?page=content&id=SOLN2289

 

It sounds like the mechanism for premature self-defense initialization failed for some unknown reason. Running the uninstall tool in safe mode should help.

 

Thanks adima and Marcos - think I am making progress, but am a worried puppy now.

As I mentioned the 4.2.58 installation initially completed halfway before puking.

So I downloaded the safe-mode uninstaller and followed the steps:

The uninstaller found 2 items to remove and I allowed it to remove both - eventually it suggested restarting machine and I did.

Now the second strange thing:

On system restart, I was expecting to find no ESS version on the machine, yet I ended up with the ESS icon on the taskbar and it proclaimed to be 4.2.58 .................

Not knowing what this meant I thought I would now try to do a "repair" install of 4.2.58, and THAT gets to a point where the installer complains about not being able to read a certain file (see attachment) and the repair then halts.

I copied the downloaded installer (done twice because I thought maybe it was corrupt first time round) to different locations on different drives and I also tried running it from a Usb memory stick but I keep getting the same message (........ and I don't find any such file on any drive of mine either)

Any thoughts on that one as I am not sure if I actually trust the ESS thing currently proclaiming to be active and fine on my taskbar

 

is process ekrn.exe actually running?

 

Yep its running and I can even update the database and experience a supposed "normal" ESS interface ..................... however, I am worried because I don't know if its actually doing anything worthwhile/properly because the way it arrived on my machine is highly suspect.

I guess I could again go through the safe-mode uninstall process but I am hoping my miseries is useful for the developers to trace what has actually caused the disaster in the first place.

 

It also does not correct the problem where I have to disable real time file system in order to get onto some sites. If it is running I get a message about cookies not being enabled. I have had this with the past two versions, and a previous post did not bring anything that cured it. Pay pal, Ciao, My laps, and some survey sites I use are affected. Disable ESS and everything is fine!!

 

Try running the uninstall tool twice with a restart after the first run. Then post here the uninstall tool log.

 

I want to tread lightly here in case I end up with a system that I am completely unable to install ESS on ..................

So:
Are you saying that the suggestion will automatically address the installer complaining about that file it cannot read from too ?

 

I had same problems with installing version 4.2.58 like thread opener.

History:
- I had problems in 4.2.35.
- I had problems in 4.2.40
- I had problems in 4.2.58
- ....

From version to version I wonder a little bit more whether ESET's qualitiy assurance is really testing the new versions seriously before they release them.

I am again on ESS version 4.0.474 because that is the only stable version on Windows Vista SP 2 for me.

 

Once the uninstall tool has run successfully there's no chance the errors would persist. In such case, the repair option cannot be available as the uninstall tool removes all traces of ESET products from the registry and the disk.

Please run the ESET uninstall tool in safe mode again and post the uninstall log here. When performing a clean install, run the msi package with the "/lvx log_name" parameter so that an installation log is created. It contains valuable information necessary to troubleshoot installation issues.

 

Marcos

Thanks for the help so far - seem to be making progress - requested logs attached.

What I have now is a seemingly "working" 4.2.58 with the ability to update the database and no moans on the UI.

I do however see some moans in the logs - don't know if/how significant those are, but thanks for the help and looking.

Installer log is here : http://www.home.telkomsa.net/glad/Images/log_name.txt (forum should be able to accommodate the log the installer creates but it moans its too big)

 

The log reads "Product: ESET Smart Security -- Installation completed successfully." so no problems were encountered and the product is installed correctly

 

XP Media Ctr / All Security Apps Exited or Real-time Disabled:

My Ver upgrade from 4.2.40 to 4.2.58.3 FROZE, too, during installation (loading new files) with same "Only for Installed App" Un-install error via Start/Eset......... FYI

Safe Mode Uninstall process to follow.

Edit: Successful Safe Mode Uninstall, Re-Boot, Install Attempt again. Install FROZE on "Remove Backup Files; Hard Shutdown; back-on, ESET Boot-up Screen Appears; Virus Signature Update Error appears when I Opened ESS and All I had to do was Enter ID and P-Wd -- and it works. Makes No Sense to me!

Posting this because 4.2.58.3 might cause others issues and maybe a diary of what goes wrong will help correct other problems.

 

Yeah, I am with you, I love the product and know it is one of the best but between throwing dice on every upgrade (by the way, why select "Yes upgrade if there is a upgrade - when it doesn't upgrade it? and you still have to dowload the latest anyway), during this particular round, I am doing about 50% having to do the safe mode uninstaller to upgrade machines.

We are a managed services provider so having crashing installation packages (it essentially renders ESET useless when these errors occur - until it repaired in my cases), is a hassel and I am strongly considering other alternatives.

So... 2 issues with upgrade...

1. It does NOT upgrade automatically.
2. Half of the installations fail and require safe mode uninstall which in many cases cannot be executed remotely, thus requiring a service call and down time with no protection.

Spend some more money on ads......