Author Topic: tray icon not moving after latest update this afternoon  (Read 472 times)

0 Members and 1 Guest are viewing this topic.

Offline Heather68

  • Newbie
  • *
  • Posts: 2
tray icon not moving after latest update this afternoon
« on: January 13, 2018, 12:54:04 AM »
Hi--
for some reason a shield was shut off and my avast icon disappeared from the tray. So I installed the latest Avast program from scratch this afternoon. I read that the latest update should allow the tray icon to move while avast is working but so far it is not doing so. Any ideas why this is happening?
Thanks!

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 80653
  • No support PMs thanks
Re: tray icon not moving after latest update this afternoon
« Reply #1 on: January 13, 2018, 01:27:10 AM »
A known bug that has been reported and has featured in a number of forum topics.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 18.8.2356/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ WinPatrol+/

Offline Heather68

  • Newbie
  • *
  • Posts: 2
Re: tray icon not moving after latest update this afternoon
« Reply #2 on: January 13, 2018, 03:12:44 AM »
Thanks. I saw that, but one of the replies was that it was going to be rectified today.

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 80653
  • No support PMs thanks
Re: tray icon not moving after latest update this afternoon
« Reply #3 on: January 13, 2018, 10:03:39 AM »
Thanks. I saw that, but one of the replies was that it was going to be rectified today.

You're welcome, this has been a bug for a while now and there have been a few beta builds and program updates since then. I tend not to take dates as gospel.  There is new beta version 18.1.2323 (build 18.1.3769.0) out yesterday and as far as I'm aware this hasn't fixed this bug.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 18.8.2356/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ WinPatrol+/