Can you guys explain what "File system shield: improved on-close scanning" means?
Previously, the scanning of created/modified files was governed by the file's extension (there was a list of filename extensions). Now, all executable files are scanned, irrespective of their extension.
Why is this not in the Beta area of the forum ???
http://forum.avast.com/index.php?board=15.0
Has this area died ???
I'm about to take the plunge with the Beta ;)Just received an update.
I did notice that most (all??) Avast files are 6.0.1351 version.
Here's an [incomplete] list of the most important changes:Am I stupid? ??? I can't find more options in the UI. Could someone tell me what options are new? Or better post a screenshot?
...
- Web Shield and Script Shield: more options in the UI
Ups, i just found the new options. Sorry! ::)Here's an [incomplete] list of the most important changes:Am I stupid? ??? I can't find more options in the UI. Could someone tell me what options are new? Or better post a screenshot?
...
- Web Shield and Script Shield: more options in the UI
DJBone
Ups, i just found the new options. Sorry!Here's an [incomplete] list of the most important changes:Am I stupid? ??? I can't find more options in the UI. Could someone tell me what options are new? Or better post a screenshot?
...
- Web Shield and Script Shield: more options in the UI
DJBone
DJBone
Cold you please post a screenshot? :)Look at the attachements...
Cold you please post a screenshot? :)Look at the attachements...
DJBone
You're welcome :)Cold you please post a screenshot? :)Look at the attachements...
DJBone
Thank you very much, DJBone ;)
But Secunia files are not scanned. Some files could not be scanned: "Error: Password protected." This has not happened before the beta. (Outlook.pst often will not be scanned, but was this time.)
Just tested the autosandbox feature with the tool but Immunet 3 was faster than Avast and quarantined the autosandbox.exe file before the download was completed. ???Easly solved by getting rid of some of that security software listed in your signiture :o
does not work in version 6.0.1352 AutoSandbox :'(
Beta version installed fine. Licence date stayed as Friday last when I first downloaded Beta version (prior to reverting back to old version on Saturday).
Thank you.
Again do spell check on new Market UI page (comming??)
Thanks again for such a good AV program.
comming
A common misspelling of a word that seems so easy to spell that it hurts your brain when it's actually misspelled in this fashion. Even if you sounded out the word "coming" phonetically, to try and spell it, you would not get anything resembling "comming."
Can be found most often on internet message boards and "Comments" sections.
People's obsessions with improper spelling are comming to an apocalyptic climax.
All seems to be well.
But Secunia files are not scanned. Some files could not be scanned: "Error: Password protected." This has not happened before the beta. (Outlook.pst often will not be scanned, but was this time.)
I'm hoping detection will be improved with these newer versions.
True! ;DJust tested the autosandbox feature with the tool but Immunet 3 was faster than Avast and quarantined the autosandbox.exe file before the download was completed. ???Easly solved by getting rid of some of that security software listed in your signiture :o
I d a clean install of ais and I am on win 7 ultimate. in the non beta version I had right click and scan on files dirs etc. this beta version shows it in th elist but does not scan or do anything when selected.Context menu scanning is working for me.
I use this feature alot (till now).
I d a clean install of ais and I am on win 7 ultimate. in the non beta version I had right click and scan on files dirs etc. this beta version shows it in th elist but does not scan or do anything when selected.Context menu scanning is working for me.
I use this feature alot (till now).
I'm keeping Immunet 3 as a 2nd layer of protection. Disabling everything won't get this latest version of Avast Beta working for the autosandbox tool!!! :o So I gues not installing from scratch may be is the problem. Trying the sandbox browser now 8)True! ;DJust tested the autosandbox feature with the tool but Immunet 3 was faster than Avast and quarantined the autosandbox.exe file before the download was completed. ???Easly solved by getting rid of some of that security software listed in your signiture :o
Especially Immunet 3
I Cant't trigger autosandox.
<snip>
Are you using a desktop applications called Fences ?Why would it be related?
Can someone confirm he tested succesfully with the autosandboxme.exe file the autosandbox feature on v.1352 and how he installed it??? ???Getting...old! :D
I Cant't trigger autosandox. I have set it to ask but it dont work, like the foto. :
(http://)
so i tried install this version over Avast 4! install on Windows XP 32bit Sp3 machineWith such a large gap inbetween versions it is always recommended to do a clean install since avast 4 to avast 6 are like chalk and cheese.
result after reboot was BSOD on boot
(this BSOD does not wait to generate minidump, yet the OS can invoke minidump fine if i do it manually)
only solution to fix was remove C:\Windows\System32\Drivers\aswSnx.sys
then OS boots fine and Avast! seems work fine
the avast 4 was uninstalled correctly...
so i tried install this version over Avast 4! install on Windows XP 32bit Sp3 machine
the avast 4 was uninstalled correctly, the issue is un-related to avast 4....Now im confused as your first post stated - so i tried install this version over Avast 4! install on Windows XP 32bit Sp3 machine, so did you do a clean install or over the top ?
the avast 4 was uninstalled correctly, the issue is un-related to avast 4....Now im confused as your first post stated - so i tried install this version over Avast 4! install on Windows XP 32bit Sp3 machine, so did you do a clean install or over the top ?
@AdrianH,
Just for curiosity (and because I might have misunderstood), are you reporting about the current BETA version, or about the current stable?
@ AdrianH
Had you read the topic you would have seen this question was asked and answered. The landing page for the new monthly security report isn't complete, so essentially you are redirected to the main avast page.
This is one of the beauties of beta testing, some stuff won't quite be ready.
Spelling Error. Not sure what English is used but in North America it's "Coming" not "Comming". If another English is used perhaps having seperate English like English UK, English USA, English Canada
Just checked in the reliability monitor and noticed that iv got three warnings about windows not being shut down properly error 6008, this was a issue with 6.0.1289 on win7 64 bit systems but has returned in this beta as well, link to earlyer thread http://forum.avast.com/index.php?topic=86694.msg698615#msg698615
@AdrianH,The beta version, that's why I posted in this forum.
Just for curiosity (and because I might have misunderstood), are you reporting about the current BETA version, or about the current stable?
Jekku and craigb, is there something else in the Event Log? Or any minidumps in the \windows\minidump folder?Unfortunately iv cleared my logs but they were all the same as what were reported here by Tenseur http://forum.avast.com/index.php?topic=86694.msg699664#msg699664
Thanks
Vlk
Jekku and craigb, is there something else in the Event Log? Or any minidumps in the \windows\minidump folder?
Thanks
Vlk
This is beta version right? www.stahuj.cz posted it as new updated avast! version ???That is what the title say's :P why are you telling us ?
http://www.stahuj.centrum.cz/utility_a_ostatni/antiviry/kompletni/avast/ (Czech only)
stahuj.cz posted it as new stable version. But this is not stable version -_-This is beta version right? www.stahuj.cz posted it as new updated avast! version ???That is what the title say's :P why are you telling us ?
http://www.stahuj.centrum.cz/utility_a_ostatni/antiviry/kompletni/avast/ (Czech only)
Well you should go and tell them, we cant control what they post.stahuj.cz posted it as new stable version. But this is not stable version -_-This is beta version right? www.stahuj.cz posted it as new updated avast! version ???That is what the title say's :P why are you telling us ?
http://www.stahuj.centrum.cz/utility_a_ostatni/antiviry/kompletni/avast/ (Czech only)
Czech Avast users are redirected to that website from avast.comWell you should go and tell them, we cant control what they post.stahuj.cz posted it as new stable version. But this is not stable version -_-This is beta version right? www.stahuj.cz posted it as new updated avast! version ???That is what the title say's :P why are you telling us ?
http://www.stahuj.centrum.cz/utility_a_ostatni/antiviry/kompletni/avast/ (Czech only)
Thats why people should get there downloads from a reputable site.
Jekku and craigb,Done, thanks Vlk i'll keep an eye on it for the next couple of days.
could you please try adding the following mask:
last*.dat
to the File System Shield's exclusions, and see if it makes any difference?
Thanks
Vlk
Jekku and craigb,Done, thanks Vlk i'll keep an eye on it for the next couple of days.
could you please try adding the following mask:
last*.dat
to the File System Shield's exclusions, and see if it makes any difference?
Thanks
Vlk
Problem signature
Problem Event Name: APPCRASH
Application Name: avast.setup
Application Version: 5.0.0.0
Application Timestamp: 4ebea2fc
Fault Module Name: avast.setup
Fault Module Version: 5.0.0.0
Fault Module Timestamp: 4ebea2fc
Exception Code: c0000005
Exception Offset: 0008bac5
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Instead of adding more bells and whistles how about improving the slipping detection rates? For the last several months I've been watching them do downhill over at av-comparatives.org.
I only changed the log file size after the first crash but it was still set that way when i had the second crash which i sent to you, the other issue with windows not shutting down properly was there before and after changing the log size though.Problem signature
Problem Event Name: APPCRASH
Application Name: avast.setup
Application Version: 5.0.0.0
Application Timestamp: 4ebea2fc
Fault Module Name: avast.setup
Fault Module Version: 5.0.0.0
Fault Module Timestamp: 4ebea2fc
Exception Code: c0000005
Exception Offset: 0008bac5
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Am I right that you changed the maximum size of log files to 32KB?
If so, this is related to the problem.
Thanks
Vlk
I only changed the log file size after the first crash but it was still set that way when i had the second crash which i sent to you, the other issue with windows not shutting down properly was there before and after changing the log size though.
Iv now set the log size back to default.
Are you referring to the on-demand or "real-world" tests?
Instead of adding more bells and whistles how about improving the slipping detection rates? For the last several months I've been watching them do downhill over at av-comparatives.org.
Are you referring to the on-demand or "real-world" tests?
BTW we have quite high expectations of a big gun called "version 7".
Hopefully, it will change your perception little bit.
Thanks
Vlk
I'm still having the problem I mentioned earlier. Sometimes things like this happen and the next virus update resolves it. I was hoping that would happen with this but it hasn't thus far. I certainly don't want to exclude all those files (which is over 100).
"...Secunia files are not scanned. Some files could not be scanned: "Error: Password protected." This has not happened before the beta. (Outlook.pst often will not be scanned, but was this time.)"
Everything else seems to be going well.
Instead of adding more bells and whistles how about improving the slipping detection rates? For the last several months I've been watching them do downhill over at av-comparatives.org.
Are you referring to the on-demand or "real-world" tests?
BTW we have quite high expectations of a big gun called "version 7".
Hopefully, it will change your perception little bit.
Thanks
Vlk
Whole Product Dynamic Tests.
http://chart.av-comparatives.org/chart2.php (http://chart.av-comparatives.org/chart2.php)
Monthly avast! detection in this section has been going down. In Sept it was ranked 13th out of 17 programs and had been falling for months for some reason.
Having said that, I'm anxious for the new 7 when that comes out and am looking forward to renewing my subscription for another year.
My apologies if I missed this already being discussed a long the line, but my WebRep is not working in FF 8. Possibly I'm the only one. It works in Chrome (which I don't use).
It shows as being installed and I uninstalled and reinstalled the plugin but to no avail. It's not even listed as disabled in "Add ons."
When you updated to firefox 8.0 you should have had an add-on screen to allow you to enable third party add-ons such as the webrep, did you get that and check the option to allow webrep ?
My apologies if I missed this already being discussed a long the line, but my WebRep is not working in FF 8. Possibly I'm the only one. It works in Chrome (which I don't use).
It shows as being installed and I uninstalled and reinstalled the plugin but to no avail. It's not even listed as disabled in "Add ons."
I think that you still need to use the Firefox Add-On Compatibility Reporter to get WebRep to work with the latest release of Firefox. It is working fine on my Firefox 9.0B1 :)
<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id> <!-- firefox -->
<em:minVersion>3.0</em:minVersion>
<em:maxVersion>*</em:maxVersion>
</Description>
</em:targetApplication>
Instead of adding more bells and whistles how about improving the slipping detection rates? For the last several months I've been watching them do downhill over at av-comparatives.org.
Whole Product Dynamic Tests.
http://chart.av-comparatives.org/chart2.php (http://chart.av-comparatives.org/chart2.php)
Monthly avast! detection in this section has been going down. In Sept it was ranked 13th out of 17 programs and had been falling for months for some reason.
Having said that, I'm anxious for the new 7 when that comes out and am looking forward to renewing my subscription for another year.
Here is some information about the Whole Product Dynamic Tests conducted from Mar - June 2011
http://www.av-comparatives.org/images/stories/test/dyn/wpdt2011_1_en.pdf (http://www.av-comparatives.org/images/stories/test/dyn/wpdt2011_1_en.pdf)
1. Tests are performed under Windows XP SP3
2. Browser used is Internet Explorer 7
3. Adobe Flash Player ActiveX 10.0
4. Adobe Player Plug-In 10.1
5. Java 6.0.140
I sure hope that there current tests are using up to date software. I put no value in tests that use outdated software. Adobe Flash 11.x was released Oct 3rd
http://blogs.adobe.com/flashplayer/2011/10/adobe-flash-player-11-air-11-available-later-today.html
Java 7 was released July 28th
https://en.wikipedia.org/wiki/Java_version_history
XP3 is archaic and IE7 is junk
ISTM that people really need to understand how tests are performed and know all the software that is used in the test before talking about them. Now I don't know what software was used in their Sept tests so it is possible that they used W7 x64 along with Firefox or at least IE9 or the latest version of Chrome. However, the fact that their testing as late as last June was still using Windows XP3 and IE7 makes me very hesitant to accept any of their numbers.
I have posted before how AIS interacts with a bad URL differently when you access the URL using IE9 vs the current release of Firefox. I know this because I tested it on one of my computers and got different results.
JMO
Yes, I understand about the outdated software you mentioned, but all AVs were tested under the same old software and therefore it seems a "somewhat" fair comparison. Would not the up to date software simply point to them doing the work of catching virus' and the like, not the AV itself? I would think that updated software won't make any AV inherently better--only look better in tests because it didn't allow for a vulnerability to be exploited in the first place. Had the software been current it would have been a better test to be sure, but likely all AVs would simply have done better.
Maybe my thinking is all wrong here. I don't think such tests are the end-all, I just think they provide one additional piece of information to consider.
I'm not a tech person by any means, thus I like to be informed and learn from people who are and know more than me (which is a lot), in this and a few other forums.
When you updated to firefox 8.0 you should have had an add-on screen to allow you to enable third party add-ons such as the webrep, did you get that and check the option to allow webrep ?
I think that you still need to use the Firefox Add-On Compatibility Reporter to get WebRep to work with the latest release of Firefox. It is working fine on my Firefox 9.0B1 :)
My apologies if I missed this already being discussed a long the line, but my WebRep is not working in FF 8. Possibly I'm the only one. It works in Chrome (which I don't use).
It shows as being installed and I uninstalled and reinstalled the plugin but to no avail. It's not even listed as disabled in "Add ons."
I think that you still need to use the Firefox Add-On Compatibility Reporter to get WebRep to work with the latest release of Firefox. It is working fine on my Firefox 9.0B1 :)
WebRep works fine in Firefox 8.0 official release without any help or modification. It doesn't need another add-on to make it work. WebRep's install.rdf has had the lines below for the past few releases.Quote<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id> <!-- firefox -->
<em:minVersion>3.0</em:minVersion>
<em:maxVersion>*</em:maxVersion>
</Description>
</em:targetApplication>
Note that the maxVersion is a * wildcard.
@dagrev Yes, I understand about the outdated software you mentioned, but all AVs were tested under the same old software and therefore it seems a "somewhat" fair comparison. Would not the up to date software simply point to them doing the work of catching virus' and the like, not the AV itself
Quote@dagrev Yes, I understand about the outdated software you mentioned, but all AVs were tested under the same old software and therefore it seems a "somewhat" fair comparison. Would not the up to date software simply point to them doing the work of catching virus' and the like, not the AV itself
The reason I don't agree is because ISTM that you are assuming some things that I don't agree with.
1. That all software updates are equivalent when it comes to security.
2. That the Browser has no or very little impact with regard to Malware protection.
3. That the Operating System has no or little impact with regard to Malware protection
4. That all AV programs work just as efficiently with regard to Malware detection irrespective of what Browser, and Operating System you are using with the AV.
5. That Flash for IE is going to be just as secure as Flash for non-IE browsers.
6. That same for Java as with Flash
JMO
You could be correct about Firefox 8. I never used it. I went from Firefox 8B6 to Firefox 9B1. I have stopped using Firefox non-Beta releases. No need to use them. IMO
Vlk im still recieving the system was not shut down properly warnings, the only thing different iv noticed is that since placing the exclusion in file system shield is that i now dont get any extra information shown just the basic warning ( The previous system shutdown at 3:34:55 AM on 11/18/2011 was unexpected. )
Well yes it's only after a reboot but i dont think it has anything to do with the def updates, just when the action center updates itself after rebooting im finding.Vlk im still recieving the system was not shut down properly warnings, the only thing different iv noticed is that since placing the exclusion in file system shield is that i now dont get any extra information shown just the basic warning ( The previous system shutdown at 3:34:55 AM on 11/18/2011 was unexpected. )
craigb, can you confirm, that you'll get these shutdown warnings only when you shut down or reboot your computer after virus definitions update? And you will not get these warnings until the next definitions update? That's what I think is happening to me.
Well yes it's only after a reboot but i dont think it has anything to do with the def updates, just when the action center updates itself after rebooting im finding.Vlk im still recieving the system was not shut down properly warnings, the only thing different iv noticed is that since placing the exclusion in file system shield is that i now dont get any extra information shown just the basic warning ( The previous system shutdown at 3:34:55 AM on 11/18/2011 was unexpected. )
craigb, can you confirm, that you'll get these shutdown warnings only when you shut down or reboot your computer after virus definitions update? And you will not get these warnings until the next definitions update? That's what I think is happening to me.
Vlk im still recieving the system was not shut down properly warnings, the only thing different iv noticed is that since placing the exclusion in file system shield is that i now dont get any extra information shown just the basic warning ( The previous system shutdown at 3:34:55 AM on 11/18/2011 was unexpected. )
Nov 15th
23:40:44 nrm/int ERROR:HttpGetWininet, catch returned 0x00002EFD (12029)
Nov 16th
19:48:07 nrm/int ERROR:HttpGetWininet, catch returned 0x00002EFD (12029)
19:48:09 nrm/int ERROR:HttpGetWininet, catch returned 0x00002EE7 (12007)
Nov 18th
04:00:53 nrm/int ERROR:HttpGetWininet, catch returned 0x00002EFD (12029)
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Thanx for the welcome message on boot screen back! :)
Nothing to do with Avast, it's a windows problem, do you have Vista or 7? There is a different fix for each.
Oh! man
when is the official version coming????...waiting to see that boot screen message:
protected by avast! antivirus
nope...that feature is broken in 1289... :'(It worked fine in 1289 and also works in 1352 but I did not like it so I disabled it like DavidR
In that case, open this Microsoft KB article (http://support.microsoft.com/default.aspx?scid=kb;en-US;2545227), and click on the "Fix it" button.Nothing to do with Avast, it's a windows problem, do you have Vista or 7? There is a different fix for each.Win7
nope...that feature is broken in 1289... :'(
***
I think it has something to do with the def update process. I just compared my Windows event log and avast setup.log and got these results:
***
16.11.2011 12:30 PM avast update
16.11.2011 12:31 PM reboot --> ERROR
17.11.2011 12:15 PM avast update
17.11.2011 12:24 PM reboot --> ERROR
18.11.2011 05:03 AM avast update
18.11.2011 08:18 AM reboot --> ERROR
18.11.2011 08:21 AM reboot OK
18.11.2011 10:23 AM avast update
18.11.2011 12:51 AM reboot --> ERROR
18.11.2011 01:05 PM reboot OK
18.11.2011 01:24 PM reboot OK
18.11.2011 02.25 PM reboot OK
18.11.2011 02.50 PM reboot OK
18.11.2011 06.10 PM avast update
18.11.2011 07.50 PM reboot --> ERROR
18.11.2011 11.25 PM reboot OK
I get always that event log error 6008 during the next reboot after avast has updated itself. I don't get those errors at any other times when rebooting my computer.
Just forgotten: Thanx for the welcome message on boot screen back! :)
DJBone
i have question, is there way how force (setting in .ini) engine to do update on lower priority ?
***
I think it has something to do with the def update process. I just compared my Windows event log and avast setup.log and got these results:
***
16.11.2011 12:30 PM avast update
16.11.2011 12:31 PM reboot --> ERROR
17.11.2011 12:15 PM avast update
17.11.2011 12:24 PM reboot --> ERROR
18.11.2011 05:03 AM avast update
18.11.2011 08:18 AM reboot --> ERROR
18.11.2011 08:21 AM reboot OK
18.11.2011 10:23 AM avast update
18.11.2011 12:51 AM reboot --> ERROR
18.11.2011 01:05 PM reboot OK
18.11.2011 01:24 PM reboot OK
18.11.2011 02.25 PM reboot OK
18.11.2011 02.50 PM reboot OK
18.11.2011 06.10 PM avast update
18.11.2011 07.50 PM reboot --> ERROR
18.11.2011 11.25 PM reboot OK
I get always that event log error 6008 during the next reboot after avast has updated itself. I don't get those errors at any other times when rebooting my computer.
Comming back to that "system was not shut down properly warnings", I monitored my system for the last 24 hours and came exactly to the same findings and obviously to the same conclusion.
There must be some relations between avast! update and the "system was not shut down properly warnings".
i have question, is there way how force (setting in .ini) engine to do update on lower priority ?
No.
i have question, is there way how force (setting in .ini) engine to do update on lower priority ?
i seen several times avast updating with not nice cpu spike
then it would be nice to add this feature ... it's bit problem when you do something and get stutter and lag due avast updating on 'background'
I never had any issues when avast! updates.
Also this is OT here..!!
Quote from: AsynAlso this is OT here..!!
it's not OT as i never had such issue in past ... thus why i mention it in the beta thread ...
2. Show notification box after automatic update.I receive the pop ups on update on my systems. ;D ;D
However I have noticed that the notification box does not pop up when the automatic update has been received and I used to get the pop up box on my screen after every update, all three boxes are checked (ticked) 1. Ask for reboot when needed. 2. Show notification box after automatic update. 3 Show notification box if an error occurs, but I don't get ANY pop ups on my screen at all. :( :(The popups are working for me on this beta. No problems.
Now updated to build 1354.Trying now. Will test tomorrow.
Users of the previous beta can go to this build by simply invoking the in-product update feature.
Main changes include speed optimizations in the updater, little fix in the Web and Network Shields, and added localizations.
Thanks
Vlk
Appears AIS 1354 is useless.
Seems like the problem is related to IS only.Not for me.
Free AV is fine, everyone?
Appears AIS 1354 is useless.
Based on what?
I'm running it on this computer without any issues, for example.
It is a beta, things are being changed. issues are expected. That is the whole point of beta testing.
If you don't want to take part, then that is your decision.
Please send me the file <avast>\setup\components.ini (by email) and also say in that email which modules you don't see in the UI.
Thanks
Vlk
Seems like the problem is related to IS only.
Free AV is fine, everyone?
Please send me the file <avast>\setup\components.ini (by email) and also say in that email which modules you don't see in the UI.
Thanks
Vlk
I don't get paid enough
Please send me the file <avast>\setup\components.ini (by email) and also say in that email which modules you don't see in the UI.Done.
Thanks
Vlk
OK, I will for now remove the 6.0.1354 files from the download locations until the problem is resolved (tomorrow daytime).
DO NOT USE THIS LATEST RELEASE IT IS FLAWED!There may well be more issues with this Beta than we're used to, but what do mean by "LATEST RELEASE" is flawed?
Where exactly can you find an avast! Market inside GUI?You have to turn on the community features in settings to see the market tab in the UI RejZoR.
DO NOT USE THIS LATEST RELEASE IT IS FLAWED!
Installed 6.0.1354 no problems at all. Have Windows XP Home with Windows7 Firewall control. The only thing that I can criticise, is that Weprep in Internet Explorer give a whole toolbar to be able to show. Having an extra toolbar is not good on my NetBook, as I loose about 8mm from my page screen view.There was some discussion about this before. It has always been this way. Essentially, to make the icon changeable, so you can have different colours, it has to be on a toolbar.
Why can't Webrep be tucked away as it is on Google Chrome toolbar?
What's the point of having twitter and facebook nonsense enabled to see the avast! Market ? It makes no sense at all...
"avast! recommendations" should be turned into separate "avast! Market" checkbox...
New version(6.0.1354) installed itself without any problems via GUI. It seems to be working fine, although I can't access Real-time shields tab in GUI and stop real-time shields via tray icon.I noticed that I can not access the Real-time shields tab in GUI either on my Windows 7 system but I can stop real-time shields via tray icon though.
What's the point of having twitter and facebook nonsense enabled to see the avast! Market ? It makes no sense at all...
"avast! recommendations" should be turned into separate "avast! Market" checkbox...
Couldn't agree more, when that social network branding cr*p came out I hated it. As soon as options were there to remove it, it was history. So to put something totally unconnected under that heading doesn't make sense as I doubt I was alone in removing this twitter/facebook branding.
So for me the loss of the Market is a small price to pay (no pun intended) if it meant getting the twitter/facebook branding junk. So as RejZoR said this needs its own checkbox.
What's the point of having twitter and facebook nonsense enabled to see the avast! Market ? It makes no sense at all...
"avast! recommendations" should be turned into separate "avast! Market" checkbox...
DO NOT USE THIS LATEST RELEASE IT IS FLAWED!There may well be more issues with this Beta than we're used to, but what do mean by "LATEST RELEASE" is flawed?
DO NOT USE THIS LATEST RELEASE IT IS FLAWED!There may well be more issues with this Beta than we're used to, but what do mean by "LATEST RELEASE" is flawed?
I could not surf the Net with it.
won't update from program but still showing
After this update (1354), now my inernet connection is almost useless, I have to reload pages most of the time, because I keep losing connectivity.
After this update (1354), now my inernet connection is almost useless, I have to reload pages most of the time, because I keep losing connectivity.
+1
Win 7 64Bit
Greetings
Christian
I have still another problem. I can not open the Real Time Protection (Echttzeitschutz) Menu.
I have still another problem. I can not open the Real Time Protection (Echttzeitschutz) Menu.
Third problem: The Settings are on English instead of German. No language selectable.
At least I'm one of the few lucky ones without problems (even though I have IS).
If you read Vlk's first post of this topic you will notice that he mentions these betas are only available in english as of yet.Third problem: The Settings are on English instead of German. No language selectable.
Not only not selectable, languages setup gives no options too...
(http://i1111.photobucket.com/albums/h478/Paulius_Yla/avast%20screens/th_601354.jpg) (http://s1111.photobucket.com/albums/h478/Paulius_Yla/avast%20screens/?action=view¤t=601354.jpg)
I'd say the message was that the localizations were not updated before the first beta has been released, so the new UI items may still be in English...
I'd say the message was that the localizations were not updated before the first beta has been released, so the new UI items may still be in English - but it certainly shouldn't behave like that.Looks like i had to read more carefully ::), new UI items only in english ;D
Anyway, what's the point in publishing a file so flawed it lacks major features EVEN THOUGH BETA. It's a lack of respect, a minimal testing before release is required in AILWIL lab. Avast is showing a DOWNHILL trend I have never seen before. Even november http://www.av-comparatives.org/en/comparativesreviews/detection-test (http://www.av-comparatives.org/en/comparativesreviews/detection-test) posts bad results for Avast (AGAIN). Let's try at least to give STABLE Betas to the Avast Community! ;D :P
I agree and the fact that Avast would release to the public such a Beta makes me question if I will renew my license.
I agree and the fact that Avast would release to the public such a Beta makes me question if I will renew my license.
EDIT: Also noticed that I am seeing many more "The connection has been reset" messages in firefox recently...Click a link somewhere, and no loading is done, just get the message. Hit reload and it is fine...not sure of relevance, but worth noting.
Today it has been rather annoying. I would say that at least one in five clicks results in the connection reset page...
This seems to have begun (this bad) with these betas.
Am I the only one?
I agree and the fact that Avast would release to the public such a Beta makes me question if I will renew my license.
OMG. ::)
Don't use a beta then and stay on the stable builds...
The problem is, this update was sent out as a final build in my avast! U.I
The problem is, this update was sent out as a final build in my avast! U.I.,
The problem is, this update was sent out as a final build in my avast! U.I.
Am I the only one?
Am I the only one?
No, third time for me during this hour...
The beta has now been updated to build 6.0.1356.
BTW let me just say a few words about the dreaded 1354 update. This was probably one of the most interesting experiences we've ever had with a product update. The problem was related to this little item briefly mentioned in the revision history:
- speed optimizations in the updater
What this meant was that we rewrote a part of the updater which takes care of parsing of certain files in the avast SETUP folder. Now, the interesting part is that there was no problem with that code - it was implemented correctly, and thoroughly tested. However, there was a bug in a previous version of avast (probably all versions up to 6.0.1352) which caused one of the files to be malformed (under certain circumstances). The new optimized code didn't expect such a corrupted file though, and that resulted in the rather surprising symptoms many of you were experiencing - all sorts of erratic behavior.
This is also why the reaction to this build was somehow bipolar - either it was working perfectly fine (this was the case where the file had been OK) or it wasn't quite working at all (the case where the file had been corrupted).
The "fix" we implemented in v1356 allowed us to process both the valid and corrupted versions of the file.
Of course, let me apologize for any inconveniences this might have caused. This was a very interesting lesson for us - this was exactly the type of issue where external testing proved indispensable. However, this will hopefully allow us to also improve our internal QA process moving forward.
Thanks
Vlk
Updated to the very latest version, and everything is back to normal.
Just updated with NO problems so far. ;DUpdated to the very latest version, and everything is back to normal.
+1 I hope "Diagnose connection problems" will be gone too ;D
Thanks Vlk ;DJust updated with NO problems so far. ;DUpdated to the very latest version, and everything is back to normal.
+1 I hope "Diagnose connection problems" will be gone too ;D
The topic should be renamed to the latest beta 6.0.1356 :)
I will install it in my XP SP3 PC and see if it works fine..rm
However, what was weird was that that my Real-Time Shields personal perferences and Firewall personal preferences remained in tact from what they were on .1354 even though I uninstalled .1354 using "awsclear6.exe"
Since I had this "unexpected shut down error (6008)" with version .1352 everytimes a new def update came in I reverted to version .1289 again and it was OK.
Now I tried .1356 as an over thetop update.
The error is immediately back after the first def update! :o :o :o
Came back to .1289 and observing the system now. After the next update this evening I will report back!
Edit: First big def update of .1289 to current status folowed by a reboot did not show the 6008 error in the event viewer.
the stable release wont be out before thanksgiving will it? i dont want to miss out on the release because i going to be out of town for a few days.
No one other than avast knows that, but I guess they won't wait for you to get back if it is ;D
You will just have a nice surprise when you get back.
Than you have to call Vlk's wife. She knows everything about new releases at first hand ;)Specially when he does not come back home and stay working until late in the evening ;D
Web Shield and Script Shield: more options in the UI
Check the NEW 'Processes to exclude' option in the web shield, expert settings, Exclusions, scroll down to the bottom of the screen..
are the Ad for trying out Products still happening? in the free version like the in you face ad and the silder popup ads.
<snip>
oh okay thx ... missed that, that's related to the new webshield scope in Windows/programs, anything connecting through http.
Check the NEW 'Processes to exclude' option in the web shield, expert settings, Exclusions, scroll down to the bottom of the screen..Just remember that if you are using the outgoing filtering of the Windows Firewall, the rules will be bypassed by the Web Shield if you don't restrict it to browser processes only.
are the Ad for trying out Products still happening? in the free version like the in you face ad and the silder popup ads.
The IS trial offer was displayed exactly once for each user of the free version (I think that was in September). Since that, nothing.
I can't say it won't happen again, but given its frequency I don't think it's such a big deal. Or do you think otherwise?
Thanks
Vlk
In all the versions of Avast autosandbox has never workedSorry, can you post again what you're calling "never worked" exactly?
In all the versions of Avast autosandbox has never worked
...
In all the versions of Avast autosandbox has never workedSorry, can you post again what you're calling "never worked" exactly?
Nothing ever happens not a thingAnd why do you think it is not working then?
It looks like we're getting closer to the official release.Still getting the mysterious 6008 event. :(
The beta build has now been updated to version 6.0.1364.
This version should fix all the issues reported/discovered in build 1356 (with the exception of the mysterious 6008 event being written to the Windows Event Log during system shutdown).
Users of the previous beta can get this build by invoking the in-product update.
Thanks
Vlk
Downloaded setup_ais.exe of 6.0.1364 just now.
It does not detect my 6.0.1356 and does not have an upgrade (or update) option.
When I run it, it just acted as a brand new installation.
My system is Windows 7 Ultimate SP1 simple Chinese
How did you test if it is working ?
OK correction, it works on my system, but not on anything that is on my pc...so if I run autosandboxme.exe from a flash drive, I get the popup...(from what I can tell)
Free Version On-line Update from 1356.Same here. Updated from previous 1356. AutoSandbox is working like a charm. Everything OK. 8)
All OK inclusive Auto Sandbox (Red Border and no System modification)
My System: WIN 7 64 Bit
Nice Weekend
Christian
OK correction, it works on my system, but not on anything that is on my pc...so if I run autosandboxme.exe from a flash drive, I get the popup...(from what I can tell)
I'm slightly confused by your posts :)
So, which is it - the autosandbox popup doesn't appear at all, or it does but (after selecting to sandbox the application) it doesn't get sandboxed?
C:\Users\Scott\autosandboxme.exe | No AutoSandbox prompt, it just runs |
C:\Users\Scott\Desktop\autosandboxme.exe | No AutoSandbox prompt, it just runs |
F:\autosandboxme.exe | I get an autosandbox prompt (F:\ is a flash drive) |
After reading the above post I tried something similar. . . .
C:\Users\Bob\Downloads\autosandboxme.exe -> program just runs, i.e. no Autosandbox prompt nor red outline
C:\autosandboxme.exe -> program just runs, same as above
F:\autosandboxme.exe -> prompt from Autosandbox appears, and program has red outline when run as it should
Hopefully this helps identify where the problem might be . . . .
EDIT: same thing happens when using OTL.exe as the test file
No, I have a 64GB SSD as Systemdrive C and a 1.5TB Samsung as Drive D in my PC.As you are from Germany you may want to go to PROFILE then Modify Profile then Forum Profile Information then select your country in Please select your country: then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.
And the D: drive is a removable drive?
I also took the liberty of trying the same "experiment" on my D:\ partition (which is on the same physical drive as my C:\ partition). Autosandbox worked as it is supposed to. Looks like something is messing with the Autosandbox feature when run on files that are on my C:\ partition . . . .
Hi,
is it possible, that this is a problem with the rights restrictions at the system drive under Win 7?
Greetings
Christian
Does this have any problems on people's computers? if not, i'm going to install the beta ::)
The AutoSandbox is working fine for me on my Windows 7 system.
Hi,
is it possible, that this is a problem with the rights restrictions at the system drive under Win 7?
Greetings
Christian
Don't know. I can tell you that the Autosandbox feature was working fine up until I installed the beta. As far as I know, nothing else has changed on my system.
I have sent some additional information to the avast! team (requested by them) about this so hopefully they will be able to figure it out. It might, however, be fairly elusive since it appears that only some people are having the problem. We'll see . . . .
The AutoSandbox is working fine for me on my Windows 7 system.
The AutoSandbox is working fine for me on my Windows 7 system.
It's the autosandboxing feature itself that is not working - not the screen that allows you to choose its options and settings. ::)
For me, it works with internal drive D :) but not with systemdrive C :(Same here, autosandbox works on D drive but not on C drive. Both are on same disk.
Greetings
Christian
2011/11/27 1:20:35 Autosandbox candidate: C:\autosandboxme.exe
[Source: local://*C:\windows\explorer.exe ]
[Opened by: C:\windows\explorer.exe]
--> Result: Not sandboxing (because the file is trusted).
When will come the final version? :)As David pointed out, no one knows for sure. But there was a posting from Vlk in the last day or two that indicated they seem fairly happy with .1264, so we're probably getting pretty close, hopefully sometime next week.
1) Open the Avast main window and go to the tab with types of scans (screenshot 1)
2) Expand the field with scan from Windows Explorer ... this error occurs when you move the scrolling bar down, but if you move it up or expand the window so that the scroll bar has disappeared, error does not appear (screenshot 2)
3) Close the window
4) Re-open the window: the scrolling bar disappeared and the Quick scan field is hidden under the tab's title (screenshot 3)
5) Expand any other field and the scrolling bar returns (screenshot 4)
Thanks for the update. I like to know because avast there isn't add support to mozilla,seamonkey and google chrome portables of portableapps and the other question when will has a virtual keyboard like kaspersky.
sorry if dont understand.