I got hit by another 14 day reminder yesterday. This time I just X’d the tray icon whilst I was doing other things and it was killed without opening a window and interrupting me.
@prokopes Thanks for the reply. I look forward to a solution. I understand this isn’t the most pressing issue and other things will take priority, but then again this is something that has been going on for a long time now, and it is annoying, so I do hope eventually a fix will be implemented.
And again
Maybe I haven’t read everything, but it seems that no one has tried to reinstall Avast properly, disabled Windows “push” notifications, or used the hidden “geek:area” menu to see if there’s a setting related to the problem that needs to be enabled or disabled (e.g., disable Windows notifications).
As DavidR said, if you don’t want to send the logs or (phew, someone finally send them) selfishly wait for a response, this issue is going to keep annoying you for a while…
As for me, on my three devices, I’ve never seen these pop up in the taskbar.
And as for the notification area, the only times I’ve seen the blue circle is when a new device has joined the network (even if that’s not true—it’s always the same devices).
Even notifications like “Your IP is visible,” “Your identity is known,” etc., don’t appear in the notification area; they only show up if I open the UI.
But it’s maybe because I use “premium”
I don’t get Windows Notifications. It is the Avast program itself which opens minimized on the taskbar.
1 Like
Another occurrence today.
I have done a “Repair App”, to see if that does anything. I will find out in 14 days.
It happened here too just now
And again. It really is like clockwork. So what in Avast runs on a two week schedule? Can’t be that many things.
Same here. Just appears minimised in taskbar. I just ignore it and X it when I have finished other things.
My “repair app” obviously did nothing to help.
Maybe try a clean install? I’d do it myself but I really don’t want to deal with the forced full install and subsequent component uninstall (might mess up existing VPN etc), and all the dumb purple ‘new user’ hints and notifications. Both a result from lack of options to disable things, and choices foisted upon users.
And Again. Should we start calling this the Fortnight Frustration?
I would have thought that by now you would have been annoyed (mild version) enough to run the Support tool and submit the logs.
Or I guess we will see you in two weeks.
The problem doesn’t seem to be bothering you too much, because if I’d had a problem for six months, I would have tried a clean install ages ago – but anyway, you’ll be back here in a fortnight saying the same thing, with nothing having changed. 
By the way, have you checked the Windows scheduled tasks to make sure it isn’t that which is launching Avast every fortnight?
@DavidR
Oops, you were quicker 
The fact that this isn’t fixed after all this time is ridiculous. And yes, I will keep bumping this topic until things change!
I can’t do a clean install because Avast has chosen to forceably install ALL THEIR CRAP when doing so. Removing components afterwards, when potential damage to other software has already been done, is not an option.
2 Likes
Still not fixed. Just happened again.
NON sent logs. No feedback on whether they helped, or were investigated at all. Would more logs even actually make a difference? We don’t know because Avast doesn’t seem to care to keep us informed.
And no: there aren’t any Avast tasks in the scheduler besides the normal ones. None of those have 14-day triggers.
Well hello again.
I would suggest you send the logs (as it seems to be troubling your more). Hopefully, the more people who send logs the more likely it is that they will find the cause.
I’m still not seeing this issue you keep reporting every two weeks.
‘Hopefully’ isn’t good enough. Avast needs to respond and tell if NON’s logs were actually investigated seriously.
I’m still not about to send logs without knowing exactly what’s in them. That won’t change.
Also: you don’t have to reply to each bump with a repeat of your previous advice. I’m just keeping this topic from sinking into oblivion in the hope that they’ll keep being reminded the issue still exists, if and when an Avast employee deigns us worthy enough to grace us with a visit.
One set of logs isn’t going to be very definitive, the more they receive the more likely to find the reason.
So far this topic has run from Sept 2025 and only one who has experienced the issue and has sent the logs, is ‘NON’.
A very very long time ago (18 years or more ago) when internet connection speed was terrible, I had a problem, I saved my logs on a CD and posted it to Avast.
But its your system and your choice, see you in two weeks.