Author Topic: [Resolved] Failure to update due to "invalid file signature"  (Read 20456 times)

0 Members and 1 Guest are viewing this topic.

hzmonte

  • Guest
[Resolved] Failure to update due to "invalid file signature"
« on: October 05, 2010, 05:14:00 AM »
These several days the update of the virus definition has been unsuccessful, whether done automatically or manually.  The program reports "Last encountered error: Invalid file signature.  Setup will terminate."
I am running WinXP and avast Free AntiVirus.
On the About AVAST tab, it reports:
Program version: 5.0.677
Virus definition version: 100928-0
On the Update tab, it reports:
Current version: 100928-0
Release date: 9/28/2010 ...
Your virus definitions are out of date!  Latest virus definitions: 101004-1

By the way, I suggest Avast improve its terminology: it can be confusing as to what "current" and "latest" mean.  Obviously, "current" refers to the latest version on my computer, and "latest" refers to the version currently available from Avast.  But I guess someone may be confused.
« Last Edit: November 05, 2010, 08:06:12 PM by hzmonte »

SafeSurf

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #1 on: October 05, 2010, 07:39:28 AM »
Hello hzmonte and welcome to the forum.  :)

How do you connect to the Internet?  Broadband/DSL, proxy?  Have any of your settings been changed in the GUI for connecting to Avast?

Have you checked your firewall to see if Avast is being blocked?

Have you tried an Avast Repair:
- Go to Control Panel > Add/Remove programs > Avast Antivirus > Remove.
- Then choose Repair function in the pop-up window (Repair).  Reboot.

hzmonte

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #2 on: October 05, 2010, 08:14:55 PM »
I am using AT&T broadband.  I have not changed any setting.
I went to Control Panel and repaired Avast as suggested.  A message box popped up: "Error processing packages.  Please use full updates."
The only firewall I have been running is Windows Firewall. I have not changed any setting.  And when I looked at its setting for the first time, the Exceptions does not include Avast.  So I added Avast.
Then I repaired Avast again.  Same error.  The following is the log:
 
05.10.2010 11:09:47 general: Started: 05.10.2010, 11:09:47
05.10.2010 11:09:47 general: Running setup_ais-2a5 (677)
05.10.2010 11:09:47 system: Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
05.10.2010 11:09:47 system: Memory: 85% load. Phys:155760/1048048K free, Page:4194303/4194303K free, Virt:2066784/2097024K free
05.10.2010 11:09:47 system: Computer WinName: CA-TAR
05.10.2010 11:09:47 system: Windows Net User: CA-TAR\mkl
05.10.2010 11:09:47 general: Cmdline: /uninstwiz 
05.10.2010 11:09:47 general: Old version: 2a5 (677)
05.10.2010 11:09:47 registry: Deleted registry: Software\Alwil Software\Avast\5.0\UpdateReady
05.10.2010 11:09:47 system: Using temp: C:\DOCUME~1\mkl\LOCALS~1\Temp\_asw_aisI.tm~a02352 (10969M free)
05.10.2010 11:09:47 general: SGW32AIS::CheckIfInstalled set m_bAlreadyInstalled to 1
05.10.2010 11:09:47 general: DldSrc set to inet
05.10.2010 11:09:47 internet: SYNCER: Agent=Syncer/5.00 (ais-677;p)
05.10.2010 11:09:47 system: Computer DnsName: CA-TAR
05.10.2010 11:09:47 system: Computer Ip Addr: 192.168.1.65
05.10.2010 11:09:47 system: Installed in: E:\Program Files\Alwil Software\Avast5 (11M free)
05.10.2010 11:09:47 internet: SYNCER: Type: use IE settings
05.10.2010 11:09:47 internet: SYNCER: Auth: another authentication, use WinInet
05.10.2010 11:09:47 package: Part prg_ais-2a5 is installed
05.10.2010 11:09:47 package: IsInstalledPartVpuOkay: E:\Program Files\Alwil Software\Avast5\Setup\part-vps_win32-10100401.vpx does not exist
05.10.2010 11:09:47 package: Part vps_win32-10100500 was guessed as installed
05.10.2010 11:09:47 package: Part setup_ais-2a5 is installed
05.10.2010 11:09:47 package: Part jrog-a7 is installed
05.10.2010 11:09:47 package: IsInstalledPartVpuOkay: E:\Program Files\Alwil Software\Avast5\Setup\part-jrog2-4e.vpx does not exist
05.10.2010 11:09:47 package: Part jrog2-4f was guessed as installed
05.10.2010 11:09:47 general: LoadState: Edition=1
05.10.2010 11:09:47 general: Old version: 2a5 (677)
05.10.2010 11:09:48 file: SetExistingFilesBitmap: 479->90->90
05.10.2010 11:09:48 general: GUID: 0906ed82-d0f7-40d6-94ac-fe9fb53c9aa6
05.10.2010 11:09:48 general: Server definition(s) loaded for 'main': 373 (maintenance:0)
05.10.2010 11:09:48 general: SelectCurrent: selected server 'Download840 AVAST5 Server' from 'main'
05.10.2010 11:09:48 internet: SYNCER: Type: use IE settings
05.10.2010 11:09:48 internet: SYNCER: Auth: another authentication, use WinInet
05.10.2010 11:09:52 general: Operation set to INST_OP_REPAIR
05.10.2010 11:09:52 general: Entered SetupProcessAIS::Do( INST_OP_REPAIR )
05.10.2010 11:09:52 general: Entered SetupProcessWin32Avast::Do( INST_OP_REPAIR )
05.10.2010 11:09:52 general: Entered SetupProcessWin32::Do( INST_OP_REPAIR )
05.10.2010 11:09:52 general: Entered SetupProcess::Do( INST_OP_REPAIR )
05.10.2010 11:09:52 general: Entered SetupProcessAIS::Do( INST_OP_UPDATE_INSTALL_PACKAGES )
05.10.2010 11:09:52 general: Entered SetupProcessWin32Avast::Do( INST_OP_UPDATE_INSTALL_PACKAGES )
05.10.2010 11:09:52 general: Entering:UpdateInstallPackages
05.10.2010 11:09:52 general: progress thread start
05.10.2010 11:09:52 package: LoadProductVpu: E:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx
05.10.2010 11:09:52 package: LoadPartInfo: jrog = jrog-a7 returned 00000000
05.10.2010 11:09:52 package: LoadPartInfo: jrog2 = jrog2-4f returned 00000000
05.10.2010 11:09:52 package: LoadPartInfo: program = prg_ais-2a5 returned 00000000
05.10.2010 11:09:52 package: LoadPartInfo: setup = setup_ais-2a5 returned 00000000
05.10.2010 11:09:52 package: LoadPartInfo: vps = vps_win32-10100500 returned 00000000
05.10.2010 11:09:52 package: LoadProductVpu: E:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx ended with 00000000
05.10.2010 11:09:52 package: FilterOutExistingFiles: 90 & 90 = 0
05.10.2010 11:09:52 package: IsFullOkay: vps_32-2e3.vpx - not okay (doesn't exist)
05.10.2010 11:09:53 package: SetDownloadBits: vps_32 setting 14 diffs to process
05.10.2010 11:09:53 package: IsFullOkay: vps_win32-2f7.vpx - not okay (doesn't exist)
05.10.2010 11:09:53 package: SetDownloadBits: vps_win32 setting 14 diffs to process
05.10.2010 11:09:53 package: ArePartsInstallable: 0
05.10.2010 11:09:53 package: Error processing packages. 0x20000011

SafeSurf

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #3 on: October 06, 2010, 08:52:06 AM »
I suggest that you uninstall Avast and do a CLEAN install:

1. Save a copy of newest version of Avast (5.0.677) for the version you need and save it to your HDD:
Freehttp://files.avast.com/iavs5x/setup_av_free_eng.exe
2. Download the Avast Uninstall Utility, aswClear5.exe http://www.avast.com/uninstall-utility and save it to your HDD (put it on your desktop).  If you had a previous version of Avast on this machine, uninstall that version at this time as well.
3. Disconnect from the Internet at this time.
4. Boot into Safe Mode (hit F8 repeatedly) and run the Avast Uninstall Tool.
5. Reboot twice.
6. Install the newest version of Avast and reboot.
7. Get Internet access and update Avast definitions.
8. Register your copy or add the license key for Free:
    Free – http://www.avast.com/registration-free-antivirus.php
     
The XP Windows Firewall offers only one-way (very weak) protection.  You really should get a third-party firewall (FW).  Ones that do not conflict with Avast are Online Armor, Outpost, Comodo as a suggestion - all are free or paid; or you can upgrade to Avast AIS after you know your problems are resolved.

I also suggest that you update from SP2 to SP3 since there are many security holes in SP2, which is no longer supported by MS.

Let me know how this works for you.  Thank you.

hzmonte

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #4 on: October 06, 2010, 11:48:30 AM »
Well, as anyone can imagine, I really hate to re-instal a software, especially when it appears that the need to reinstal is due to a bug in that software.  I know I am taking a risk for not getting a updated virus definition but I really don't want to spend that time.  So, hopefully there would soon be enough people encounterng the same problem forcing Avast to do something and eliminating the need for the user to reinstal.  Thanks anyway.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67241
Re: Failure to update due to "invalid file signature"
« Reply #5 on: October 06, 2010, 01:32:21 PM »
@SafeSurf...

Boot into Safe Mode (hit F8 repeatedly) and run the Avast Uninstall Tool.
Safe mode is only necessary if the normal way fails.
Control Panel removing must be run before using the avast uninstall tool.

Reboot twice.
I think only once is necessary.

Get Internet access and update Avast definitions.
Register your copy or add the license key
It's better to register before updating (in some cases the trial period is expired).
The best things in life are free.

SafeSurf

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #6 on: October 06, 2010, 07:44:11 PM »
@ Tech,

The OP has an XP, which often requires 2 boots, and I have tested this on several machines.  This is not a problem with Vista or Win7.  As for uninstalling in Safe Mode first, I am instructing as other have been lately, however I will return to your method and will change my other instructions.  Thank you.

@ hzmonte ,

I hope you are not confused by the above comments, but the best way to fix your problem is to do the uninstall and install.  Should you wish to review the Avast knowledge articles to problem-solve, they are here: https://support.avast.com/index.php?_m=knowledgebase&_a=view&parentcategoryid=2&pcid=0&nav=0.  You are also welcome to contact Avast to open a ticket, however you will most likely get a quicker response here in the forum.  To contact Avast: http://www.avast.com/contacts.  Thank you.


Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67241
Re: Failure to update due to "invalid file signature"
« Reply #7 on: October 07, 2010, 12:03:14 AM »
The OP has an XP, which often requires 2 boots, and I have tested this on several machines.
Why? Why two boots?
The best things in life are free.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86670
  • No support PMs thanks
Re: Failure to update due to "invalid file signature"
« Reply #8 on: October 07, 2010, 12:30:45 AM »
When I have ever had to do a clean reinstall of avast I have 'never' rebooted twice, on my XP Pro SP3 systems.

This is a myth along the same lines as having to uninstall avast 4.8 before installing avast 5. Yes some people experienced a problem (for whatever reason) when installing avast 5 over 4.8, but the majority didn't. So my view was to install avast 5 over 4.8 as was the intended method from avast.

So there is no need to pre-empt problems that generally don't effect every user, no need to reboot twice.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.5.6015 (build 22.5.7263.730) UI 1.0.711/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

SafeSurf

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #9 on: October 07, 2010, 08:34:54 AM »
Back to the OP's problem...are either of you going to help him/her instead of writing about me?  A PM would have more appropriate especially when providing customer service.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67241
Re: Failure to update due to "invalid file signature"
« Reply #10 on: October 07, 2010, 01:17:56 PM »
Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair).
If this does not help, I suggest an installation from scratch:

1. Download the latest version of avast! Uninstall Utility and save it.
2. Download the latest avast! version and save it.
3. Uninstall avast from Control Panel (if possible). If, for any reason, you can't run it, try booting in Safe Mode and doing it from there. Anyway, boot after that.
4. Run the avast! Uninstall Utility saved on 1. If, for any reason, you can't run it, try booting in Safe Mode and doing it from there. Anyway, boot after you've run it.
5. Install avast! using the setup saved on 2. Boot.
6. Register your free copy or add the license key for Pro.
7. Check and post the results.
The best things in life are free.

hzmonte

  • Guest
Re: Failure to update due to "invalid file signature"
« Reply #11 on: November 05, 2010, 12:25:37 AM »
As I said, I hate to re-instal a software which appears to be buggy; so I have done nothing to it since last time I posted.  And yesterday it continued to try to do an automatic update and then reported a failure as it has since last month.  Well, about 10 minutes ago a pop-up box said that it completed an update successfully.  I did not do anything to the OS or the Avast software or any program or anything out of the ordinary.  So I guess the Avast people fixed that bug in its latest release.  Now, my Avast version is still 5.0.677 and the virus definition version is 101104-1.  My patience has paid off.
« Last Edit: November 05, 2010, 12:27:09 AM by hzmonte »

SafeSurf

  • Guest
[RESOLVED] Re: Failure to update due to "invalid file signature"
« Reply #12 on: November 05, 2010, 12:48:14 AM »
@ hzmonte,

Yes, there have been major updates recently which might have fixed your problem.

Now that your issue is resolved/fixed, please go back to the first open post in this topic, click the modify button in that Post and change the title/subject, add [Resolved] to the beginning of the title so this thread can be closed.  Thank you.  :)