Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: velox on January 09, 2007, 09:19:46 PM

Title: updates possible only on admin account why ??
Post by: velox on January 09, 2007, 09:19:46 PM
Hello 
Thx Avast Team for their great  job !!! :D

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 ???  :'(
 
Title: Re: updates possible only on admin account why ??
Post by: DavidR on January 09, 2007, 11:16:24 PM
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.
Title: Re: updates possible only on admin account why ??
Post by: t l s on January 09, 2007, 11:21:03 PM
It is possible to do VPS updates on a limited user account (which is what I normally use).
Title: Re: updates possible only on admin account why ??
Post by: sergofun on January 09, 2007, 11:23:42 PM
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).
Title: Re: updates possible only on admin account why ??
Post by: DavidR on January 09, 2007, 11:39:02 PM
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.
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on January 10, 2007, 02:03:14 AM
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.
Title: Re: updates possible only on admin account why ??
Post by: wain on March 10, 2007, 12:34:09 AM
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]
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on March 10, 2007, 09:44:15 PM
I just get the "Summary" window about the update, but nothing happens.
Vlk (our guru) said:
Quote
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.
Title: Re: updates possible only on admin account why ??
Post by: wain on March 11, 2007, 02:32:21 PM
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      <runs in users account>
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 (http://forum.avast.com/index.php?topic=20047.0)
-"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]
Title: Re: updates possible only on admin account why ??
Post by: kubecj on March 11, 2007, 06:22:58 PM
Have you tried to go thru setup.log if there is anything interesting - ie. if you see any difference between admin / non-admin accesses?
Title: Re: updates possible only on admin account why ??
Post by: wain on March 15, 2007, 08:00:55 PM
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   <my username>   3500   Function setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 00000000.
   <date & time>  1173982422   <my username>   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 :(
Title: Re: updates possible only on admin account why ??
Post by: kubecj on March 15, 2007, 09:27:19 PM
0x426 is service was not started.

Something is probably blocking avast updater service which is needed for successful updates under non-admin account.
Title: Re: updates possible only on admin account why ??
Post by: wain on March 15, 2007, 11:35:17 PM
@kubecj: Yes, I just found that out too from your answer in the post 4.7 : Updating pbl error 0x426 - 0x2 (http://forum.avast.com/index.php?topic=20812.0) :).

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)
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on March 16, 2007, 12:13:53 AM
it seems Avast! doesn't get to the point where it needs access!?
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.

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.
The file setup.ovr is transformed on avast.setup to update but, strangely, in your case, it is setup.ovr which asks connection...
Title: Re: updates possible only on admin account why ??
Post by: wain on March 18, 2007, 12:17:08 AM
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 (http://www.nativecs.com/index.en.php) 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!
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on March 18, 2007, 01:27:31 AM
I finally came to the conclusion that the problem is related to permission rights in the SetUp directory.
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...
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 11:44:53 AM
Problem 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 (http://www.nativecs.com/index.en.php) 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....

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.  :)

Title: Re: updates possible only on admin account why ??
Post by: Lisandro on March 19, 2007, 02:46:29 PM
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.
Program updates are not allowed.
Virus database updates work fine here in a limited user account, both manual and automatic.

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.
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.

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.
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.
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 04:44:45 PM
  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.)

Title: Re: updates possible only on admin account why ??
Post by: kubecj on March 19, 2007, 04:49:22 PM
Is the avast update service running?
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 04:51:05 PM
Is the avast update service running?

Absolutely!  The update service is both visible in the Task Manager and in Windows XP services.msc module.  And YES, the LOG ON properties of this service is associated with LOCAL SYSTEM ACCOUNT as Tech suggested.  (and this is a bit of useless info - but AVG 7.x worked flawlessly from a LU account both manually and automatically.  AVG is not on my system today.)  I wonder if anybody else with this trouble is using ZoneAlarm 6.x or 7.x on their system.  Although ZA permissions are in order else how could the automatic updates work so well?
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on March 19, 2007, 07:02:49 PM
Can you, please, check the log files and post the last 150 lines of these logs:
C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log
C:\Program Files\Alwil Software\Avast4\Setup\setup.log
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 07:38:25 PM
C:\Program Files\Alwil Software\Avast4\Setup\setup.log

04:58:03 nrm/pkg  Transferred bytes: 362664
04:58:03 nrm/pkg  Transfer time: 105296 ms
04:58:03 vrb/int  Sending stats 'http://download99.avast.com/cgi-bin/iavs4stats.cgi': 00000000 204
04:58:03 vrb/fil  NeedReboot=false
04:58:03 min/gen  Return code: 0x20000000 [Something done]
04:58:03 min/gen  Stopped: 19.03.2007, 04:58:03
04:58:03 min/gen  Started: 19.03.2007, 04:58:03
04:58:03 min/gen  Running setup_av_pro-3ae (942)
04:58:03 nrm/sys  Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
04:58:03 vrb/sys  Computer WinName: XXX-XXX
04:58:03 min/sys  Windows Net User: SYSTEM
04:58:03 min/gen  Cmdline: /refresh /noreboot /updatevps /verysilent
04:58:03 vrb/gen  Operation set to INST_OP_UPDATE_INSTALL_PACKAGES
04:58:03 min/gen  Old version: 3ae (942)
04:58:03 nrm/gen  SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
04:58:03 nrm/int  SYNCER: Type: use IE settings
04:58:03 nrm/int  SYNCER: Auth: another authentication, use WinInet
04:58:04 vrb/pkg  Part prg_av_pro-3ae is installed
04:58:04 vrb/pkg  Part vps-72500 is installed
04:58:04 vrb/pkg  Part news-4b is installed
04:58:04 vrb/pkg  Part setup_av_pro-3ae is installed
04:58:04 min/gen  Old version: 3ae (942)
04:58:04 vrb/fil  SetExistingFilesBitmap: 937->145->145
04:58:04 min/gen  GUID: c094c804-36f5-4c01-9bf1-f9f6e3f4f064
04:58:04 vrb/gen  Entering:UpdateInstallPackages
04:58:04 min/pkg  Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
04:58:04 vrb/pkg  LatestPartInfo: news = news-4b
04:58:04 vrb/pkg  LatestPartInfo: program = prg_av_pro-3ae
04:58:04 vrb/pkg  LatestPartInfo: setup = setup_av_pro-3ae
04:58:04 vrb/pkg  LatestPartInfo: vps = vps-72500
04:58:04 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
04:58:04 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
04:58:04 vrb/pkg  ArePartsInstallable: 1
04:58:07 min/pkg  vps: updated [072500]
04:58:07 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\*.*
04:58:07 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\*.*
04:58:07 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HELP\*.*
04:58:07 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HtmlData\*.*
04:58:07 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\images\*.*
04:58:07 nrm/pkg  Transferred files: 0
04:58:07 nrm/pkg  Transferred bytes: 0
04:58:07 nrm/pkg  Transfer time: 0 ms
04:58:07 vrb/fil  NeedReboot=false
04:58:07 min/gen  Return code: 0x20000000 [Something done]
04:58:07 min/gen  Stopped: 19.03.2007, 04:58:07
10:32:57 min/gen  Started: 19.03.2007, 10:32:57
10:32:57 min/gen  Running setup_av_pro-3ae (942)
10:32:57 nrm/sys  Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
10:32:57 vrb/sys  Computer WinName: XXX-XXX
10:32:57 min/sys  Windows Net User: SYSTEM
10:32:57 min/gen  Cmdline: /downloadpkgs /noreboot /updatevps /verysilent
10:32:57 vrb/gen  DldSrc set to inet
10:32:57 vrb/gen  Operation set to INST_OP_UPDATE_GET_PACKAGES
10:32:57 min/gen  Old version: 3ae (942)
10:32:57 nrm/gen  SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
10:32:57 vrb/sys  Computer DnsName: home-alone
10:32:57 vrb/sys  Computer Ip Addr: 63.69.XXX.XX
10:32:57 nrm/int  SYNCER: Type: use IE settings
10:32:57 nrm/int  SYNCER: Auth: another authentication, use WinInet
10:32:57 vrb/pkg  Part prg_av_pro-3ae is installed
10:32:57 vrb/pkg  Part vps-72500 is installed
10:32:57 vrb/pkg  Part news-4b is installed
10:32:57 vrb/pkg  Part setup_av_pro-3ae is installed
10:32:57 min/gen  Old version: 3ae (942)
10:32:57 vrb/fil  SetExistingFilesBitmap: 937->145->145
10:32:57 min/gen  GUID: c094c804-36f5-4c01-9bf1-f9f6e3f4f064
10:32:58 nrm/gen  Server definition(s) loaded for 'main': 105 (maintenance:0)
10:32:58 nrm/gen  SelectCurrent: selected server 'Download67 AVAST server' from 'main'
10:32:58 min/pkg  GetPackages - set proxy for inet
10:32:58 nrm/int  SYNCER: Type: use IE settings
10:32:58 nrm/int  SYNCER: Auth: another authentication, use WinInet
10:33:00 vrb/gen  Used server: http://download67.avast.com/iavs4x
10:33:00 nrm/gen  Server definition(s) loaded for 'main': 105 (maintenance:0)
10:33:00 nrm/gen  SelectCurrent: selected server 'Download47 AVAST server' from 'main'
10:33:00 min/pkg  GetPackages - set proxy for inet
10:33:00 nrm/int  SYNCER: Type: use IE settings
10:33:00 nrm/int  SYNCER: Auth: another authentication, use WinInet
10:33:01 vrb/gen  Used server: http://download47.avast.com/iavs4x
10:33:01 vrb/gen  Used server: http://download47.avast.com/iavs4x
10:33:01 min/gen  Part of license key: W49757335H4100AXXXXX
10:33:01 min/pkg  Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
10:33:01 vrb/pkg  LatestPartInfo: news = news-4b
10:33:01 vrb/pkg  LatestPartInfo: program = prg_av_pro-3ae
10:33:01 vrb/pkg  LatestPartInfo: setup = setup_av_pro-3ae
10:33:01 vrb/pkg  LatestPartInfo: vps = vps-72501
10:33:02 vrb/gen  Used server: http://download47.avast.com/iavs4x
10:33:02 vrb/pkg  Part vps-72501 was set to be installed
10:33:02 vrb/pkg  Removed obsolete file part-vps-72500.vpu
10:33:02 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
10:33:02 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
10:33:02 vrb/pkg  IsFullOkay: vpsm-72501.vpu - not okay
10:33:02 vrb/pkg  IsFullOkay: vpsm-72501.vpu - not okay
10:33:02 vrb/pkg  IsFullOkay: vpsm-72501.vpu - not okay
10:33:02 vrb/pkg  IsFullOkay: vpsm-72501.vpu - not okay
10:33:04 vrb/gen  Used server: http://download47.avast.com/iavs4x
10:33:04 nrm/pkg  DldPackage: C:\Program Files\Alwil Software\Avast4\Setup\vpsm-72501.vpu, returned 0x00000000
10:33:04 vrb/pkg  Removed obsolete file vpsm-72500.vpu
10:33:07 min/pkg  vps: needs to be updated [072501]
10:33:07 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
10:33:07 nrm/pkg  Transferred files: 5
10:33:07 nrm/pkg  Transferred bytes: 7652
10:33:07 nrm/pkg  Transfer time: 5686 ms
10:33:07 vrb/int  Sending stats 'http://download47.avast.com/cgi-bin/iavs4stats.cgi': 00000000 204
10:33:07 vrb/fil  NeedReboot=false
10:33:07 min/gen  Return code: 0x20000000 [Something done]
10:33:07 min/gen  Stopped: 19.03.2007, 10:33:07
10:33:08 min/gen  Started: 19.03.2007, 10:33:08
10:33:08 min/gen  Running setup_av_pro-3ae (942)
10:33:08 nrm/sys  Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
10:33:08 vrb/sys  Computer WinName: XXX-XXX
10:33:08 min/sys  Windows Net User: SYSTEM
10:33:08 min/gen  Cmdline: /refresh /noreboot /updatevps /verysilent
10:33:08 vrb/gen  Operation set to INST_OP_UPDATE_INSTALL_PACKAGES
10:33:08 min/gen  Old version: 3ae (942)
10:33:08 nrm/gen  SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
10:33:08 nrm/int  SYNCER: Type: use IE settings
10:33:08 nrm/int  SYNCER: Auth: another authentication, use WinInet
10:33:08 vrb/pkg  Part prg_av_pro-3ae is installed
10:33:08 vrb/pkg  Part vps-72501 is installed
10:33:08 vrb/pkg  Part news-4b is installed
10:33:08 vrb/pkg  Part setup_av_pro-3ae is installed
10:33:08 min/gen  Old version: 3ae (942)
10:33:08 vrb/fil  SetExistingFilesBitmap: 937->145->145
10:33:08 min/gen  GUID: c094c804-36f5-4c01-9bf1-f9f6e3f4f064
10:33:08 vrb/gen  Entering:UpdateInstallPackages
10:33:08 min/pkg  Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
10:33:08 vrb/pkg  LatestPartInfo: news = news-4b
10:33:08 vrb/pkg  LatestPartInfo: program = prg_av_pro-3ae
10:33:08 vrb/pkg  LatestPartInfo: setup = setup_av_pro-3ae
10:33:08 vrb/pkg  LatestPartInfo: vps = vps-72501
10:33:08 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
10:33:08 vrb/pkg  FilterOutExistingFiles: 145 & 145 = 0
10:33:08 vrb/pkg  ArePartsInstallable: 1
10:33:11 min/pkg  vps: updated [072501]
10:33:11 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\*.*
10:33:11 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\*.*
10:33:11 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HELP\*.*
10:33:11 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HtmlData\*.*
10:33:11 vrb/fil  Fix security on: C:\Program Files\Alwil Software\Avast4\images\*.*

10:33:11 nrm/pkg  Transferred files: 0
10:33:11 nrm/pkg  Transferred bytes: 0
10:33:11 nrm/pkg  Transfer time: 0 ms
10:33:11 vrb/fil  NeedReboot=false
10:33:11 min/gen  Return code: 0x20000000 [Something done]
10:33:11 min/gen  Stopped: 19.03.2007, 10:33:11
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on March 19, 2007, 07:44:03 PM
Thanks bcool, hope Kubecj has something to say...
Indeed, what that permissions changing are doing there I don't know...
Title: Re: updates possible only on admin account why ??
Post by: kubecj on March 19, 2007, 07:48:47 PM
This shows only successful downloads under SYSTEM account. I'd try unsuccessful (manual) update and then I'd check if anything has changed in log.
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 07:53:00 PM
I can tell you already there is not change to the logs because it is not written to on any unsuccessful manual attempts.  Nothing is logged on manual attempts except for in Avast! Log Viewer.   This would be compatible with the theory that access to the setup.log(s) are only permitted during automatic updates and other Avast system functions but clearly not on manual updates.
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 07:54:05 PM
C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log

19.03.2007   04:58:07.000   1174298287   file   Fix security on: C:\Program Files\Alwil Software\Avast4\*.*
19.03.2007   04:58:07.000   1174298287   file   Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\*.*
19.03.2007   04:58:07.000   1174298287   file   Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HELP\*.*
19.03.2007   04:58:07.000   1174298287   file   Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HtmlData\*.*
19.03.2007   04:58:07.000   1174298287   file   Fix security on: C:\Program Files\Alwil Software\Avast4\images\*.*
19.03.2007   04:58:07.000   1174298287   package   Transferred files: 0
19.03.2007   04:58:07.000   1174298287   package   Transferred bytes: 0
19.03.2007   04:58:07.000   1174298287   package   Transfer time: 0 ms
19.03.2007   04:58:07.000   1174298287   file   NeedReboot=false
19.03.2007   04:58:07.000   1174298287   general   Return code: 0x20000000 [Something done]
19.03.2007   04:58:07.000   1174298287   general   Stopped: 19.03.2007, 04:58:07
19.03.2007   10:32:57.000   1174318377   general   Started: 19.03.2007, 10:32:57
19.03.2007   10:32:57.000   1174318377   general   Running setup_av_pro-3ae (942)
19.03.2007   10:32:57.000   1174318377   system   Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
19.03.2007   10:32:57.000   1174318377   system   Computer WinName: XXX-XXX
19.03.2007   10:32:57.000   1174318377   system   Windows Net User: SYSTEM
19.03.2007   10:32:57.000   1174318377   general   Cmdline: /downloadpkgs /noreboot /updatevps /verysilent
19.03.2007   10:32:57.000   1174318377   general   DldSrc set to inet
19.03.2007   10:32:57.000   1174318377   general   Operation set to INST_OP_UPDATE_GET_PACKAGES
19.03.2007   10:32:57.000   1174318377   general   Old version: 3ae (942)
19.03.2007   10:32:57.000   1174318377   general   SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
19.03.2007   10:32:57.000   1174318377   system   Computer DnsName: XXX-XXX
19.03.2007   10:32:57.000   1174318377   system   Computer Ip Addr: 63.69.XXX.XX
19.03.2007   10:32:57.000   1174318377   internet   SYNCER: Type: use IE settings
19.03.2007   10:32:57.000   1174318377   internet   SYNCER: Auth: another authentication, use WinInet
19.03.2007   10:32:57.000   1174318377   package   Part prg_av_pro-3ae is installed
19.03.2007   10:32:57.000   1174318377   package   Part vps-72500 is installed
19.03.2007   10:32:57.000   1174318377   package   Part news-4b is installed
19.03.2007   10:32:57.000   1174318377   package   Part setup_av_pro-3ae is installed
19.03.2007   10:32:57.000   1174318377   general   Old version: 3ae (942)
19.03.2007   10:32:57.000   1174318377   file   SetExistingFilesBitmap: 937->145->145
19.03.2007   10:32:57.000   1174318377   general   GUID: c094c804-36f5-4c01-9bf1-f9f6e3f4f064
19.03.2007   10:32:58.000   1174318378   general   Server definition(s) loaded for 'main': 105 (maintenance:0)
19.03.2007   10:32:58.000   1174318378   general   SelectCurrent: selected server 'Download67 AVAST server' from 'main'
19.03.2007   10:32:58.000   1174318378   package   GetPackages - set proxy for inet
19.03.2007   10:32:58.000   1174318378   internet   SYNCER: Type: use IE settings
19.03.2007   10:32:58.000   1174318378   internet   SYNCER: Auth: another authentication, use WinInet
19.03.2007   10:33:00.000   1174318380   general   Used server: http://download67.avast.com/iavs4x
19.03.2007   10:33:00.000   1174318380   general   Server definition(s) loaded for 'main': 105 (maintenance:0)
19.03.2007   10:33:00.000   1174318380   general   SelectCurrent: selected server 'Download47 AVAST server' from 'main'
19.03.2007   10:33:00.000   1174318380   package   GetPackages - set proxy for inet
19.03.2007   10:33:00.000   1174318380   internet   SYNCER: Type: use IE settings
19.03.2007   10:33:00.000   1174318380   internet   SYNCER: Auth: another authentication, use WinInet
19.03.2007   10:33:01.000   1174318381   general   Used server: http://download47.avast.com/iavs4x
19.03.2007   10:33:01.000   1174318381   general   Used server: http://download47.avast.com/iavs4x
19.03.2007   10:33:01.000   1174318381   general   Part of license key: W49757335H4100AXXXX
19.03.2007   10:33:01.000   1174318381   package   Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
19.03.2007   10:33:01.000   1174318381   package   LatestPartInfo: news = news-4b
19.03.2007   10:33:01.000   1174318381   package   LatestPartInfo: program = prg_av_pro-3ae
19.03.2007   10:33:01.000   1174318381   package   LatestPartInfo: setup = setup_av_pro-3ae
19.03.2007   10:33:01.000   1174318381   package   LatestPartInfo: vps = vps-72501
19.03.2007   10:33:02.000   1174318382   general   Used server: http://download47.avast.com/iavs4x
19.03.2007   10:33:02.000   1174318382   package   Part vps-72501 was set to be installed
19.03.2007   10:33:02.000   1174318382   package   Removed obsolete file part-vps-72500.vpu
19.03.2007   10:33:02.000   1174318382   package   FilterOutExistingFiles: 145 & 145 = 0
19.03.2007   10:33:02.000   1174318382   package   FilterOutExistingFiles: 145 & 145 = 0
19.03.2007   10:33:02.000   1174318382   package   IsFullOkay: vpsm-72501.vpu - not okay
19.03.2007   10:33:02.000   1174318382   package   IsFullOkay: vpsm-72501.vpu - not okay
19.03.2007   10:33:02.000   1174318382   package   IsFullOkay: vpsm-72501.vpu - not okay
19.03.2007   10:33:02.000   1174318382   package   IsFullOkay: vpsm-72501.vpu - not okay
19.03.2007   10:33:04.000   1174318384   general   Used server: http://download47.avast.com/iavs4x
19.03.2007   10:33:04.000   1174318384   package   DldPackage: C:\Program Files\Alwil Software\Avast4\Setup\vpsm-72501.vpu, returned 0x00000000
19.03.2007   10:33:04.000   1174318384   package   Removed obsolete file vpsm-72500.vpu
19.03.2007   10:33:07.000   1174318387   package   vps: needs to be updated [072501]
19.03.2007   10:33:07.000   1174318387   package   FilterOutExistingFiles: 145 & 145 = 0
19.03.2007   10:33:07.000   1174318387   package   Transferred files: 5
19.03.2007   10:33:07.000   1174318387   package   Transferred bytes: 7652
19.03.2007   10:33:07.000   1174318387   package   Transfer time: 5686 ms
19.03.2007   10:33:07.000   1174318387   internet   Sending stats 'http://download47.avast.com/cgi-bin/iavs4stats.cgi': 00000000 204
19.03.2007   10:33:07.000   1174318387   file   NeedReboot=false
19.03.2007   10:33:07.000   1174318387   general   Return code: 0x20000000 [Something done]
19.03.2007   10:33:07.000   1174318387   general   Stopped: 19.03.2007, 10:33:07
19.03.2007   10:33:08.000   1174318388   general   Started: 19.03.2007, 10:33:08
19.03.2007   10:33:08.000   1174318388   general   Running setup_av_pro-3ae (942)
19.03.2007   10:33:08.000   1174318388   system   Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
19.03.2007   10:33:08.000   1174318388   system   Computer WinName: XXX-XXX
19.03.2007   10:33:08.000   1174318388   system   Windows Net User: SYSTEM
19.03.2007   10:33:08.000   1174318388   general   Cmdline: /refresh /noreboot /updatevps /verysilent
19.03.2007   10:33:08.000   1174318388   general   Operation set to INST_OP_UPDATE_INSTALL_PACKAGES
19.03.2007   10:33:08.000   1174318388   general   Old version: 3ae (942)
19.03.2007   10:33:08.000   1174318388   general   SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
19.03.2007   10:33:08.000   1174318388   internet   SYNCER: Type: use IE settings
19.03.2007   10:33:08.000   1174318388   internet   SYNCER: Auth: another authentication, use WinInet
19.03.2007   10:33:08.000   1174318388   package   Part prg_av_pro-3ae is installed
19.03.2007   10:33:08.000   1174318388   package   Part vps-72501 is installed
19.03.2007   10:33:08.000   1174318388   package   Part news-4b is installed
19.03.2007   10:33:08.000   1174318388   package   Part setup_av_pro-3ae is installed
19.03.2007   10:33:08.000   1174318388   general   Old version: 3ae (942)
19.03.2007   10:33:08.000   1174318388   file   SetExistingFilesBitmap: 937->145->145
19.03.2007   10:33:08.000   1174318388   general   GUID: c094c804-36f5-4c01-9bf1-f9f6e3f4f064
19.03.2007   10:33:08.000   1174318388   general   Entering:UpdateInstallPackages
19.03.2007   10:33:08.000   1174318388   package   Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
19.03.2007   10:33:08.000   1174318388   package   LatestPartInfo: news = news-4b
19.03.2007   10:33:08.000   1174318388   package   LatestPartInfo: program = prg_av_pro-3ae
19.03.2007   10:33:08.000   1174318388   package   LatestPartInfo: setup = setup_av_pro-3ae
19.03.2007   10:33:08.000   1174318388   package   LatestPartInfo: vps = vps-72501
19.03.2007   10:33:08.000   1174318388   package   FilterOutExistingFiles: 145 & 145 = 0
19.03.2007   10:33:08.000   1174318388   package   FilterOutExistingFiles: 145 & 145 = 0
19.03.2007   10:33:08.000   1174318388   package   ArePartsInstallable: 1
19.03.2007   10:33:11.000   1174318391   package   vps: updated [072501]
19.03.2007   10:33:11.000   1174318391   file   Fix security on: C:\Program Files\Alwil Software\Avast4\*.*
19.03.2007   10:33:11.000   1174318391   file   Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\*.*
19.03.2007   10:33:11.000   1174318391   file   Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HELP\*.*
19.03.2007   10:33:11.000   1174318391   file   Fix security on: C:\Program Files\Alwil Software\Avast4\ENGLISH\HtmlData\*.*
19.03.2007   10:33:11.000   1174318391   file   Fix security on: C:\Program Files\Alwil Software\Avast4\images\*.*
19.03.2007   10:33:11.000   1174318391   package   Transferred files: 0
19.03.2007   10:33:11.000   1174318391   package   Transferred bytes: 0
19.03.2007   10:33:11.000   1174318391   package   Transfer time: 0 ms
19.03.2007   10:33:11.000   1174318391   file   NeedReboot=false
19.03.2007   10:33:11.000   1174318391   general   Return code: 0x20000000 [Something done]
19.03.2007   10:33:11.000   1174318391   general   Stopped: 19.03.2007, 10:33:11


Title: Re: updates possible only on admin account why ??
Post by: kubecj on March 19, 2007, 07:57:42 PM
If the log is not written, it means that setup was not run at all. Is the failure logged somewhere?
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 08:02:44 PM
Sorry  - please see my modified post above.    Yes in Avast! Log Viewer

Code: [Select]
Function SetiFaceUpdatePackages()has failed. Return Code is 0x00000426,dwRes is 00000000.
Title: Re: updates possible only on admin account why ??
Post by: kubecj on March 19, 2007, 08:19:41 PM
We're now going in circles, as the 426 error code was reported and explained earlier in this thread  ;)

I asked my colleague to try to replicate the behaviour in our lab. It'll take day or two, I suppose. Stay tuned.

Title: Re: updates possible only on admin account why ??
Post by: bcool on March 19, 2007, 08:25:27 PM
Yes the error code was explained but I suspect that the explanation wasn't comprehensive enough. 
I only say this because none of what has already been mentioned here relating to 0426 seems to adequately address my situation.  On the other hand, we could add to the list that this error code indicates that a manual update request is being blocked. 
I can surely attest to that.  ;)

Anyway, thanks so much for your help.  It is much appreciated.
Title: Re: updates possible only on admin account why ??
Post by: bcool on March 27, 2007, 01:58:08 PM
Because Avast (HOME) works what appears to be flawlessly from a limited user account save for manual updating, I have to admit that uprooting the reason I can't update at will has loss urgency for me.  I still suspect when the smoke clears it will be revealed that this was by design all along.  Regardless, I'm content with Avast's faithful automatic updating from my limited user account.  I have no other complaints.  Thanks again.
Title: Re: updates possible only on admin account why ??
Post by: HA Nut on May 05, 2007, 10:36:03 PM
Curious...  :)

Has there been any news on this front from the avast! support team/programers? I gave avast! Home a trial last night/this morning and manual definition updates still do not work from a limited user account in XP.

From a PC safety standpoint, I feel that connecting to the web as a limited user is important and an antivirus should be able to update either automatically or manually (depending on specific situations.) In my case, I am on very slow dialup. I just cannot allow applications to run auto updates. If I did, I would never be able to do anything else when I'm connected...
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on May 05, 2007, 10:51:40 PM
I gave avast! Home a trial last night/this morning and manual definition updates still do not work from a limited user account in XP.
I've tested few minutes ago and have no problems into a limited user account.
Into the Administrator account, try to change the logon account for avast updates to administrator account.
In services control panel display properties of avast! iAVS4 Control Service, switch to LogOn page, and enter administrator account and password. Restart service to take effect on changes.
You can try setting avast! Antivirus service logon too.
Title: Re: updates possible only on admin account why ??
Post by: HA Nut on May 06, 2007, 04:21:01 AM
I made the changes to the 2 services you noted but no joy.  :'(  Still unable to update manually as a limited user (admin works fine as it has all along.)

Based on my tests, I'm thinking it must be a permissions issue with a folder and/or some file(s). If I change the limited account to an admin, it can manually update fine...
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on May 07, 2007, 01:06:47 AM
I'm thinking it must be a permissions issue with a folder and/or some file(s).
Did you install avast in the default folder?
If you follow...
1. Uninstall avast from Control Panel first.
2. Boot.
3. Use Avast Uninstall (http://www.avast.com/eng/avast-uninstall-utility.html) for complete uninstallation.
4. Boot.
5. Install again from the scratch, will it work?
Title: Re: updates possible only on admin account why ??
Post by: HA Nut on May 07, 2007, 04:03:45 AM
Quote
Did you install avast in the default folder?
If you follow...
1. Uninstall avast from Control Panel first.
2. Boot.
3. Use Avast Uninstall for complete uninstallation.
4. Boot.
5. Install again from the scratch, will it work?

The installation was the typical default setup. I made no customizations and installed the files to the regular, default folder.

I have installed the program 3 or 4 times. ??? After each trial, I reverted back to the drive image I had created prior to the installation.

I have not tried to do a second, clean install. I will try that and get back.

(FWIW, the AV, antispyware and antitrojan I have been using all update fine (both automatically and manually) under the limited user account.)
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on May 07, 2007, 08:37:23 PM
(FWIW, the AV, antispyware and antitrojan I have been using all update fine (both automatically and manually) under the limited user account.)
Which are these programs that you're using?
Title: Re: updates possible only on admin account why ??
Post by: sergofun on May 07, 2007, 10:59:34 PM
I'm thinking it must be a permissions issue with a folder and/or some file(s). If I change the limited account to an admin, it can manually update fine...
Hi! HA Nut, I think you are right. At admin account I've gave some permissions for limited account to "ALWILL Software" folder. Now I manually update avast! at limited account.
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on May 07, 2007, 11:02:58 PM
Hi! HA Nut, I think you are right. At admin account I've gave some permissions for limited account to "ALWILL Software" folder. Now I manually update avast! at limited account.
But take care, you've reduced the security level of that folder (and so, of avast in general).
Generally, it would be enough to correct this with a new installation.

If avast! is run from non-admin account, it does spawn the setup process using the service with LocalSystem rights. That brings you that it should update program without problem.
So, to sum it up: it should be possible to run whole program update from an limited user account, avast's setup was designed that way.
Title: Re: updates possible only on admin account why ??
Post by: HA Nut on May 08, 2007, 06:25:39 AM
Update...

The programs that I have been updating manually via my limited account have been SuperAntiSpyware, Comodo BOClean and NOD32. (They can update automatically but on my slow dialup, I need to control things better. Otherwise, the PC would be updating for 10 to 15 minutes (or more) the first boot/connection of each day.)

I spent a fair amount of time tonight testing 2 more avast installs (per your recommendations.) I also installed and tested another free competitor for manual updating under a limited account.

Neither the 1st or second install of avast would manually update via the limited account. I finally tried changing the security setting for the Setup folder (under Alwil\Avast4) to "Modify" for the limited account and it then ran ok. So it is something related to permissions. But as you noted, my feeling is that even though that works, it's not something one should be doing as a permanent solution.

FWIW, I also tested another free AV from a competitor. It was able to manually update via the limited account with no issues. (I didn't care for how it reacts with ZoneAlarm though. Always banging at the door, so to speak.)

Anyway, I'm kinda spent from all the tests. I'll probably sit things out for a while and test some later builds, which will hopefully work out better...  Thanks for the ideas! :)
Title: Re: updates possible only on admin account why ??
Post by: sergofun on May 08, 2007, 11:01:22 PM
Tech, thanks for explaining :)
Title: Re: updates possible only on admin account why ??
Post by: Lisandro on May 08, 2007, 11:29:55 PM
I finally tried changing the security setting for the Setup folder (under Alwil\Avast4) to "Modify" for the limited account and it then ran ok.
Uninstall avast, boot, use the uninstall tool, delete the avast folder if it remains there.
Boot and install again.
This way, installing from the scratch, the permissions will be set correctly.
Other way, you're lowering your computer security: a virus could destroy avast installation.

FWIW, I also tested another free AV from a competitor. It was able to manually update via the limited account with no issues. (I didn't care for how it reacts with ZoneAlarm though. Always banging at the door, so to speak.)
I'm absolutely sure that avast updates from a limited account IF it is correctly installed.
I have 3 computers running this way. All of them update through the limited accounts. XP SP2 by the way.