I have problem i can’t updates from nonadmin account on windows xp sp 2( on admini account update come without any problem ) ,i don’t know why always was no problem but now what can be wrong .I use comondo firewall avast.setup are showing up on taskbar but firewall dont show any active from avast when i start update ???
What version of avast are you using, 4.7.892 is the latest regular release ?
The program updates can’t be done from a limited user account, but I believe it is possible to do VPS updates on a limited user account, so what update were you trying to do ?
I suggest you delete the entry for avast.setup and do a manual update and have the firewall ask permission again. I believe there have been some problems with comodo (a forum search for comodo and beta might return some information), can’t recall if they might have had something like this but people have tried the beta release of comodo.
velox, let me correct you. avast! can be updated from nonadmin account but from advanced user.
However I wonder too why avast! can’t be updated from user and limited user accounts? ???
Another point is you use quick switching from accounts avast! doesn’t unload himself from memory. I mean that if I’ll switch avast! off as user and logout his resident protection won’t work when I login as another user (even as administrator).
You wouldn’t want a limited user being able to update the program (not VPS), which was installed by the administrator or a user with administrator privileges.
Administrator could update program and virus database.
Limited users could update only the virus database.
I’m not sure about advanced users, but probably, only the virus database too.
I’ve been looking around but can’t find a solution for the same or similar problem on WinXP SP1 with Avast 4.7.942. Problem: Update of virus database is not working as non administrator account. (If I make myself member of Administrators, it’s working fine.)
It’s also not working manually via menu:
->Settings, Update(basic),Virus Database, “Update now…”
I just get the “Summary” window about the update, but nothing happens.
I don’t get the “Downloading Packages” window, and the database version stays indeed the same.
Am I the only one having that problem ??? [edit: layout emphasized about problem]
On a side note, whenever you see symptoms like "I try Add/Remove Programs -> avast and nothing happens" or "I try to invoke avast update and nothing happens", the cure that almost always works is to kill any running instances of the process "avast.setup" (or avast01.setup, avast02.setup etc. - if these are running as well). This can be done from the Processes tab in the Task Manager.
Thanks Tech for your reply :). Unfortunately it’s no solution in my case :(.
The only processes I can find related to Avast are:
ashDisp.exe 1264 avast! service GUI component 4.07.0936.0000
ashMaiSv.exe 2596 NT AUTHORITY\SYSTEM
ashServ.exe 832 NT AUTHORITY\SYSTEM
ashWebSv.exe 2688 NT AUTHORITY\SYSTEM
aswUpdSv.exe 3680 NT AUTHORITY\SYSTEM
Remark: File versions of Avast are all max. version 4.07.0936.0, but I’m using version build 4.7.942, like “About avast!” tells me.
I checked the advice(s) before already of the post: Avast automatic update only for system administrator
-“avast!iAVS4 Control Service” is running in system account with interaction to desktop.
-I can ping to the Avast update server as non administrator.
I found a few posts with similar topics on this forum, but it seems with no solution at the end.
Or the user has changed to another antivirus application, which I have to do at the end maybe as well :(.
[edit: layout]
I checked the Setup.log files (In Setup and Data\log directories) for a few days.
It seems that in the Setup.log files, only lines are added when I’m administrator, at least so far regarding the updates.
Both files end with “Stopped: 14.03.2007, 21:52:31”, which was the time of the successful update as administrator.
Further on, the following files where last time changed after successful update (when I was adminstrator).
Avast\Setup\part-vps-72302.vpu
Avast\Setup\vps-72300.vpu
Avast\Setup\vpsm-72302.vpu
Avast\Setup\setup.log
Avast\DATA\400.vps
Avast\DATA\log\Setup.log (has already Full Control for Everyone")
Giving them “Full Control” rights like administrators isn’t a solution as well.
The file “Avast\DATA\log\Warning.log” has many errors for failed updates as follows:
<date & time> 1173982026 3500 Function setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 00000000.
<date & time> 1173982422 1092 Function setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 72FE02C0.
PS: Only numbers after “Return Code” are mostly the same.
I will dig some more into the “setifaceUpdatePackages()” message on this forum, but so far not much useful found
I checked a bit more on the firewall side (Firewall Comodo version 2.3.5.62):
Removed Avast.setup (and all others from Avast) from firewall ->is not asking for access when starting update (manually or Avast’s request) ->it seems Avast! doesn’t get to the point where it needs access!?
I don’t know what’s the value of the “Test Connection” in Proxy server Settings", but that works fine as non adminstrator.
And on “Test Connection” the “setup.ovr” asks for Internet connection.
Maybe I try to install Avast on another machine and do some more experiments there… (to be continued)
Strange… it should be there… I have a ‘lot’ of avast versions because: home skin, professional, BART CD, avast for PDA, a script for automated updates, etc. All of them uses an avast.setup version.
The file setup.ovr is transformed on avast.setup to update but, strangely, in your case, it is setup.ovr which asks connection…
Problem partially Solved
I finally came to the conclusion that the problem is related to permission rights in the SetUp directory.
I gave only the files in Setup directory extra permission like this:
Avast\Setup\INF directory: make not inherited
Avast\Setup\setiface.dll file: make not inherited (doesn’t need write permission)
Avast\Setup directory: make not inherited
Avast\Setup directory: add permission “Write Data / Create Files”
AFAIK, in XPhome this can only be done from the command line, which is rather a pain in the ass.
Even in XPpro is it a bit complicated, and accidental permission change is easy made (no go back).
So using ACLView from Native Computer Systems Tools can make that a lot easier.
After these changes, my Avast virus database update works so far OK. Dowload Packages window comes up etc…
I hope it stays like that :-\ . Now have to wait for new available update…
[edit:] Partially solved
It’s downloading the packages, but it seems not installing them. Compilation date of database stays the same!
Strange that this happens with XP from time to time, from user to user.
For any reason, in the past, the Windows Media Player folder get ‘corrupted’ permissions. It took some time for me to discover why it wasn’t updating to a new version…
Ok here’s my theory on the Avast update question in a Windows XP Limited User account. I may as well have a theory of my own.
First off - thanks to wain for pointing out something that hadn’t occurred to me. Manual updates are not allowed from a limited user account. By design they do not work. However automatic updates work just fine from a limited user account. My theory is that Avast is able to adjust the security for its pertinent folder(s) in order to accommodate a virus data base “automatic” update. Once the update is completed successfully, Avast “fixes” or returns the security to any folder(s) involved which will mean of course no write access from a limited user account. Which also means no manual updates. This is why if I were to alter the permissions manually (as wain pointed out here) or even customize the installation into folders with liberal permissions - Avast would update manually from a limited user account without any problems. By circumventing a security design of sorts, I could force Avast to do what the programmers, I suspect, did not intend, i.e., update manually willy nilly from a limited user account. If my theory is correct, then I get it. I suppose I can even live with it.
This morning Avast updated successfully on its own from my limited user account. This is a good thing.
Program updates are not allowed.
Virus database updates work fine here in a limited user account, both manual and automatic.
No folder access rights are changed during updates.
On a limited user account the update is carried on by ‘System’ user and not the common user logged on.
You can test… but avast does not change any access rights during updates. Worse, you can mess your installation changing the permissions of the antivirus folder and files… take care.
I will tell you that “manual” updates do not work for me and a few others from a limited user account. I have contacted AVAST directly for further enlightenment. If you have confirmed beyond a reasonable doubt that manual updates work all the time from a bonafide Windows XP SP2 Home Ed. Limited user account using Avast 4.7 Home(FREE) Build Jan2007(4.7.942) - then I surely would love to know the difference between your config and mine. Thank you for your thoughts on this matter.
Clue: If the permissions ARE changed on the Avast folders - the manual update in the LU account works every time. I confirmed this by installing Avast into a non default location where permissions were liberal. However when Avast is in its default location (\Program Files), everything works fine in the Limited User account EXCEPT if I decide to perform a manual update out of the blue - all I get is a pop up telling me the status of the most recent update. No other activity. Otherwise the automatic updates are performing flawlessly.
(Incidentally, I never ever fiddled with permissions manually from Safe Mode or using wain’s suggestion. I only tested liberal permissions by installing Avast into a non default location. That is all.)