eEye Digital Security

So Blink won't install on the Windows 7 Beta.  Says the program is only for XP/Vista and simply quits the installer.  Is there a way to work around this, so that I can give it a shot?  Windows 7 and Vista are so similar on the backend that I was kind of hoping it would just work out of the box.  If you all haven't tested it on your end, and there's a way for me to force Blink to install anyway, i'd be happy to give you my results :)

You are welcome to do the test. We did it and it works but no extensive testing took place yet.

To force the installation, use this command line argument when executing Blink installer:

Wonderful!  Thank you, and I'll be sure to report any issues I experience.

Installation was successful, and all services appear to start correctly, however when trying to launch the Blink app (container), I am told that Blink needs to be started with Administrator privileges to update configuration.  Doing so results in no visible action.  No app launch, no setting changes, no nothing.  I receive the Windows UAC prompt and then nothing.  According to the task manager, Blink.exe starts, loads about 3mb into RAM, and then quits.

Bump?  Any help would be hot.

Same here.  I run Blink successfully on XP Pro in VirtualBox on Mac OS X, and would like to share my experiences with Blink on Vista 7 within a VM.

Good News.  Installed using the above command line argument and worked very well, with the following notes.

1. Installed on fresh install of Windows 7 Beta build 7000 with all patches up to today, except Silverlight.  Plus latest version of CCleaner.
2. Within Sun Virtualbox 2.1.0 on my iMac Core Duo, with 1 GB of RAM, 24 MB of VRAM and 20 GB of HD allocated to VM.
3. Installed Blink 4.2.1 which auto-updated to 4.2.3 as part of the 4 components updated.  Used free trial with no serial number.
4. Trained the Blink firewall for the usual services from Microsoft, as well as the CCleaner updater.
5. W7 Action Centre complained I had 2 firewalls running, and 2 AV clients.
6. At first, the Action Centre allowed me to see all the firewalls running.  Actually 3!  Windows Firewall On, Blink On, and Blink Off.  Perhaps the 2 Blink firewalls were from the update, and suspected one would disappear after restart (not required by Blink update, but my usual practice).  There were buttons supposedly allowing me to turn the firewalls on and off from the Action Centre, but they were greyed out.  Since restarting, I am unable to get into this detailed view of firewalls from the Action Centre so cannot check.
7. Windows contradicts itself as usual.  From the Firewall control panel, turning off the Windows firewall draws the warning that this is risky.  But the Action Centre says running 2 firewalls will cause conflicts.
8. On Antivirus, perhaps disabling the launch check disabled the usual warning I remember on Blink Install that Windows Defender should be disabled.  Both were running in parallel.
9. Microsoft has made Defender even harder to find and disable in W7.  You can only find it in the Classic/Detailed view of all control panels, then have to go across several tabs in the panel to turn it all off.  You cannot find it in Programs or Windows Features.  But once off, it does correctly reflect in Action Centre that the computer is still protected from Virus and Spy by Blink.
10. W7 default taskbar will not show the Blink icon unless there are alerts.  I changed it to always show that familiar green eye.
11. Vulnerability scan showed no high-risk vulnerabilities, 6 Medium, 5 Low, 5 Information.  Looked reasonable.  Blink could not detect the OS in the Machine Information, but did correctly identify all the hardware my VM offered, and the W7 services, in the Scan Details.
12. Virus Scan found 1 Trojan.Win32.StartPage.fw at c:\Windows\system32\mfplay.dll.  I do not get this trojan on the same version of CCleaner on IE7 on XP Pro in a separate VM, so I don't believe it came from CCleaner.  I also went to no other websites than Eeye and CCleaner/FileHippo for their respective downloads.

Still no luck getting the Blink container running on Windows 7 Beta x64

 I would assume as we get closer this will be solved..

But I was hoping to try this sooner than later to get ready in case we move to 7

neatchee:

Still no luck getting the Blink container running on Windows 7 Beta x64

OK, my report was on the 32-bit Windows 7 Beta, as I have the Core Duo, not Core2Duo in my computer.

VirtualBox has now updated to 2.1.2 with formal support for Windows 7 Beta.  I did not rebuild my VM from scratch to see if the issues I saw earlier changed.  I simply updated my VM software to 2.1.2 and Blink continues to run successfully on W7 Beta.

http://www.virtualbox.org/wiki/Changelog

Ziad:

Good News.  Installed using the above command line argument and worked very well, with the following notes.

 

1. Installed on fresh install of Windows 7 Beta build 7000 with all patches up to today, except Silverlight.  Plus latest version of CCleaner.
2. Within Sun Virtualbox 2.1.0 on my iMac Core Duo, with 1 GB of RAM, 24 MB of VRAM and 20 GB of HD allocated to VM.

My Blink 4.2.3 no longer completes initializing on Windows 7 Beta, preventing me from updating to 4.2.4 as well as accessing the Home screen.

Same problem before, and after today's Windows 7 Patch from Microsoft.  

I run the separate Auto-Update Tool from the Programs menu, and it complains that the new Blink AV Engine update is not permitted.  However, the recommended path, to run Blink update interactively from within Blink is not possible, since Blink never completes initializing.

I've taken screen shots and am willing to collect debug logs - any particular logs and email address to send them?

Salutations.  Is there any sort of update on this issue?  I've been running ESET Nod32 v4 BETA since encountering this problem with Blink, but the beta period ends soon and I'll be out of a security solution :D

To recount the issue: As I understand it, this is primarily a problem with the program container on Windows 7 x64 (at least the problems I've encountered).  Installation seems fine, and all services start properly.  I'm given the message that Blink needs to be run as an Administrator to update configuration, but trying to do so results in the BLINK.exe process terminating almost immediately.  Any thoughts from the devs on things I could try would be greatly appreciated.  Thanks!

 Thare hasn't been any progress on this issue yet. We plan on addressing the Windows 7 issues very soon though. Will keep everyone posted when we have a Windows 7 compatible version

Thanks for the update, L.  Looking forward to an update soon!  Meanwhile, if it hasn't crossed your radar yet, I switched to using Sunbelt Vipre in the meantime.  It's an interesting program, VERY lightweight with good detection and prevention test results.