Unable to install SS4, "ended prematurely"

I am having a really tough time installing Smart Security 4 on an XP SP3 machine. No other firewall programs installed. Am logged in as an administrator. Each time it gets to the driver install part and then does a rollback with the "installation ended prematurely" error.

Have searched the web and these forums and have tried some of the suggestions (disable network connections, fix winsock). Have opened a support issue with ESET but response is slow and the first response is to verify my identity - I'm an IT consultant who recommended this to a client and now I'm stuck trying to resolve this problem for free (pretty nice! ). I should hear back in another day or so.

Any ideas would be very welcome!

Thanks,
John

 

FYI - just tried creating a new user account (also an admin) and installing under that account. No Dice

 

Yes. Have attached setup.log (in 2 parts due to 1mb size limit!?) and setupapi.log. Have also sent to ESET support

Have also tried removing XP SP3, running WinsockXPFix (again), clearing Temp dirs and checking permissions. Also found evidence of old McAfee install, so downloaded and ran Removal Tool. After that, went into drivers and removed a McAfee driver found when view hidden devices was turned on.
Ran "sfc /scannow" as well.

Still no dice. What gives? This is incredibly frustrating. Any advice greatly appreciated!

John

 

From install.log I can see that you have problem with installation of Epfwndis driver which is part of ESET firewall. Function HrGetINetCfg returns error. This function calls MS COM object and it returns error code 0x8007007e, what should mean FileNotFoundException.

WinsockFix can not help you, since NDIS driver is not registered there.

Try also this:
http://www.dcclifecare.com/list/0x8007007E.html
and this:
http://www.updatexp.com/0x8007007E.html

If still no success, download and start ProcessMonitor before installation process (with Filter->Enable Advanced Output) and post PM log somewhere to web.

 

Thanks for your response. The only reason I was running WinsockXPFix was because I had seen it posted in other responses to similar issues.

In the end I ended up formatting the hard drive and reinstalling Windows, so I guess I'll never really know what the fix was.

This definitely makes me hesitant about continuiong to recommend NOD32 to clients, as I just wasted about 7 unpaid hours trying to resolve this without formatting. It may have been a Windows issue, ultimately, but quicker response from NOD32 techs and more specific error messages would really have helped in this case.

Thanks again for your suggestions.

 

I too have this problem with the 4.0 client on select machines. I'm also unsure as to why this conflict has occured but I had this problem with NOD32 v3.0 on different machines back then, along with a slew of other annoyances that make me wonder what the heck is going on over at Eset and how they became a sloppy mess.

Looking at the fact that you were willing to do a fresh installation in order for the newest version to work is the difference between us. I instead halted my upgrade and decided to stick with v2.7. Back when 3.0 came out I also had many problems which is why I skipped over installing the whole 3.0 series entirely, looks like I'll be doing the same until Eset gets their stuff together.

I'm glad you focused on "unpaid hours" in your rant and have also lost hours and confidence in Eset as a whole and don't suggest Eset to clients of mine, escpecially those who run larger networks with 100's of clients. Also, search the forum for "installation ended prematurely" and/or Google "NOD32 4.0 Setup Wizard ended prematurely", you'll find many users who have similar problems with both the 3.x and 4.x versions, my belief is that their installer .msi file is the culprit with too many checks occuring while the installer rolls back if everything doesn't go perfect. I've built installations using Installshield and WinInstall LE and when you use too many verification checks and other options of the sort, the chances of your rollout failing increase. I notice that the 3.x and 4.x client don't ask for reboot after installation so I wonder if the starting of services and drivers live and not on reboot like v2.7 which always prompts for reboot after the install is some of the problem. Eset................time to do some homework and fix this ridiculous issue already!!!

 

I encounter this issue too on several machines. As a reseller I have been reluctant since version 3 to advice this to my business customers. For home users... ok. Businesses... nah. No way. Not anymore.

Get it on the road again ESET, or at least give more info, certainly to the persons selling your products. A filesize limit on the supportform is absolutely ridiculous. Make it easier and faster.

Please.

 

Can a push install of some sort work out? I've backed up the system using ATI2009 so right now am able to try some stuff. Otherwise best next weekend, since this (helas) is a business machine which needs to be back on its feet at 8 AM. Better get to sleep. Thanks ESET ;-P

(just messing... but come on... many people complaining, this must be better documented, even on semi-internal pages there is next to nothing available for us)