Odd tray icon issue with 5.0.95.0

Every time I open up the tray icon display since installing Nod32 5.0.95.0 I see the Nod32 icon briefly turn yellow with an exclamation point in it. It lasts a half second or so and then disappears. If I close the display and open it again, it repeats.

Here's a movie of it ...

http://dl.dropbox.com/u/8726094/nod32.swf

Perhaps this is related to the long-standing phantom warning message issue?
--
bc

 

Hi,

Best bet Disable system updates, reboot required, advise if the system tray exclamation and odd bahavior remains.

 

Odd behavior remains.
--
bc

 

What about disabling the option for switching to Gamer mode automatically when an application running in full-screen mode is detected?

 

Ayup, that was it. Thanks. I presume this is a bug as there was no switch to fullscreen going on (and further, I do not want to run with that off as I do occasionally game and like the nice auto-switch to gamer mode).
--
bc

 

Neither Win7 Aero dynamically changing the background in certain intervals?

 

Well, yes, I do have Win7 configured to change my background, but only once a day (midnight GMT). Further, I just turned that off and selected a single static background and yet, the problem persists.
--
bc

 

Have you tried running the Aero Troubleshooter ? The is an MS FixIt solution available here

 

I ran it. No problems. Honestly, I don't understand what suggests this is an Aero problem. I've got no apparent video issues whatsoever. I'm running with a Nvidia GTX 580 and the most recent WHQL drivers for it (285.62), so unless you're suggesting that those drivers are somehow confusing NOD32 into thinking I am switching into fullscreen when I am not, I respectfully submit that this is more likely to be a bug in NOD32's test for fullscreen mode.
--
bc

 

The suggestion was asked to eliminate any possbile issue with Windows Aero. Otherwise, I am frankly at a loss as to how you should proceed next.

Wait for additional suggestions from ESET.

Regards,

 

Ok, well, jsut to clarify for ESET, I ran both the troubleshooter and (even after it found no problems) the fixit (which also found no problems).
--
bc