eEye Digital Security

Hi, This is my first post so don't get hard on me.

I got this error when trying to install Blink on a WinXP Home with Admin privs. I searched the KB articles and google to no avail. Any ideas?

 

Thank you for taking time to help but I already did before writing.

 Kind regards
 

fairfax, 

As Jeffrey pointed out, the KB article gives the common fixes that have resolved it in the past.  However, even though it is briefly mentioned in the summary at the top of the article, for our Blink Personal users often it is found to be another Anti-Virus or spyware solution that is running during the installation of Blink that is improperly quarantining or deleting our files.  Even though you had reviewed the KB article already, could you double-check that this is not the case for you?  Also simply disabling any existing AV or spyware engine from its interface has been found to be insufficient at times as it might not unload completely; please consider uninstalling any identified software.

Please keep us informed of your progress,

Christopher I.

Hello Christopher,

The first thing after reading Jeffrey's post I checked both links again and read them carefully to see if I somehow missed anything. But no, nothing amiss there. But, indeed, on that machine I have Zone Alarm Pro and AVG Free running. Do you suggest that I uninstall both? I can disable Zone Alarm but I don't seem to know how to disable the AVG, short of uninstalling it.

What I did when trying to install Blink Personal was:

1. Tried to install with both Zone Alarm and AVG running --> got the 1920 error.
2. Tried to install with Zone Alarm disabled and AVG running --> the same.
3. Tried to install with Zone alarm disabled and every process starting with avg*.* terminated manually --> the same again.

Kind regards,

Art

Art,

     I would recommend uninstalling both Zone Alarm and AVG.  If I remember correctly both of these programs are listed (in a list) in the beginning of Blink's installation process as being incompatible with Blink and therefor will cause conflicting issues.  Blink in itself is considered a all-in-one security suite solution.  I hope this helps.

Jeffrey,

Thank you very much. But where do you get a list of incompatible programs? I've never seen anything like this.

Anyway, I did as you suggested and uninstalled both Zone Alarm Pro and AVG and voila, it installed without a glitch ;)

But then I started Skype and off went the Blink rule windows. Each time I ticked "Create rule" but it went on and on and on so, finally, I had to turn the computer off. How do I go about writing a rule for Skype?

Best regards,

Art
 

fairfax:

Thank you very much. But where do you get a list of incompatible programs? I've never seen anything like this.

One of the first windows that show up when installing should include such a list.

But then I started Skype and off went the Blink rule windows. Each time I ticked "Create rule" but it went on and on and on so, finally, I had to turn the computer off. How do I go about writing a rule for Skype?

They have, and it's included in the 3.1 Beta.  When it goes to production, it'll be standard.  :)
(You can find a link to the beta in this forum)

I'm sure someone more official can give more detailed answers, but this should get you started.

fairfax, 

Just to explain a bit what was occurring with Blink 3.0 and Skype, if you were to review each rule request they would have differed in the protocol: TCP or UDP, port, and direction.  Each time Skype is initialized, it is making a request outbound to random high ports in the range from 1024 to 65535 for both TCP and UDP in addition to TCP/80 and TCP/443.

With Blink 3.0, the rule created when you clicked on "Create permanent rule" and "Allow" from the interactive alert was for the specific protocol and port being requested at that time; therefore, you potentially could end up with 129,000+ rules if you continued to acknowledge each Blink prompt.  With Blink 3.1, of which a beta is already available, firstly Skype was addressed with a default Application Firewall rule.  Also, in consideration of applications that behave like Skype (recycling random high ports), now when clicking on "Create permanent rule" and "Allow", the rule will be created with "All ports" set as the default; this, by the way, is how to write the rule with your current installation of Blink 3.0.  If the user would prefer to limit it to the specific port being requested at the time, you can still do so by clicking "Advanced" which will display the rule wizard.

I hope this helps.  Please, as Spunner suggested, install the version 3.1 candidate available at the URL below.  In addition to several bug fixes, it improves a bit on usability and significantly improves on compatibility with other software and environments.

Thank you for the feedback and for helping each other out.

Spunner:

One of the first windows that show up when installing should include such a list.

I've tried to install so many times that I don't remember ever seeing it. 

They have, and it's included in the 3.1 Beta.  When it goes to production, it'll be standard.  :)
(You can find a link to the beta in this forum)

Thank you, I will download it.

Art
 

Spunner,

The list of applications that have been mentioned are only in the 3.1 build which you are downloading now; it is on one of the initial pages of the installation wizard.  You are correct that version 3.0 you have been using up until now did not include it.

Thank you.  We look forward to your feedback about the 3.1 candidate release.

cimes:

Just to explain a bit what was occurring with Blink 3.0 and Skype, if you were to review each rule request they would have differed in the protocol: TCP or UDP, port, and direction.  Each time Skype is initialized, it is making a request outbound to random high ports in the range from 1024 to 65535 for both TCP and UDP in addition to TCP/80 and TCP/443.

Yeah, I figured that out :D Had to manually turn the PC off to get rid of the Blink rule windows.

With Blink 3.0, the rule created when you clicked on "Create permanent rule" and "Allow" from the interactive alert was for the specific protocol and port being requested at that time; therefore, you potentially could end up with 129,000+ rules if you continued to acknowledge each Blink prompt.  With Blink 3.1, of which a beta is already available, firstly Skype was addressed with a default Application Firewall rule.  Also, in consideration of applications that behave like Skype (recycling random high ports), now when clicking on "Create permanent rule" and "Allow", the rule will be created with "All ports" set as the default; this, by the way, is how to write the rule with your current installation of Blink 3.0.  If the user would prefer to limit it to the specific port being requested at the time, you can still do so by clicking "Advanced" which will display the rule wizard.

That's exactly what I did. I allowed both the TCP and UDP both ways traffic and Skype works well now.
 

I hope this helps.  Please, as Spunner suggested, install the version 3.1 candidate available at the URL below.  In addition to several bug fixes, it improves a bit on usability and significantly improves on compatibility with other software and environments.

Thank you for the feedback and for helping each other out.

Just one thing. Should I uninstall Blink and then install the new version or I just install on top of the old version? 

Best regards and thanks,

Art
 

To be honest, there really isn't a difference between manually uninstalling then installing or running the new installer on top of the old version.  When performing the latter, it is simply detecting the older version and prompting the user if they'd like to uninstall it.  Saying yes, simply initiates the uninstall automatically for you.

Either way, you will be asked whether or not you'd like to keep your current configuration (settings and rules) and if you'd like to leave the license intact.  If you've made many custom configurations or created rules that you'd prefer to not have to reenter then when prompted, you'd probably want to keep your current configuration.  Otherwise, might be best to start fresh.  As for the license, you should leave it as is; otherwise you will need to reenter it later.
 

 Thank you. I will try to install the beta this afternoon.

Art 

It installed fine on one computer. Later I will try to install it on my other, more problematic machine.

Art