Author Topic: updates possible only on admin account why ??  (Read 15276 times)

0 Members and 1 Guest are viewing this topic.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: updates possible only on admin account why ??
« Reply #15 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...
The best things in life are free.

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #16 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 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.  :)


Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: updates possible only on admin account why ??
« Reply #17 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.
The best things in life are free.

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #18 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.)

« Last Edit: March 19, 2007, 04:54:59 PM by bcool »

Offline kubecj

  • Avast team
  • Advanced Poster
  • *
  • Posts: 1123
    • ALWIL Software
Re: updates possible only on admin account why ??
« Reply #19 on: March 19, 2007, 04:49:22 PM »
Is the avast update service running?
Jindrich Kubec

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #20 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?
« Last Edit: March 19, 2007, 05:12:57 PM by bcool »

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: updates possible only on admin account why ??
« Reply #21 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
The best things in life are free.

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #22 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
« Last Edit: March 19, 2007, 09:52:09 PM by bcool »

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: updates possible only on admin account why ??
« Reply #23 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...
The best things in life are free.

Offline kubecj

  • Avast team
  • Advanced Poster
  • *
  • Posts: 1123
    • ALWIL Software
Re: updates possible only on admin account why ??
« Reply #24 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.
Jindrich Kubec

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #25 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.
« Last Edit: March 19, 2007, 08:01:19 PM by bcool »

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #26 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


« Last Edit: March 19, 2007, 09:57:01 PM by bcool »

Offline kubecj

  • Avast team
  • Advanced Poster
  • *
  • Posts: 1123
    • ALWIL Software
Re: updates possible only on admin account why ??
« Reply #27 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?
Jindrich Kubec

Offline bcool

  • Jr. Member
  • **
  • Posts: 33
  • No sweat!
Re: updates possible only on admin account why ??
« Reply #28 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.

Offline kubecj

  • Avast team
  • Advanced Poster
  • *
  • Posts: 1123
    • ALWIL Software
Re: updates possible only on admin account why ??
« Reply #29 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.

Jindrich Kubec