My computer not connected to Internet or LAN. So, I update Avast 4.8 manual. I mark it in settings of antivirus, but servise of Auto Update - aswUpdSv.exe is ON. And it service get some system recourses (216 KB memory). Can you fix it in next version? Or it service need for work manual update?
I think it might be needed even for other updates, not just the automatic ones.
The avast VPS updates are very CPU intensive.
There is a significant difference between automatic updates of the virus database and manual updates. The avast team have determined that the differences represent the requirements of avast users and therefore default options.
- Manual VPS updates
Will use all available CPU capacity. They will run for a shorter period than automatic updates but can appear to be “hogging” the CPU to the detriment of other activities of the system during the update.
- Automatic VPS updates
Will endeavor to not use more than 30% of CPU capacity. Therefore while the update may run for a longer time it should not affect other system use as much.
oh, thanks for your help. Theme is closed, i think?
Well, I’m not sure what updates exactly Shein referred to (as he wrote about an off-line computer, it might have been vpsupd.exe, for example).
In any case, I think (but I may be wrong) that the updating service is not there to schedule the automatic updates (ashServ.exe probably takes care of that) - but rather to help with the updating operation itself from the user-rights’ point of view (i.e. so that the update can be invoked from a restricted user account, and still update avast! files), no matter what type of update it is.
Igor, you are quite right, the vpsupd.exe downloads have super fast run times in my experience … apologies for leaving those out of my comments.
Well, I wasn’t saying anything about speed 
I was just trying to explain that the purpose of the service in question might not be the automatic updates per se, but rather performing the file updates under local system account - no matter if automatic/manual/vpsupd/full_installer update takes place.