Author Topic: Problem with new update  (Read 1952 times)

0 Members and 1 Guest are viewing this topic.

x2397

  • Guest
Problem with new update
« on: March 08, 2012, 03:05:04 AM »
Hi all,

I updated to the new program and now avast seems to have gone crazy, when I attempt to full scan the # of files scanned jumps, from 100 to 2000 and back to 100, randomly, I am rounding numbers for simplicity.  I tried to update definitions to see if that was the problem but then there where 3000/2 or 5000/2 steps to the process but it ended quickly. Is there something wrong with the avast counter or is it the definitions? and is anyone else experiencing this?

program version: latest
definitions:120307-1
« Last Edit: March 08, 2012, 03:33:54 AM by x2397 »

Offline AntiVirusASeT

  • Poster
  • *
  • Posts: 462
Re: Problem with new update
« Reply #1 on: March 08, 2012, 04:50:22 AM »
sry not to doubt u, but is ur Avast! v7.0.1426?

also if possible please post a screenshot of the problem and ur system specs (eg. windows 7 32bit sp1, any other programmes which run on startup)

vb def is the same here: 120307-1

x2397

  • Guest
Re: Problem with new update
« Reply #2 on: March 08, 2012, 05:58:21 AM »
yep it is that version, I cant really get a screenshot since it appears to happen randomly, I have windows 7 64bit, what do you mean by programs on start up? the only things that pops up when I turn on my pc is messenger and def update.
I have had a similar issue on another computer and that was solved by a def update the next day, not sure if it is the case this time though.

Offline AntiVirusASeT

  • Poster
  • *
  • Posts: 462
Re: Problem with new update
« Reply #3 on: March 08, 2012, 06:29:03 AM »
to check what programmes u have on startup, follow the screenshot

note: u can search for cmd in windows 7. (this is the command prompt)

anyways does the full scans go into completion or it ends with errors?

« Last Edit: March 08, 2012, 06:32:12 AM by AntiVirusASeT »

x2397

  • Guest
Re: Problem with new update
« Reply #4 on: March 09, 2012, 02:55:16 PM »
After definition update yesterday it seems to be working fine, so it might have been the definitions. As aforementioned already had a similar problem before and just like last time, it leaves me scratching my head.