eEye Digital Security

blinkconsumersetupbeta4(x64)  will not install on Vista Home Premium 64

Setup display an internal error 2738 (Fatal Error)

Nod 32 is still active, I was planing to uninstal after sucessfull reboot with Blink... 

This is likely due to Nod32 removing files from Blink's folder. Please uninstall Nod32 and try again.

Blink does not play well with others, (no AV product does).

You need to remove ALL AV products, because otherwise they will be fighting for precedence, and you'll get errors like what you're seeing.  Blink tries to insert itself deep in the guts of the system, NOD says, 'wait a minute, I'm there, you must be a virus, I'll deny you' and Blink goes home crying.

Ok thanks all for the course, but the reason why I mentioned that nod was still active is because I know it can be an issue however IT SHOULD NOT BE.

When I installed nod I had to simply disable my other AV solution (VET)   not totally uninstall it, after the sucessfull install then I uninstalled VET my pc was never totally naked (I know I AM PARANOID...)

Ok back to the bug, I have totally uninstaled Nod Rebooted and the error is still there, can comeone from tech support give me the error detail, what is it.... 

Bug is still there, please note that I run vista as a regular user, so prompt pop up asking password and once provided it unpack then seem to crash running, this seem to be more an INSTALL bug than anything else...

I will try running from full admin account and I would not be surprised if it will work... 

Can you please post a screenshot of the error you are receiving?

Also you can run the installer with this command to generate an install log file which can help us in troubleshooting.

installer.exe /Lv*! c:\Blinkinstall.log

After installation fails, send us the c:\Blinkinstall.log file at blink.eap@eeye.com

Thanks!

There seems to be a problem with your VBS environment. Here is a post with some information regarding this error. Can you please try to follow the instructions and let us know if they fix the issue?

http://blogs.msdn.com/heaths/archive/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions.aspx

I did not had the key, so I did a register using

c:\windows\syswow64\regsvr32 vbscript.dll

and

c:\windows\syswow64\regsvr32 jscript.dll

Install and update completed, I forgot to mention my Vista is SP1, maybe this is the reason why VB component where unregistered, anyway all set now

Thanks for both the support and a great product!