Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: JimTheMuso on December 04, 2005, 12:29:03 PM
-
Updated program last night and now updates don't work again. Red error panel and the log shows this error:
setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 00000006.
-
Is the "Avast iAVS4 Control Service" started?
Control Panel -> Administrative Tools -> Services.
-
Yes.
Also - just a bit more of the log (in case it helps)
setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 00000006.
03/12/2005 20:47:56 SYSTEM 1860 Function setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 00000006.
03/12/2005 20:47:56 SYSTEM 1860 An error has occured while attempting to update. Please check the logs.
04/12/2005 11:06:03 SYSTEM 1872 Function setifaceUpdatePackages() has failed. Return code is 0x00000426, dwRes is 00000006.
04/12/2005 11:06:06 SYSTEM 1872 An error has occured while attempting to update. Please check the logs.
-
It would be more helpful if you could please post the tail of the file <avast>\setup\setup.log
Thanks
Vlk
-
14:29:51 min/gen Stopped: 03.12.2005, 14:29:51
18:55:38 min/gen Started: 03.12.2005, 18:55:38
18:55:38 min/gen Running setup_av_pro-2db (731)
18:55:38 nrm/sys Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
18:55:38 vrb/sys Computer WinName: JIMSPC
18:55:38 min/sys Windows Net User: JIMSPC\Jim
18:55:38 min/gen Cmdline: /downloadpkgs /noreboot /silent /progress
18:55:38 vrb/gen DldSrc set to inet
18:55:38 vrb/gen Operation set to INST_OP_UPDATE_GET_PACKAGES
18:55:38 min/gen Old version: 2db (731)
18:55:38 nrm/gen SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
18:55:38 vrb/sys Computer DnsName: jimspc
18:55:38 vrb/sys Computer Ip Addr: 192.168.0.3
18:55:38 nrm/int SYNCER: Type: use IE settings
18:55:38 nrm/int SYNCER: Auth: another authentication, use WinInet
18:55:38 vrb/pkg Part prg_av_pro-2db is installed
18:55:38 vrb/pkg Part vps-54802 is installed
18:55:38 vrb/pkg Part news-44 is installed
18:55:38 vrb/pkg Part setup_av_pro-2db is installed
18:55:38 min/gen Old version: 2db (731)
18:55:41 vrb/fil SetExistingFilesBitmap: 728->136->136
18:55:41 min/gen GUID: 4d629b7b-6daf-4372-94bf-996a6982d00e
18:55:41 nrm/gen Server definition(s) loaded for 'main': 34 (maintenance:0)
18:55:41 nrm/gen SelectCurrent: selected server 'Download33 AVAST server' from 'main'
18:55:42 nrm/gen Server definition(s) loaded for 'main': 34 (maintenance:0)
18:55:42 nrm/gen SelectCurrent: selected server 'Download3 AVAST server' from 'main'
18:55:42 min/pkg Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
18:55:42 vrb/pkg LatestPartInfo: news = news-44
18:55:42 vrb/pkg LatestPartInfo: program = prg_av_pro-2e3
18:55:42 vrb/pkg LatestPartInfo: setup = setup_av_pro-2e3
18:55:42 vrb/pkg LatestPartInfo: vps = vps-54802
18:55:43 vrb/pkg Part prg_av_pro-2e3 was set to be installed
18:55:43 vrb/pkg Removed obsolete file part-prg_av_pro-2db.vpu
18:55:43 vrb/pkg Part setup_av_pro-2e3 was set to be installed
18:55:43 vrb/pkg Removed obsolete file part-setup_av_pro-2db.vpu
18:55:43 vrb/pkg IsFullOkay: setup_av_pro-2e3.vpu - not okay
18:55:43 nrm/gen Server definition(s) loaded for 'main': 34 (maintenance:0)
18:55:43 nrm/gen SelectCurrent: selected server 'Download30 AVAST server' from 'main'
18:55:43 min/pkg Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
18:55:43 vrb/pkg LatestPartInfo: news = news-44
18:55:43 vrb/pkg LatestPartInfo: program = prg_av_pro-2e3
18:55:43 vrb/pkg LatestPartInfo: setup = setup_av_pro-2e3
18:55:43 vrb/pkg LatestPartInfo: vps = vps-54802
18:55:43 vrb/pkg FilterOutExistingFiles: 136 & 136 = 0
18:55:43 vrb/pkg IsFullOkay: setif_av_pro-2e3.vpu - not okay
18:55:43 vrb/pkg IsFullOkay: setup_av_pro-2e3.vpu - not okay
18:55:43 vrb/pkg FilterOutExistingFiles: 136 & 136 = 0
18:55:43 vrb/pkg IsFullOkay: setif_av_pro-2e3.vpu - not okay
18:55:43 vrb/pkg IsFullOkay: setup_av_pro-2e3.vpu - not okay
18:55:44 nrm/pkg DldPackage: C:\Program Files\Alwil Software\Avast4\Setup\setif_av_pro-2e3-2db.vpu, returned 0x00000000
18:55:44 vrb/pkg Diff ok, created: setif_av_pro-2e3.vpu
18:55:45 nrm/pkg DldPackage: C:\Program Files\Alwil Software\Avast4\Setup\setup_av_pro-2e3-2db.vpu, returned 0x00000000
18:55:46 vrb/pkg Diff ok, created: setup_av_pro-2e3.vpu
18:55:46 min/gen setup: updated
18:55:46 min/gen setif: updated
18:55:46 nrm/pkg Transferred files: 10
18:55:46 nrm/pkg Transferred bytes: 96464
18:55:46 nrm/pkg Transfer time: 3374 ms
18:55:46 vrb/int Sending stats 'http://download30.avast.com/cgi-bin/iavs4stats.cgi': 00000000 204
18:55:46 vrb/fil NeedReboot=false
18:55:46 min/gen Return code: 0x20000010 [New setup available.]
18:55:46 min/gen Stopped: 03.12.2005, 18:55:46
-
Is this the last thing that's in the log?? This comes from the yesterday's program update.
BTW are you logged on as admin while invoking the update?
-
Yes... and yes.
I have to go out so will reply to anything else in about one hour. Thanks for help.
Jim
-
Did the yesterday's update complete successfully?
I'm still wondering what may be causing such strange problems on your machine...
What if you re-download the installation program and re-run it?
http://www.avast.com/eng/programs.html
Thanks
Vlk
-
Well I have just been out as I said during which time I closed the machine. On returning home I booted up again and got the same update error. There has already been some speculation in other threads that ProcessGuard may have something to do with these problems - even though many of them happened with PG disabled. Anyway, I have just disabled PG and, in Avast program settings, requested an update. It immediately reinstalled the updates and requested a reboot - which I did. I am now leaving PG disabled until the next automatic update to see what happens. This is the last part of the setup.log now.
The message is too long. Am emailing to you.
-
There has already been some speculation in other threads that ProcessGuard may have something to do with these problems - even though many of them happened with PG disabled.
PG, even disabled, seems to block or redirect things at low level... the user can't even know what is happening...
-
It's almost impossible for the ordinary user. This seems to have deteriorated (again) into Avast blaming PG and vice versa. Both programs are excellent and are highly regarded and highly rated but, if you are right, then the developers have not ensured they can work with one another. I (and many others I am sure) am spending more time trying to get my security programs working together than I am enjoying the use of my PC. It looks as though I am going to have to choose between the two programs then. Anyway, I will post your comments on the PG forum and see what their response is. I think we all know what they will say. If there was a program which does both jobs effectively I would happily pay good money for it.
-
I can't agree with you on this one, Jim. PG is a program whose goal is to interact with other programs. I don't want to publicly discuss the concrete PRINCIPAL problems I see on this program, but I can say that it is quite aggresive.
Avast updater, on the other hand, is a completely high-level, regular Windows application that downloads some stuff from the internet, and unpacks it. It does not, in any way, interact with PG (or any other program, with the exception of avast).
So it's quite clear which program is to blame in this case. You can call it "incompatiblity" (which is sort of neutral term) but the truth is, it's PG that is preventing the updater from working, and not vice versa...
Thanks
Vlk
-
OK point taken. I must admit what you say makes sense. Also, as you say in your email, let's see if anything is said on Wilder's. Just the same, speaking as a home end user, if it comes to make your mind up time, which is more important for me? A good antivirus or a good program which stops ANYTHING from running without permission? It would be nice to have both but I think Avast has to win - if only because it needs less intervention from me and specifically targets nasties. So, I suspect I will be unistalling Avast, then PG and then re-installing Avast - but I'll hold off a bit longer to see what happens. Thanks for your help.
-
Just for info: I have left PG in learning mode (I know this makes it more or less useless but it's just to see what happens for now), and on boot up this morning Avast updated the virus database automatically with no problem. I am going to put it (PG) into normal mode now and see what happens when the next auto update comes.
-
I'm having the same or a similiar problem with my Automatic updates. I don't know what Program Guard (PG) is tho. Can someone explain it please? Is it something I would have conciously installed?
A screen print of the error message is attached.
-
If you don't know what Process Guard is I doubt you have it installed, you would definitely know if you installed it.
What version of avast are you using, Home or Pro and version number 4.6.739 (latest), etc., is this a new install or was it working previously?
What is your firewall - does it allow avast.setup internet access?
-
BTW, manual updates work fine just the automatic updates are being blocked.
I am running Avast Home Edition v. 4.6.739 on a Win XP Pro machine. I have had this program installed for maybe a year and the updates have worked fine up to the last program upgrade.
-
I have had this program installed for maybe a year and the updates have worked fine up to the last program upgrade.
Perhaps the re-registration date (14 months) is coming up or possibly expired check in the about avast! although if that was the case then the Manual updates may not work either.
avast! 4 Home Registration (http://www.avast.com/i_kat_207.php?lang=ENG)
If things are still in date, try a repair of avast. Add Remove programs, select 'avast! Anti-Virus,' click the Change/Remove button and scroll down to Repair, click next and follow. You need to be on-line to do this.
If that doesn't work try, uninstall, reboot, install, reboot.
-
My registration is good thru 2/1/06 so that's not it. I will try the repair.
-
Ok, I repaired Avast. Now I'll have to wait till it tries an automatic update again before I will know. Wish there were a faster way to find out if the repair worked.
-
Speaking as a home end user...
A good program which stops ANYTHING from running without permission?
Problem comes when we, the home end users, have no idea of what is trying to run, is if it's legit or not, infected or not.
The programmers will do it for you with an antivirus.
Not trying to blame PG. I've used it for a while... but it brought me more problems and disapointments than help and security.
-
Nope, repairing didn't work. Got the same message when I signed on this morning and Avast tried it's auto update. When I uninstall/reinstall how will I avoid problems with re-registering my product?
I have to go to work but will answer any further posts when I get home tonight.
-
Next Step, download avast for Home again in full and save it on your HDD where you can find it again, uninstall, reboot, install the version you downloaded, reboot.
-
Gotchya on the next step but how do I avoid issues when I reinstall and re-register Avast? I don't want to wait until I get to that point to deal with these potential issues. Like for example... will I have any problems using my original product activation code?
-
Hello,
I had this same issue november 2004 and was helped on this forum.
See post (Mal76 november 30th 2004).
The Proccess Guard splash screen did not show long enough for me to allow the updated avast.
The only way I could overcome the problem was uninstall Proccess Guard
(disable not good enough) install avast update, reinstall process guard.
I do not use PG now as I had this problem at each avast programme update.
hope this helps,
regards Mal76.
-
Gotchya on the next step but how do I avoid issues when I reinstall and re-register Avast? I don't want to wait until I get to that point to deal with these potential issues. Like for example... will I have any problems using my original product activation code?
You don't have to wait, you can use the existing key or since you are relatively close (if the expiry date is 2 January 2006 or even 1 Feb) you could re-register now and have a new key sent to you by email. avast! 4 Home Registration (http://www.avast.com/i_kat_207.php?lang=ENG)
-
Ok, uninstalled / reinstalled and the first auto update worked fine. Crossing my fingers the problem is fixed!
Thank you for your help!
-
Your welcome, fingers crossed ;D