Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Alikhan on February 02, 2016, 04:57:58 PM
-
Hi all,
I've been checking recently whether Avast VPS updates itself on startup on Windows 10 but it isn't - if I manually click update, the VPS definitions will update.
The streaming updates are not affected and always update.
Now I've been looking and when Windows 10 is enabled to fast boot (which is set by win10 default), Avast does not update until 60 mins later after startup (I have set my VPS updates to check every hour).
If Fast boot is disabled, the VPS updates happen at startup immediately.
Does anyone else have this happen to them?
-
Hello,
from what I read about win 10 fast boot it is combination of shutdown and hibernation. So maybe the hibernation is the reason that it does not look like boot of system but just wake up from hibernation.
Milos
-
Hello,
from what I read about win 10 fast boot it is combination of shutdown and hibernation. So maybe the hibernation is the reason that it does not look like boot of system but just wake up from hibernation.
Milos
Yes, that is the problem.
Certain AVs such as Eset have managed to update even through wake up for hibernation.
I think Avast needs to get this sorted since many users will be moving towards Windows 10 in the future and it wouldn't be good to be without the latest VPS for 240 minutes (which is default) until the next schedule update event happens.
I agree that streaming updates are not affected by this but the VPS is important too.
Is there any way Avast can overcome this in the future?
-
I have Windows 10 and have the same problem! I don't know why Avast hasn't fixed this yet either!
-
I have Windows 10 and have the same problem! I don't know why Avast hasn't fixed this yet either!
To be fair this hasn't been mentioned before so I await the next reply.
-
Bump..
This needs to be looked at.
-
Let's assume Avast is configured to check for updates every hour. Are you saying that if you shutdown your machine for more than an hour and then start it again, the virus definitions are not updated momentarily, but it takes another hour before that happens?
-
That's what happens to me. If I start the computer in the morning it will not update until 4 hours later. I'm using Avast Free 11.1.2253.
-
Let's assume Avast is configured to check for updates every hour. Are you saying that if you shutdown your machine for more than an hour and then start it again, the virus definitions are not updated momentarily, but it takes another hour before that happens?
Yes, that is correct.
You need to remember the default is every 4 hours though. So lets say the machine is shut down for more than 4 hours, the virus definitions are not updated momentarily, you will need to wait 4 hours, before it happens.
This only affects Windows 8/8.1 and 10 where the fast boot is enabled. Windows 7 is not affected.
I don't think it will be adviseful for users to be without the latest VPS updates.
The MAIN issue is what Milos said that Avast doesn't update itself on startup because fast boot is like waking up from hibernation (so avast doesn't think it's a system boot up)... but other anti-virus firms have found their way around this.
Edit: Fixed a typo.
-
Well, my initial understanding was that instead of attempting to update immediately on start (which is what happens on older OSes), the configured interval (4 hours by default) is sticked to (continuing through the time the machine is off), as if the shutdown didn't happen and the computer was running the whole time (example: the configured interval is 4 hours, you shut down the machine for 3 hours - and then it takes another hour for the check to happen).
That would be OK in my opinion; different from the behavior on older Windows, but not necessarily wrong.
However, if you start the computer after it's been off for a long period, and the whole interval (say 4 hours) just starts at the moment - then it's wrong. I'd say a check for a new update still "happens" right after the machine starts even in that case, but maybe it fails for some reason (network hasn't started yet?) and the interval resets. (But I'm really just speculating at the moment.)
-
Well, my initial understanding was that instead of attempting to update immediately on start (which is what happens on older OSes), the configured interval (4 hours by default) is sticked to (continuing through the time the machine is off), as if the shutdown didn't happen and the computer was running the whole time (example: the configured interval is 4 hours, you shut down the machine for 3 hours - and then it takes another hour for the check to happen).
That would be OK in my opinion; different from the behavior on older Windows, but not necessarily wrong.
However, if you start the computer after it's been off for a long period, and the whole interval (say 4 hours) just starts at the moment - then it's wrong. I'd say a check for a new update still "happens" right after the machine starts even in that case, but maybe it fails for some reason (network hasn't started yet?) and the interval resets. (But I'm really just speculating at the moment.)
I agree with your first paragraph and I see nothing wrong there.
However, I do not think the update check happens after the interval at startup - due to fast boot on Win 10. I've tested this out on a wide range of PCs and laptops with both wired and wireless connections.
The streaming updates happen immediately during startup too and they are NOT affected by this.
I have tested with other anti viruses on the same PCs and the update happens immediately with them at startup.
I don't think this is related to the network starting but rather something to do with Avast.
It's also worth mentioning that if fast boot is disabled, Avast updates the VPS fine without any problems at startup.
Feel free to test it and you will see.
Thanks.
-
@Alikhan
Could you tell me who those other AV's are that work when you first start your computer?
-
@Alikhan
Could you tell me who those other AV's are that work when you first start your computer?
I'd rather not to be honest... I just want Avast to fix the issue.
-
No Problem. I agree I want them to fix the problem also!
-
Bump...
Answer is needed.
-
Bump.... has there been any development?
-
I PM'ed igor but have not heard anything back!
-
HI I just thought I would add my thoughts if I may this morning avast free did not update the definitions so I decided to go through the power options in control panel and I disabled fast boot and restarted my Windows 10 home edition desktop and when I got to the desktop I checked avast free by going to the update and clicking and sure enough the definitions were up to date at 11-0. I just thought I would also put a thought in.
Thanks avast team hope this helps and I hope this issue get resolved sooner then later.
-
....
Can the Avast team give a reply back...
It's been more than week.
-
Can the Avast team give a reply back...
Well, they already did, see Reply #1/#3/#9.
-
Well, my initial understanding was that instead of attempting to update immediately on start (which is what happens on older OSes), the configured interval (4 hours by default) is sticked to (continuing through the time the machine is off), as if the shutdown didn't happen and the computer was running the whole time (example: the configured interval is 4 hours, you shut down the machine for 3 hours - and then it takes another hour for the check to happen).
That would be OK in my opinion; different from the behavior on older Windows, but not necessarily wrong.
However, if you start the computer after it's been off for a long period, and the whole interval (say 4 hours) just starts at the moment - then it's wrong. I'd say a check for a new update still "happens" right after the machine starts even in that case, but maybe it fails for some reason (network hasn't started yet?) and the interval resets. (But I'm really just speculating at the moment.)
I agree with your first paragraph and I see nothing wrong there.
However, I do not think the update check happens after the interval at startup - due to fast boot on Win 10. I've tested this out on a wide range of PCs and laptops with both wired and wireless connections.
The streaming updates happen immediately during startup too and they are NOT affected by this.
I have tested with other anti viruses on the same PCs and the update happens immediately with them at startup.
I don't think this is related to the network starting but rather something to do with Avast.
It's also worth mentioning that if fast boot is disabled, Avast updates the VPS fine without any problems at startup.
Feel free to test it and you will see.
Thanks.
I want an answer to this from them...
-
As long as the stream updates work for you, I can't see any real problem here.
-
For what it is worth over years Hibernation has caused real problems within Windows......not O/S but other software.
Normal "sleep" provides all the "power" levels you need so all Hibernation does is quicker starts or re-starts.
https://msdn.microsoft.com/en-us/library/windows/hardware/jj835779%28v=vs.85%29.aspx
Win10 uses Hibernation as its trick for fast boot.....but oddly a power down is just a hibernation, a restart is a true boot.
For me there is too many variables for a problem to occur (not just me making mistakes but 3rd party software packages.....their drivers, etc.) that I cannot readily understand.
Also, "for me" a "return from sleep mode" is fine in its speed/quickness.
Thus, in my experience with Hibernation over the years the risk/reward is heavily weighted as too much problem for too little glory. :)
Anyway, my point is I "disable" hibernation in every PC...first thing I do with new PC.
It's real simple (c:\windows\sysmtem32\powercfg -h off) process to disable: https://support.microsoft.com/en-us/kb/920730
Here is link on Fast Startup disabling: http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html
.....but simply disabling Hibernate takes care of this.
Anyway, just FYI in case there is interest...........