in

eEye Digital Security

The endpoint to vulnerability starts here.

 

3.5.4 Not detected by Windows Security Centre and an update problem

Last post 01-11-2008 11:32 PM by PaulField. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 01-06-2008 2:59 AM

    3.5.4 Not detected by Windows Security Centre and an update problem

    Hi All

    I've been successfully using Blink for sometime, but have just had to reinstall following a hard drive failure. Once it had completed updating to 3.5.4 I have two problems

    1) Windows Security Centre is not detecting Blink as present on the system- Its still running the Windows Firewall (which I can turn off manually) and declaring that no AV is present. I know blink firewall is running as I'm getting messages and alerts, while the AV declares itself as running in the logs

    2) Following autoupdate the installation declares itself as 3.5.4, but checking with a manual update still decides it needs blink 3.5.4 and install the following
                 eEye Auto-Update 2.4.17
                 Application Bus 2.3.4
                 Blink AntiVirus Engine 1.0.289
                 Blink 3.5.4

                 which it does but decides it still needs them after both Blink and system restarts

    I've reinstalled  even with resetting the config but the behaviour is consistent

    I'm happy I'm protected but would prefer it if the install was properly detected by Windows

    Any ideas welcomed

    System is XP home SP2, Blink Personal

    Filed under: ,
  • 01-06-2008 4:25 AM In reply to

    Re: 3.5.4 Not detected by Windows Security Centre and an update problem

    I have noticed the same thing on my system.  I know if you turn off the Windows Firewall it will detect whether or not Blink's firewall (Application or System firewall) is off.  eEye would have to explain the AV portion of it though.
  • 01-06-2008 8:08 PM In reply to

    Re: 3.5.4 Not detected by Windows Security Centre and an update problem

    I have experienced similiar problems...but Win xp sometimes is ignorant and has to be repeatedly told, like a child misbehaving, and it will eventually recognize 'Blink'...been a mystery to me as well...my questions concern numerous so-called unused registry entries 'fix-it' utilities finds

  • 01-07-2008 7:56 AM In reply to

    Re: 3.5.4 Not detected by Windows Security Centre and an update problem

     

    1) I’ve installed an older version of Blink Personal and I updated to the latest version 3.5.4. It seems that if the Windows Firewall in Security Center is turned off and Blink Firewall enabled, XP will not tell the user that the OS is unprotected because it will use the Blink Firewall. I couldn’t reproduce the issue. We will further look into this.

    2) It’s a normal behavior what happens if you try to update Blink again. Blink will check for updates for all selected products; 3.5.4 will be selected and if you press next to update once again you will see the list with the current versions for each product:

    eEye Auto-Update 2.4.17
                 Application Bus 2.3.4
                 Blink AntiVirus Engine 1.0.289
                 Blink 3.5.4 

    Cristi Ungureanu - QA Team
  • 01-11-2008 11:32 PM In reply to

    Re: 3.5.4 Not detected by Windows Security Centre and an update problem

    cungureanu:
    1) I’ve installed an older version of Blink Personal and I updated to the latest version 3.5.4. It seems that if the Windows Firewall in Security Center is turned off and Blink Firewall enabled, XP will not tell the user that the OS is unprotected because it will use the Blink Firewall. I couldn’t reproduce the issue. We will further look into this.

    I should expand a bit on my original message. It was the allegedly missing AV that prompted me to look into Security Centre. While there I checked the firewall and Window had re-run its own firewall so gave no warning - I was getting messages from Blink firewall so it was running. Manually turning off the Windows firewall then gave the warning that no firewall was runnning. I'm currently having to run with both AV and firewall as manually monitoring

    Paul

Page 1 of 1 (5 items)
© 1995 - 2009 eEye Incorporated