New *release* build of avast now available (5.0.677)

[Arizona]

Will sandbox work with MSN.

[Ruck3r]

I just updated  to avast! Free Antivirus version 5.0.677.

As soon as I updated and restarted my computer, I began to get the following error messages when using my mail program:

"avast! will not be able to protect mail/news (error 12)
Please check that avast! service (AvastSvc.exe) is not
blocked by your personal firewall."

and:

"avast! will not be able to protect mail/news (error 2)
Please check that avast! service (AvastSvc.exe) is not
blocked by your personal firewall."

System is Windows 7 professional 64-bit
Windows firewall - (I have made sure AvastSvc.exe and AvastUI.exe are permitted)
Mail program is Mozilla Thunderbird version 2.0.0.24

This worked without problems before the update.

What is the problem?

[Don_in_Vermont]

Avast stopped and found App Crash info listed below. Three seperate events.

9/9/2010 3:37 PM   Application Error   Faulting application name: AvastSvc.exe, version: 5.0.677.0, time stamp: 0x4c8651fd
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00010000
Faulting process id: 0x480
Faulting application start time: 0x01cb50160dc7cf3d
Faulting application path: C:\Program Files\Alwil Software\Avast5\AvastSvc.exe
Faulting module path: unknown
Report Id: 1c51467e-bc28-11df-93dd-0026189e970b

9/9/2010 3:37 PM   Windows Error Reporting   Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: AvastSvc.exe
P2: 5.0.677.0
P3: 4c8651fd
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: 00010000
P8: c0000005
P9: 00000008
P10: 

Attached files:
C:\Windows\Temp\WER2C12.tmp.appcompat.txt
C:\Windows\Temp\WER2C81.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER2C82.tmp.hdmp
C:\Windows\Temp\WER2D3E.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_AvastSvc.exe_3d65eda4da51e8a65af52bf94d4046963f1aaba3_cab_13e62da8

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1c51467e-bc28-11df-93dd-0026189e970b
Report Status: 0

9/9/2010 3:37 PM   Windows Error Reporting   Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: AvastSvc.exe
P2: 5.0.677.0
P3: 4c8651fd
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: 00010000
P8: c0000005
P9: 00000008
P10: 

Attached files:
C:\Windows\Temp\WER2C12.tmp.appcompat.txt
C:\Windows\Temp\WER2C81.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER2C82.tmp.hdmp
C:\Windows\Temp\WER2D3E.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_AvastSvc.exe_3d65eda4da51e8a65af52bf94d4046963f1aaba3_cab_13e62da8

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1c51467e-bc28-11df-93dd-0026189e970b
Report Status: 4

[Bucksnort]

What is taking over a damn year on 64 bit bootlog scanning??? Some of us paid for this thing!

[Hermite15]

What is taking over a damn year on 64 bit bootlog scanning??? Some of us paid for this thing!

you knew it wasn't there before buying didn't you? and if you read a bit more you would have known that bootscan on 64 bit OS won't be introduced before 5.1...that 5.1 will feature many new things...and that a year of development for all that is nothing special, that's normal

ps: oh, one last thing, the bootscan belongs to the "free" version of Avast 5

[gblu]

My guess is limiting its growth potential, restricting it to either a file size or number of days records retained. I believe it would be part of avast's internal housekeeping so no option required in the settings.

before program update, i noticed my setup log was about 20MB...and now, it's so small. less than 1 MB.

[=SKY=]

before program update, i noticed my setup log was about 20MB...and now, it's so small. less than 1 MB.

Wonderful, isn't it?!
They've really done a good job!

[DavidR]

before program update, i noticed my setup log was about 20MB...and now, it's so small. less than 1 MB.

Wonderful, isn't it?!
They've really done a good job!

Yes it will save me periodically disabling the self-defence module and deleting the two setup.log files.

One slight downside, the setup.log files are no longer in a user readable format, e.g. viewing in a text editor. So we won;t be able to ask a user to post the last 300 lines of the setup.log to see if we can find the reason for any errors they have/had.

Image1 - Editpad Lite
Image2 - Notepad

[spg SCOTT]

One slight downside, the setup.log files are no longer in a user readable format, e.g. viewing in a text editor. So we won;t be able to ask a user to post the last 300 lines of the setup.log to see if we can find the reason for any errors they have/had.

I can open them with notepad and see the text...

[igor]

David, could you please compress and upload the log to our FTP? I'd take a look at it...

[DavidR]

I don't know why, both setup.log files are the same for me in notepad virtually unreadable as a) I don't use word wrap and b) there doesn't appear to be any line breaks (return) in mine.

[=SKY=]

David, just for information:
I can read my setup.log without problems, too.

[DavidR]

David, could you please compress and upload the log to our FTP? I'd take a look at it...

OK Igor it should be up there as DavidR_Setup.7z a 7zip archive with the C:\Documents and Settings\All Users\Application Data\Alwil Software\Avast5\log\Setup.log file enclosed.

The compression ration for 7z was impressive only 28KB

[igor]

Strange... I somehow understand the problem, but the source seems to have been fixed on August 31st.
Did you have any of the (earlier) betas installed?

[Sgt.Schumann]

5.0.677 runs without any problems. Thanks for the new release