Am I correct in observing that script shield isn’t working with the latest Firefox release (17.0)?
That appears to be the case, which after a firefox update has happened before I believe. So it may be a little while to be resolved.
Just so I can learn, how do you check if it’s working or not? I just opened up Avast and it says the Script Shield is running… ??
Just open Real-Time Shields > Protection Status and look at the count. Also Script Shield tab and see how many files it has scanned. See image.
Yep same here, XP Pro SP3, Avast free 7.0.1474 and Firefox 17.0, no Script Shield activity at all.
Same here, Vista user. What is the recommended course of action? My script shield has never detected anything malicious on any of the sites I visit, and in addition I also use NoScript and Adblock to block a lot of scripts. So is it safe to continue using Firefox for now?
I had Firefox 17 yesterday but after reading the OP’s post I checked and noticed Script Shield wasn’t working so I uninstalled FF17. I had FF 16.0.2 saved in my downloads, installed it this morning so Script Shield is working now.
As I type this on firefox 17.0, I think that you may have answer to your question.
Lets not forget that you still have the network shield, web shield and up to a point some of the other shields may provide a different level of protection (it would depend what the script was attempting to do). So you should still be covered, the script shield adds that little something more. No doubt in due course it will support firefox 17.0, though there are other areas other than your browser where the script shield would be monitoring (like windows scripting host I believe).
As you say firefox with NoScript also provides protection in this area by not allowing scripts to be run by default, unless you specifically allow it for a site.
Firefox 17.0 is an important release because it’s an ESR version.
I recommend to use ESR versions of Firefox in all cases (home and all organizations). 8)
http://www.mozilla.org/en-US/firefox/organizations/all.html
Who is it for?
Firefox ESR is intended for groups who deploy and maintain the desktop environment in large organizations such as universities and other schools, county or city governments and businesses.
Who is it not for?
Individual users who always want the latest features, performance enhancements and technologies in their browser without waiting for them to become available in ESR several development cycles later.
@-midnight
Yes, I know, but that Mozilla’s statement doesn’t actually mean anything. ;D Use the ESR version of Firefox, if you want a stable and solid version. 
Since I know now what Frefox ESR is, I did Firefox 17 (ESR) the compliment of installing this highly sophisticated state of the art piece of equipment on my computer.
And — yes, script shield does not work with it’s Majesty.
@jrace
Script Shield will work with Firefox 17.0 after Avast has updated their software. Just wait a few days.
It’s working for me. Thanks iroc9555. 
Firefox is so sneaky. Each time I restart my computer it automatically updates to version 17, which I don’t want so I have to uninstall it, then go to my downloads folder and reinstall version 16.0.2.
Script shield uses exact pre-configured data to monitor FF 3.x up to 13.x, then it uses different method.
Now we found out, FF 16.x changed filtering algo a little bit (same as for FF 17.x I guess) so we’ll need to modify our code.
I tried XP SP2 + FF 16.0.2 and SS didn’t scan any FF script, can you confirm it?
I’ll try to release a patched version and post a link.
It’s working on FF 16.0.2.
Windows 7 SP1
Go to Options and click on Advanced, then Update. You can turn off Automatically Install Updates there. See screen shot below:
Nothing sneaky about it it is well known that it will auto update if you don’t tell it not to.
It didn’t use to auto update. I now have it set to where it has to ask before updating.
So much for asking to update. Just uninstalled a program which required my restarting my computer and once again FF updated to version 17. Going to have to do the uninstalling and reinstalling version 16.0.2. What a pain!