Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on June 12, 2004, 10:53:52 AM

Title: PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 12, 2004, 10:53:52 AM
Hi,

there're about 10 new topics in the last 12 hours related to the very same thing: there's a bug in the latest version that has 2 implications (but is really the same problem):

1. the scan is taking forever
2. avast refuses to scan some files with 'Archive is corrupted' or 'Not enough TEMP disk space' values. You may also see file names in the form <pathname>\[AsPack].

Again, this is a confirmed bug in the latest release and will be addressed shortly.

Please don't start any new threads related to either of those two symptoms.

Thanks
Vlk


PS. I have removed the topics as they're all duplicate.
Title: Re:Please read: a bug in the current update (4.1.412)
Post by: RejZoR on June 12, 2004, 11:19:05 AM
Interesting,i did full disk scan yesterday and it finished as usual with no errors.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 12, 2004, 01:45:06 PM
Thanks Vlk and ReJzor!

Interesting, this seems to be one or the other I'm getting the corrupted files one as you know but scanning speed is fine.  I wonder why that is, surely if it's a software bug you'd expect it to be the same across the board?

Not criticizing you I know you're dealing with this, I'm just wondering why that might be.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 12, 2004, 02:32:06 PM
Yeah it's pretty strange. On most machines, it doesn't exhibit any problems. On some of them, it exhibits either the first or the second problem and some very unlucky people are experiencing both of the problems.. :)

Anyway, it is ONLY visible if archive scanning is turned on. This is because it's a bug (or rather not-really-stable code incidentally checked-in) in one of the unpackers.


Hope this helps,
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 12, 2004, 03:02:54 PM
Yes it does, thank you.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 12, 2004, 03:04:46 PM
Yeah it's pretty strange. On most machines, it doesn't exhibit any problems. On some of them, it exhibits either the first or the second problem and some very unlucky people are experiencing both of the problems.. :)

Anyway, it is ONLY visible if archive scanning is turned on. This is because it's a bug (or rather not-really-stable code incidentally checked-in) in one of the unpackers.


Hope this helps,
Vlk



Even with Archives turned off it scans as far as my Document/Settings / Avast 4 ... and then it freezes ....should I just sit back and wait for " Fix" or should I do something ....I have to do "Alt/Ctrl/Delete " in order to stop the Scan even ....Any idea as to when this might be fixed by ...Am I stll Protected without running a regular Scan ....Thanks ...(( Not very Computer wise here )))
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 12, 2004, 03:24:03 PM
Hmm, I'm not very glad to hear that... What do you mean exactly, "freezes"? Like it would never complete? Or just takes very long time? Can you leave it running?

Also, does it happen even if you do a Quick scan?


Thanks
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: SpeedyPC on June 12, 2004, 03:30:16 PM
Hmm, I'm not very glad to hear that... What do you mean exactly, "freezes"? Like it would never complete? Or just takes very long time? Can you leave it running?

Also, does it happen even if you do a Quick scan?


Thanks
Vlk

Quick scan is also having the same problem too Vlk when I checked after the full thorough scan.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 12, 2004, 04:14:56 PM
Hmm, I'm not very glad to hear that... What do you mean exactly, "freezes"? Like it would never complete? Or just takes very long time? Can you leave it running?

Also, does it happen even if you do a Quick scan?


Thanks
Vlk

Quick scan is also having the same problem too Vlk when I checked after the full thorough scan.


I meant it just stopped dead ...I left it alone and it did do a thorough scan but took over an hour ....at this moment I am doing a scan of my Files will post here and let you know as to whether it scans.... how long or just stopps dead ...will also try a quick scan ....have not included the Archives in any of the scans as yet but will and let you know that out come as well ....Thanks



P.S :::  Results from the Scans I did ::: Thorough" Local Disks" took an Hour without Archives checked.... Thorough "Folders" without Archives took 49 minutes .... Quick Scan with Archives checked took 15 minutes plus I got 417 Files not Scaned with the following [ASPAC ] behind all of them....Sure hope "" Bug "" is fixed soon ....

 :o  ;)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 12, 2004, 05:35:29 PM
That's not so bad is it? I mean how long did it take with version 396?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: SpeedyPC on June 12, 2004, 05:50:58 PM
That's not so bad is it? I mean how long did it take with version 396?

I say about 20mins on thorough and about 8mins on a normal scan as I remember
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: moses_x on June 12, 2004, 05:53:28 PM
Should we get concern about this bug ???? As mentined in a removed topic, it's possible a hotfix or we gone get a new version soon ????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 12, 2004, 06:11:41 PM
On an average it took about 45 minutes to do a Thorough Scan with Archives checked with  "Local Disks" and " Folders" checked as well ...  .This was before the update .

With the update it seems to be really sluggish through out the Scan ....and stopping for 5 to 8 minutes before scanning another file .
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 12, 2004, 07:53:50 PM
Should we get concern about this bug

I'd like to know that too please.  Or do we just scan as normal and ignore the Error 42052 and 42056?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 12, 2004, 08:37:00 PM
I suppose that the screensaver and the slidebar bug will also be fixed in the next build?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 12, 2004, 08:45:54 PM
No for extra fun we'll leave it there... :P :P

(just kiddin'...)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 12, 2004, 10:51:49 PM
No for extra fun we'll leave it there... :P :P

(just kiddin'...)


 ::)  Hmmm kidding are you ..... :P
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 12:56:20 AM
Alright, I've prepared an (yet-unofficial) update thath should solve the problems. I'd like to ask anyone who's been having problems w/ version 4.1.412 to try it out.

How to install it:
1. Download the file http://cat.asw.cz/beta-bart2/servers.def and place it to the <avast>\setup folder (overwrite the existing file) -- see comments below on how to download the file.
2. Invoke avast! program update (will require reboot).

That's about it.

Note that servers.def is a text file - so I recommend to right click the link and select "Save as". If you left click it, it may open in your browser as text (as a page). In that case, you can simply copy&paste it to the corresponding file, but the first method is definitely more convenient.


(Yes you figured it -- the procedure is exactly the same as was for the beta last week).


And please -- let me know how it goes.

Thanks
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 01:05:15 AM
Do you have a ETA for the official update? Or does it depend on how this update goes?
Thanks Vlk!
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 01:09:18 AM
Tomorrow if this unofficial patch does the trick...
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 01:11:44 AM
Cool! Just like the beta.  ;D
BTW, the beta wouldn't make my installation "dirty" right? (No reinstallation needed for the official tomorrow?)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 01:18:03 AM
No, it's just like an extra update. No extra stuff. :)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 01:22:39 AM
Better than ZoneAlarm 5.0 or Windows XP SP2 Betas.  :D
Should backup my server.def, should I?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 01:23:45 AM
You don't have to back it up, it's always available at http://www.avast.com/iavs4x/servers.def
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 01:26:41 AM
Alright Thanks... I will take a look at this beta then.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 01:47:10 AM
1. Screensaver Config Fixed
2. Screensaver Selection Missing From Screen Saver Task. (See Below)
3. Slidebar Problem Exists. (Tasks -> Resident Protection -> Script Blocking -> Set to normal.) (Double click Avast balloon -> Script Blocking -> Slider did not change to normal if it was at custom)
This is same for Standard Shield. Not really a big deal, but...  :)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 01:47:51 AM
4. Explorer Results tab don't apply?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: moses_x on June 13, 2004, 03:02:54 AM
Great Work !!!
Now i can scan with the options "Through Scan" with "scan archieves files" on without problems. All scan time taked 45 minutes.
Only one question: should i put back the old servers.def file, or in the next update this is will be automatic ?????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 03:17:13 AM
You should leave your server.def in place until the next official update is announced.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 13, 2004, 06:57:51 AM
HELPPPPP ...just read about the fix ...I am totally confused and scared now especially since i got a Virus today .....I am not the computer smart ......can you please explain in simple terms as to how to set the fix for the bug ????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 06:59:55 AM
Do you need help applying this beta update?
Or..?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 13, 2004, 07:05:40 AM
I also got this today not sure as to what to do other then i put it in the chest :::
>>:_CHEST_ANALYZE_:<<

Virus name: Win32:Zafi-B [Wrm]
Original file location: C:\DOCUME~1\ANNETT~1\LOCALS~1\Temp\_avast4_\unp2371363\Review.exe
Computer name: BARRETT
Transfer time: 12.06.2004 23:25:21
Modification time: 13.06.2004 04:25:22
Total size: 12800
Comment:

File ID: 4
Category: 1

OS:
Microsoft Windows XP Professional (Build 2600) Service Pack 1

are they going to release an update tomorrow that will be less complicated????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 13, 2004, 07:13:29 AM
It seems that Avast caught a file that it (Avast Quick Scanner) extracted from an archive on your computer. Unless the file is important to you, it is safe to delete this from your computer. (Check your archives and make sure you have this file repaired or cleaned.)

And hopefully they will complete the update tomorrow. It should be available to the public once it is released.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 13, 2004, 07:37:59 AM
It seems that Avast caught a file that it (Avast Quick Scanner) extracted from an archive on your computer. Unless the file is important to you, it is safe to delete this from your computer. (Check your archives and make sure you have this file repaired or cleaned.)

And hopefully they will complete the update tomorrow. It should be available to the public once it is released.
...........................................................................................................................................................................................
Sry but I have no idea as to what you are talking about ,,,that Virus warning came off of an e-mail I got through my OutLook Exress from some one I have no idea who it is ....all I want to do is to know how to get rid of it ...


As for the ""Fix "" I sure hope it is soon ....I have ran one scan of my "" Local Disks "" the scan froze but then it completed ....telling me it was clean ...trying to run a Scan of my "" Folders"" at the present time but the Scan has frozen ...hoping it will start up again soon ....
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 10:28:17 AM
Note that servers.def is a text file - so I recommend to right click the link and select "Save as". If you left click it, it may open in your browser as text (as a page). In that case, you can simply copy&paste it to the corresponding file, but the first method is definitely more convenient.

Sorry Vlk but this is not clear for those who have never followed this procedure before.  What do you mean "copy and paste it to the corresponding file"?

I looked in C:/Program Files/Alwil Software/Avast but there is no corresponding file there called servers.def, where do I look, which file do I open and once there is it a right click and open with Notepad again?

Running Windows XP Home Edition Service Pack 1.

I'm learning an awful lot from you people...
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 10:44:41 AM
Found it, it's in the Setup folder within Avast (if anyone else is wondering this).  Do you just add the new coding to the text file and if so where (at the beginning or at the end) or do you delete the text from it and copy and paste?  Or is there something specific you delete and replace?

I apologise if there's something obvious I'm missing, I'm not a programmer.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 12:21:25 PM
Quote
Found it, it's in the Setup folder within Avast (if anyone else is wondering this).  Do you just add the new coding to the text file and if so where (at the beginning or at the end) or do you delete the text from it and copy and paste?  Or is there something specific you delete and replace?

As I said, you either replace the file by using the Save As method (and confirm with Yes when asked by your browser if you want to overwrite the existing version), OR you replace the contents of the file -- i.e. delete its current contents (completely) and paste the new contents instead.

BTW I DID say that the file is in <avast>\setup, didn't I? ;)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 12:37:49 PM
BTW I DID say that the file is in <avast>\setup, didn't I?

Yes you did, sorry and thank you for clarifying, so you just replace the whole file :)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 01:06:59 PM
There's yet-another refresh at the beta location now (no need to download any new servers.def's if you've done that already -- just let avast do a program update).

Quote
2. Screensaver Selection Missing From Screen Saver Task. (See Below)

Should now be fixed.

Quote
3. Slidebar Problem Exists. (Tasks -> Resident Protection -> Script Blocking -> Set to normal.) (Double click Avast balloon -> Script Blocking -> Slider did not change to normal if it was at custom)
This is same for Standard Shield. Not really a big deal, but...


Well this can be caused by the fact that you "customized" it too much. I mean, the 'Set to High' and 'Set to Normal' buttons change only a couple of basic settings - not all of them. This is basically by design...

Quote
4. Explorer Results tab don't apply?


Also "fixed"now. (that was the same problem as with the Screen-Saver -- "special" tasks should be treated in a special way).


Thanks
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 02:10:12 PM
Sorry Vlk it isn't fixed, I'm still getting the same errors.  I cut and pasted the new servers.def file into the Avast/setup folder and told it to over-write the original as you instructed.

I'm attaching my log so you can see which files are affected for the next fix.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 02:12:33 PM
Try searching your hard drive for a file called aswEngin.dll . There should be only ONE occurence - in the avast folder. Are there any other copies on your hard drive?

Thanks
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 03:07:51 PM
Yes there was just one copy of this aswEngin.dll file and it was in the correct c:/Program Files/Alwil Software/Avast folder.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 03:26:24 PM
And it's got yesterday's timestamp?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 04:12:12 PM
Hope the screenshot has the info you want.

Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: S.Z.Craftec on June 13, 2004, 05:06:36 PM
EDIT:

Build 4.1.416 here and I still can not configure my screen saver... I don't know why is that happening...

Any thoughts ?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 13, 2004, 05:07:42 PM
Is there a simple update that we can do other then looking for certain files ????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 13, 2004, 07:37:12 PM
Pleaseeeee tell me how I can get the download for this Fix before I need to take off a Virus ...and run everything in Safe Mode .....What would happen if I uninstalled Avast then reinstalled it would that correct everything ......would I need to have a new Reg Key ?????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: S.Z.Craftec on June 13, 2004, 08:00:34 PM
Calm down Awake... no need to worry so much...

Here is Vlk's advice how to update avast!, just read it careful:

Quote
How to install it:
1. Download the file http://cat.asw.cz/beta-bart2/servers.def (http://cat.asw.cz/beta-bart2/servers.def) and place it to the <avast>\setup folder (overwrite the existing file) -- see comments below on how to download the file.
2. Invoke avast! program update (will require reboot).

That's about it.

Note that servers.def is a text file - so I recommend to right click the link and select "Save as". If you left click it, it may open in your browser as text (as a page). In that case, you can simply copy&paste it to the corresponding file, but the first method is definitely more convenient.

Just click with right mouse button on that link Vlk gave us, and select SAVE TARGET AS... Then save that file into c:/program files/Alwil sofwtare/avast4/setup subdirectory... of course, you have to overwrite existing file. After that, just manually invoke program update (go to sphere icon in system stray, right click it, and choose UPDATING and then PROGRAM UPDATE... and that's it... when updating is finished it will ask you to reboot... simple...

Cheers !
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: MikeBCda on June 13, 2004, 08:21:16 PM
Just a quick note, since I didn't see it mentioned anywhere here -- if you haven't already put the patch in, don't worry about it.  4.1.416 was already available as a "full" version by the time I got online today about 1:30 PM EDT.

I'd meant to post last night that (for me, at least) the patch seemed to work just fine for getting rid of what in effect were additions to the Exclusions list.  But that's history now, thanks team.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 08:26:10 PM
Yes I just downloaded the latest update the normal way and everything's fine now.  Thanks Vlk for all your help!
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: S.Z.Craftec on June 13, 2004, 08:34:45 PM
Well people, screen saver still has problems with configuring it... if you go with right click on your desktop and choose PROPERTIES, then SCREEN SAVER... choose avast acreen saver and press SETTINGS... nothing... nothing, at least in here... I can't configure that screen saver any more... what should I do Vlk ?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Gillie2tat on June 13, 2004, 08:40:05 PM
yes what I meant was that the Aspack and speed problem is resolved.  Now that you mention it, I select my screensaver exactly the same way as you do and it's doing much the same as yours- a black screen appears in the monitor preview of the Screensaver selector when I select the Avast screensaver and there's nothing to configure.

In addition because I have the Anfy software on my puter it's wanting to launch the Anfysave when I select it.  Maybe there's a conflict between the two.  All Anfy does is make Java applets using JPGs and GIFs and it does have a save as screensaver function which I have never used because I make screensavers through the My Pictures function in XP.  So why it's wanting to launch when I select the Avast screensaver I fail to understand.  It is listed in my screensavers though.

I didn't spot this earlier because I didn't know what was normal for Avast and what wasn't, but I'm getting to know how it works better now.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: S.Z.Craftec on June 13, 2004, 08:51:41 PM
Yeah, that's what I'm talking about... Don't worry Gillie2tat, Vlk will fix that too soon... I'm 100% sure.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: RejZoR on June 13, 2004, 08:51:59 PM
For me everything works fine (finally :) ) except Explorer Extension settings which i cannot save. Explorer Extension doesn't save itself,but it creates new task instead.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 09:46:53 PM
Build 416 is now in the release stream. It should have all known problems solved.

All beta users: please change the servers.def file to the original (release) one -- can be download from here: http://www.avast.com/iavs4x/servers.def . That's about it.


Thanks to everyone who helped to work on this issue. An amusing weekend I've got to say... :)

Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: RejZoR on June 13, 2004, 09:53:05 PM
Thanks,just updated :)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: RejZoR on June 13, 2004, 10:38:54 PM
Now this is what i call really damn fast :) Great job Alwil for this fix,now Explorer Extension is working again :D
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: moses_x on June 13, 2004, 10:58:00 PM
Thank you !!! I'm in love with this software ;D
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: cousindave on June 13, 2004, 11:25:19 PM
I must admit I am impressed with the speed with which these gliches get corrected and this forum in general. ;D
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: S.Z.Craftec on June 13, 2004, 11:46:18 PM
Welcome CousinDave, and stick around...

You'll see why these forums are the greatest...

Cheers !
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 13, 2004, 11:53:45 PM
:(

There's one more pretty serious bug in the latest build. It only affects non-English language versions of avast.

Symptoms: entering program Settings dialog crashes the program...  :-\

I guess we'll have to do a re-release. Sorry.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: moses_x on June 14, 2004, 12:00:31 AM
 ??? oh oh.....
Now i'm scannig the system, but i'll check it as soon as i finish the scanning.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: moses_x on June 14, 2004, 12:28:43 AM
Bug Confirmed  ???
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: MikeBCda on June 14, 2004, 03:04:24 AM
I got notified of (and installed) 418 sometime this afternoon.  At the rate the team's currently going, don't blink or you'll be a couple of builds behind.  ;)

A programmer's work is never done...
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 14, 2004, 03:28:03 AM
really a Great Bug ....Got a Major Virus sent from here ...spent all day removing it and finally had take Avast off as well .....Sry guys
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Tipton on June 14, 2004, 03:31:45 AM
I got notified of (and installed) 418 sometime this afternoon.  At the rate the team's currently going, don't blink or you'll be a couple of builds behind.  ;)

A programmer's work is never done...

Just got the update! Thanks......the avast support is awesome!

Douglas
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: dadkins_1 on June 14, 2004, 03:43:11 AM
Two program updates in one day? I love this company! ;D
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: softwareguy on June 14, 2004, 04:43:09 AM
If I am correct, build 418 is the re-released version?
Good Job Alwil!
Should we move on to 4.5? :P
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 14, 2004, 04:48:50 AM
i never got any notice oif any update all i got was a big big headache today from that worm that i was sent
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: .: Mac :. on June 14, 2004, 05:02:20 AM
Awake did you re install avast?
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: SpeedyPC on June 14, 2004, 05:57:29 AM
Vlk,

Is it safe to download the 418 version since I download the 412, and went back to 396 version until the bugs are fully fix?????

But the built version still say 4.1.416 inside the 4.1.418????
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 14, 2004, 09:47:08 AM
Awake from all you've said I'm pretty sure you are (and were) NOT infected by anything - it was just a file in a temp folder, really nothing to worry about.

SpeedyPC, you should be able to update to 418 from any previous version. But -- if you used any of the betas, please revert the servers.def to the original [release] version (can be download here: http://www.avast.com/iavs4x/servers.def ).


Thanks
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: MikeBCda on June 14, 2004, 07:03:31 PM
SpeedyPC, you should be able to update to 418 from any previous version. But -- if you used any of the betas, please revert the servers.def to the original [release] version (can be download here: http://www.avast.com/iavs4x/servers.def ).
Thanks
Vlk

Sorry if this was already covered earlier, Vlk, but if so I missed it.

I didn't get or play with the beta at any time -- but I did get and put in that patched version of servers.def you made available a few nights ago before the first of the current wave of version-upgrades.

Should I still go back and get the "standard" servers.def even though I never had the beta?  Updates seem to be working fine, although there's been an unusual flood of them.

Thanks and best,
Mike
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Vlk on June 14, 2004, 07:11:44 PM
You should revert to the original servers.def.
The one you have points to our internal testing distribution is unless you want to have 1-2 new program updates a day you need to replace the file.

In fact as soon as we're finished with the BART 2.0 beta testing I'll delete this beta directory from the server so you won't be able to update at all...

Thanks
Vlk
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 14, 2004, 07:27:14 PM
It was in my TEmp yes but it was sent from here and yes it was a Worm ...I went from 10.9 GB free on my hard drive to none after I was infected .......
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Tipton on June 14, 2004, 07:38:56 PM
It was in my TEmp yes but it was sent from here and yes it was a Worm

What do you mean it was sent from here? In what way were you infected from this site?

Douglas
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 14, 2004, 08:12:55 PM
The Virus was in an e-mail sent from Avast ...when I finally located the infected file it was _avast4_  ....
Virus name: Win32:Zafi-B [Wrm]
Original file location: C:\DOCUME~1\ANNETT~1\LOCALS~1\Temp\_avast4_\unp2371363\Review.exe
Computer name: BARRETT
Transfer time: 12.06.2004 23:25:21
Modification time: 13.06.2004 04:25:22
Total size: 12800
Comment:

Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: MikeBCda on June 14, 2004, 08:52:01 PM
You should revert to the original servers.def.
The one you have points to our internal testing distribution is unless you want to have 1-2 new program updates a day you need to replace the file.

In fact as soon as we're finished with the BART 2.0 beta testing I'll delete this beta directory from the server so you won't be able to update at all...

Thanks
Vlk

Done, Vlk, thanks.  :)  Interestingly, I rebooted and tried manual updating after that -- and it did succesfully "downgrade" a couple of sub-versions from what you say was probably a lab-only-version.  I forget what I started with, but it's now showing as 4.1.418.

The most interesting thing was, in the process it had to download and install from scratch (saved the original INI though, thank heavens), 2 megs plus.  I guess that's deliberate in case there's a major foul-up with one of the lab versions, easier to start over from a last-known-good point.

Thanks again, and best,
Mike
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: lava1 on June 14, 2004, 09:34:43 PM
Hi  For some reason I keep getting a email from this forum when people write in and I wish I could stop getting it to inform me that someone has written I deleted my question from here and I still get one telling me that someone else wrote in about it. How can I stop it.
 2nd question I did not get a email to inform me that was a new virus update was more important to let me know.  3rd  Now Iam worry and I did a thourgh check for virus because of "Awake" in what he said and it shows nothing 0  files not infected.   Please advise me what to do Thanks
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Awake on June 14, 2004, 10:12:27 PM
You should be ok ...I was sent an e-mail from Avast that contained something....when I clicked into my mail server it opened it before I knew it I got a pop up stating I was infected ....I Quaratined it but to ate up most f my free space on my drive ...finally gor rid of it and things returned normal on my drive
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: S.Z.Craftec on June 14, 2004, 10:20:54 PM
Hi  For some reason I keep getting a email from this forum when people write in and I wish I could stop getting it to inform me that someone has written I deleted my question from here and I still get one telling me that someone else wrote in about it. How can I stop it.
 2nd question I did not get a email to inform me that was a new virus update was more important to let me know.  3rd  Now Iam worry and I did a thourgh check for virus because of "Awake" in what he said and it shows nothing 0  files not infected.   Please advise me what to do Thanks

Hi LAVA1

1.) go to NOTIFICATIONS (right hand side from PROFILE option in this forum) and click it. From there you should be able to manage yourself...

2.) Same thing... go there and if you want to be informed about some important issues regarding avast!, just put checkmark under "Receive email notification when new Announcements"

3.) don't worry :)
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: Garythek on June 28, 2004, 06:45:39 PM
Will we be notified somehow when the bug is fixed? I have had both problems.
Title: Re:PLEASE READ: a bug in the current update (4.1.412)
Post by: igor on June 28, 2004, 06:53:04 PM
What particular bug do you mean? This is quite an old thread, and the bug for which this thread was created has been fixed "long" ago, in build 418.