Appears to be working fine to me, but I’m on 7.0.1469beta but it was working fine in .1466 and I have some areas excluded forum.avast.com/* and static.avast.com//.js. This would further reduce its activity.
Could this be traced to vps updates? Which I doubt.
I have noticed seemingly constant issues with script shield with v7.0.xxx Well at least off and on.
Well, it could be possible Firefox auto updated and Avast doesn’t support it yet. You could open up Windows live messenger if you have it and log in and then the script shield should scan.
My thoughts would be if you had a problem before the update to the beta build that may well be carried forward to the beta. e.g. any setting which might impact on the script shield would be present in the beta update.
You could first try the avastUI, Settings, Maintenance, Settings Backup and export your existing settings. Then I would try restoring factory settings in the Settings, Troubleshooting.
Thanks guys! I rolled back to an earlier version of Chrome, FF and Pale Moon.
Script Shield now works in Firefox (1469 beta). But not in Chrome or PM. ???
Now Chrome 22.0.xxx Firefox 16.0.1 PM 15.0
edit: I’ve thought and tried all of the above suggestions before they were suggested. Just befuddled. ???