I often turn my PC on, and receive an anti-virus warning that my Avast had expired and that I’m not protected… We use Avast Endpoint Protection with more than enough licenses.
Attachments AvastA and AvastB shows the messages. Once I’ve rebooted, I get attachment AvastD…
Please help?
Are you using fast-boot on that system ?
If so, disable it.
I’ll try that, but please explain how fast-boot could have an effect on anti-virus subscription? I like fast-boot…
With the fast boot option enabled a system isn’t shutting down completely.
Meaning not everything will be loaded when you boot.
That can mean certain information is not retrieved by a application.
Most computers are connecting to NTP server at startup, especially in AD environment. If avast “intercept” any change of time-stamp in the self loading frame will consider this as a license issue. The result is an unprotected user. Restarting only the Avast Net-Client Service will correct instantly the problem. Is my simple theory, we have the same problem on many corporate workstation. Unfortunately support team was, probably, unable to search and discover the cause. Of course - support ticket, tons of logs uploaded, etc. Waste of time…
Sorry to chime in late on this, but I’ve been away.
I see this a lot on my network. All machines are Win 7 with no “fast boot” option like those in Win 8 or Win 10. We do not use an NTP server to set the time on the machines. We do use SOA on an ordinary Win 7 Ultimate box.
I have about 130 machines on the network, still with plenty of licenses to spare.
My theory is that it’s due to the fact that I’m not using a true server OS for the SOA. Win 7 Ultimate allows a maximum of 20 concurrent connections. Most people start their computers around the same time every morning, so it seems likely that some of those machines simply can’t get a connection to the SOA.
I, too, filed a ticket and spent a lot of time going back and forth with Avast with no results to show for it.
However, I will say that I am seeing this less frequently with Endpoint Protection 8.0.1607 than with earlier versions. It does still happen though.
Hi,
Same here. Normally a handful of machines each day fail to connect to the SOA Console properly (different machines each time).
Today we have around 50% of the machines reporting licensing errors.
For the record, my system is running on Windows Server 2008, so I don’t think it is a connection limit issue in my case.
Kind Regards, Stephen