Author Topic: invalid file signature  (Read 94475 times)

0 Members and 1 Guest are viewing this topic.

iroc9555

  • Guest
Re: invalid file signature
« Reply #120 on: October 04, 2012, 04:32:39 AM »
@iroc9555:  nah, not an isolated issue, you're not alone -- same thing happened here (and others).

I didn't mean the "I can't update Avast!" deal. I know it is a problem Avast! is working on. I meant if you, or any one, had already 121003-2 and Avast! by itself downloaded the whole VPS, and now is saying it is not updated. You need to repaired Avast! to go back to 121003-1 that it is the correct VPS. There are members who still have VPS 121003-2 shown as correct and without problems.

bknabe

  • Guest
Re: invalid file signature
« Reply #121 on: October 04, 2012, 05:05:26 AM »
Mine no longers throws up the invalid signature message, but now it says it is up to date, but with the same def file. Bummer.

I've uninstalled and reinstalled and it still give the "invalid file signature" error when trying to update. I'm beginning to think it's the definition file.

OhMyGod

  • Guest
Re: invalid file signature
« Reply #122 on: October 04, 2012, 05:17:31 AM »
I'm shocked that Avast hasn't made any kind of a statement to let us know what is going on.

Thanks. :)

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67203
Re: invalid file signature
« Reply #123 on: October 04, 2012, 05:30:36 AM »
In the middle of the night? Well... not all of us are in the workable hours of the day :)
The best things in life are free.

KinightOfLight

  • Guest
Re: invalid file signature
« Reply #124 on: October 04, 2012, 07:37:23 AM »
It is now some hours later after this first issue, around 7 hours later and I have still the 121003-1 VPS.

When I did manually update, because the regular update did work, I had 121003-2 VPS. To manually  update I did use: http://www.avast.com/download-update

Than the update worked again and this happend:



Avast updated a older VPS than the manually  update has.

Since them not one new VPS update.
« Last Edit: October 04, 2012, 07:51:59 AM by KnightOfLight »

OhMyGod

  • Guest
Re: invalid file signature
« Reply #125 on: October 04, 2012, 07:50:14 AM »
In the middle of the night? Well... not all of us are in the workable hours of the day :)

According to their contact details they have global offices in USA, Austria and Germany as well as their head quarters in Czech Republic.
Someone should be awake. http://www.avast.com/contacts

Thanks. :)

KinightOfLight

  • Guest
Re: invalid file signature
« Reply #126 on: October 04, 2012, 07:54:19 AM »
In the middle of the night? Well... not all of us are in the workable hours of the day :)

According to their contact details they have global offices in USA, Austria and Germany as well as their head quarters in Czech Republic.
Someone should be awake. http://www.avast.com/contacts

Thanks. :)

German, Austria office should open around 08:00GMT+1 or 08:30GMT+1 or maybe 9:00GMT+1 / I do not work there, so I do not know.

KinightOfLight

  • Guest
Re: invalid file signature
« Reply #127 on: October 04, 2012, 10:45:34 AM »
Any news yet from Avast? I'm still at VPS 121003-1 for 10 hours now, the other Anti-Vir Programms did already update the VPS !!!   >:(

true indian

  • Guest
Re: invalid file signature
« Reply #128 on: October 04, 2012, 10:52:17 AM »
Any news yet from Avast? I'm still at VPS 121003-1 for 10 hours now, the other Anti-Vir Programms did already update the VPS !!!   >:(

faulty updates have removed from the servers...the New VPS will release probably by next 1 to 2 hours...protection is still the same...just tested against some brand new malware..and still very damn good as it always has been  ;D

Simple solution to fix the update problems will be to go ahead and re-install avast!

true indian

  • Guest
Re: invalid file signature
« Reply #129 on: October 04, 2012, 11:00:43 AM »
That does not work. Next Idea? >:(

Try doing the manual update stuff in safe mode without networking followed by a repair...and that should fix it.

Duncan9999

  • Guest
Re: invalid file signature
« Reply #130 on: October 04, 2012, 12:32:28 PM »
That does not work. Next Idea? >:(

Try doing the manual update stuff in safe mode without networking followed by a repair...and that should fix it.

How do you get into safe mode?

true indian

  • Guest

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 87667
  • No support PMs thanks
Re: invalid file signature
« Reply #132 on: October 04, 2012, 01:35:33 PM »
As I said in another topic about this:
Quote
I think that they have pulled the VPS 121003-2 version so the update check doesn't fail as it did before.

That is why it is showing 121003-1 as the latest update when you try an update check. This gives them time to find the reason for the problem in the bad VPS update without the problem 'for users' spreading as people update. So those who managed to get round the problem of the bad VPS they will still see version 121003-2 as their current version.

So I would expect an update later today version 121004-0 to be released, that should fully resolve the VPS version number mismatch. But having pulled the bad VPS version from the update servers, the system should be working.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.4.6062 (build 23.4.8118.762) UI 1.0.762/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

MatteoB

  • Guest
Re: invalid file signature
« Reply #133 on: October 04, 2012, 02:59:13 PM »
Thanks David that clears up a lot of confusion. I have the -1 now showing as the lastest update and fully updated. Let's hope this is just a glitch as I was spending ages trying to fix it last night. Sorry for rant: was tired and frustrated.

gblu

  • Guest
Re: invalid file signature
« Reply #134 on: October 04, 2012, 03:06:24 PM »
i have version 121003-1, and my avast says it's updated version (not outdated anymore). i tried to manual update ( i was curious), and i got this ( see the attachment). and no 'invalid file signature' anymore



 well, i think version 121003-2 was a bad update, so they pulled it back. (but the funny thing is, i never had version -2, but my avast said my previous version was 121003-2).
« Last Edit: October 04, 2012, 03:11:24 PM by gblu »