Hello When i updated to IE9 the script shield died. it hasn’t been scanning nothing as i surf the web. I did a repair that didn’t work. I did a reinstall of avast and that didn’t work… What is going on with it?
Is there any way i can make the Script Shield work again? ???
I noticed that also.
Script Shield is not working on Free Version.
Also that under real time shields log has no result.
Ex: File system, mail shield… etc.
Is the Shield log will only have a result if it detects something?
The script shield doesn’t work with IE9 RC it appears.
It is working overall though for non-browser scripts - try opening windows media player for instance.
Working fine for me and Windows Media Player is working fine as well.
Is the script shield activity shown in your snip from IE9 activity (under real time shields avast tells you what program ran the last script scanned)?
The only script shield activity I see is from non-browser scripts - such as those run by WMP.
Mine only shows some activity if i open media player, no activity with ie9.
Unfortunately there are no expert settings in the script shield so there is no way to access something like the Report generation settings and you could then have it record OK files (for troubleshooting as the file would get very large), etc. so you would see what it was scanning in the actual C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\report\ScriptShield.txt report file.
Currently it is as much use as a chocolate ashtray reporting only when it started and stopped, of course if it actually detected something I believe that would be recorded. But that doesn’t show if your browser is actually supported and scripts being scanned. On that note, you don’t say what your browser is ?
Unfortunately there are no expert settings in the script shield so there is no way to access something like the Report generation settings and you could then have it record OK files (for troubleshooting as the file would get very large), etc. so you would see what it was scanning in the actual C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\report\ScriptShield.txt report file.
Currently it is as much use as a chocolate ashtray reporting only when it started and stopped, of course if it actually detected something I believe that would be recorded. But that doesn’t show if your browser is actually supported and scripts being scanned. On that note, you don’t say what your browser is ?
If you look at the script shield in the GUI it tells you what program ran the last script scanned - see attached snip.
I was trying to establish whether Kenny has ever seen this program reported as being IE9.
I have never seen any script shield activity on my 64 bit system that I could attribute to any browser (FF, Chrome, or IE (32 bit or 64 bit). There is some script shield activity associated with other programs, such as WMP
The only browser I expected it to work for was IE 32 bit. Since it doesn’t I am trying to figure out if that is because I am running IE9 RC 32 bit rather than IE8 32 bit, or if in fact script shield just doesn’t run on any browser in 64 bit operating systems at present.
It is working overall though for non-browser scripts - try opening windows media player for instance.
I opened media player and the script shield worked for the first time for me. I use Firefox w/Noscript 100% of the time which is why I haven’t seen it do anything since I installed Avast 6. It doesn’t support Firefox from what I understand.
@ mag
Yes, but unless you always leave the avast UI open at that page and sit watching that last scanned file you don’t have a lot to check back on.
For the most part it will be scanning hard disk based scripts; since the script shield of old only monitored three browsers IE, Mozilla (not firefox) & Netscape; IE being the only one in popular current use. Though there are moves afoot to include Firefox and presumably Chrome in time.
That is why it would be nice to be able to check in a log rather than spend hours screen watching to see if it is monitoring your browser.
I was trying to establish whether Kenny has ever seen this program reported as being IE9.
That was IE9 on Windows 7.
This is with IE8 on my XP Pro system.