Author Topic: Database update bug - does not get past "161219-1)  (Read 7261 times)

0 Members and 1 Guest are viewing this topic.

Offline Lord_Ami

  • Sr. Member
  • ****
  • Posts: 227
Database update bug - does not get past "161219-1)
« on: December 27, 2016, 09:36:58 PM »
For over a week now, database is stuck with 161219-1. However, I can see that files are downloaded/updated. See picture.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89064
  • No support PMs thanks
Re: Database update bug - does not get past "161219-1)
« Reply #1 on: December 27, 2016, 09:48:26 PM »
This sort of out of sync issue (program says up to date but the display was wrong) used to be seen on occasion in avast. An avast repair usually sorted out this out of sync condition where the reported data didn't match the displayed data.

I don't know if the AVG beta has the avast repair function merged into the AVG settings.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #2 on: December 28, 2016, 04:02:05 PM »
It shows in the folder as 16121901, but the last modification date is 26th December. How is it on your PCs?

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89064
  • No support PMs thanks
Re: Database update bug - does not get past "161219-1)
« Reply #3 on: December 28, 2016, 04:23:03 PM »
Your imgur.com image is AWOL.

On any count mine shows 16122800 (today's current VPS and its associated stream 16122800_stream version both updates today.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #4 on: December 28, 2016, 04:24:56 PM »
Oops, attaching it here...  ;D


Offline Lord_Ami

  • Sr. Member
  • ****
  • Posts: 227
Re: Database update bug - does not get past "161219-1)
« Reply #5 on: December 28, 2016, 04:33:25 PM »
Just finished clean reinstall (haven't tried this beta on this particular PC yet)
https://snag.gy/VPNk7A.jpg

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89064
  • No support PMs thanks
Re: Database update bug - does not get past "161219-1)
« Reply #6 on: December 28, 2016, 05:42:54 PM »
This is certainly looking like a VPS update issue with this new AVG beta, my image was on this win10 notebook and the latest avast version. So no issues on the avast program VPS updates.

That said I still think you should try a Repair of your AVG beta installation if the AVG beta has the avast repair function ?
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #7 on: December 28, 2016, 05:46:51 PM »
That said I still think you should try a Repair of your AVG beta installation if the AVG beta has the avast repair function ?
There is a repair option. I'll repair it if i find free time today.  ;)

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #8 on: December 30, 2016, 07:06:33 PM »
I've tried the repair and it still stays at 161219-1. When check for updates it shows as downloading some files and then says: "Already up to date 161219-1". Let's hope for 170101-1.  :)

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #9 on: January 05, 2017, 02:54:23 PM »
Today the VPS was updated to 170105-0, but there is no number of the virus definitions in the About page, don't know if it's a bug or intended.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89064
  • No support PMs thanks
Re: Database update bug - does not get past "161219-1)
« Reply #10 on: January 05, 2017, 03:03:25 PM »
Quote from:  link=topic=194680.msg1357752#msg1357752 date=1483624463
Today the VPS was updated to 170105-0, but there is no number of the virus definitions in the About page, don't know if it's a bug or intended.

You don't say what avast version you are using, latest regular release is 12.3.2280.

On my about avast shows the number of definitions as 6,033,664.

Personally I'm not concerned with the numbers more on the protection. Avast is regularly optimising the virus signatures to capture more than just a single malware variant, so it is pretty hard to say how many variants would be caught.
« Last Edit: December 14, 2021, 11:23:16 AM by Eva137 »
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #11 on: January 05, 2017, 03:05:17 PM »
Quote from:  link=topic=194680.msg1357752#msg1357752 date=1483624463
Today the VPS was updated to 170105-0, but there is no number of the virus definitions in the About page, don't know if it's a bug or intended.
You don't say what avast version you are using, latest regular release is 12.3.2280.
Hmm, this is the... AVG beta forum here.  ;) :D
« Last Edit: December 13, 2021, 03:44:22 PM by Eva137 »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89064
  • No support PMs thanks
Re: Database update bug - does not get past "161219-1)
« Reply #12 on: January 05, 2017, 03:34:19 PM »
Oops
Then I think that you have to expect some niggles like this when trying to implement avast style updates and info into the AVG beta. But it is certainly right to report it.

My second point is still valid I think, that number is meaningless (even when displayed) other than our database is bigger than yours database.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline A. User

  • Sr. Member
  • ****
  • Posts: 388
Re: Database update bug - does not get past "161219-1)
« Reply #13 on: January 05, 2017, 03:46:53 PM »
Oops
Then I think that you have to expect some niggles like this when trying to implement avast style updates and info into the AVG beta. But it is certainly right to report it.
Especially when they are working on the unification of the definitions.  :) What i as thinking is that this period of not receiving new definitions only streaming ones was because of a "good work behind the scene".

My second point is still valid I think, that number is meaningless (even when displayed) other than our database is bigger than yours database.
It really depends on how generic and complex the definitions are. Norton has around 25 million and Comodo some millions more, but you can't really say that the signatures are Comodo's strength.  ;D However i would like to see what will be the change after the integration of the AVG's definitions and now i don't know if this has happened or not.  ::)