Received warning re. McAfee ScriptScan 14.4.1 extension won't work with FF 10.0.2 update, and will be disabled. How should I proceed?
MY system is Windows XP, SP3, laptop, running FF 9.0.1. When trying to update to FF 10.0.2 I got a msg that the McAfee ScriptScan 14.4.1 addon won't work with FF 10.0.2 and will be disabled. Shall I go ahead and install the FF update? Would it be a security risk either way? Which one is worse?
Solution eye eponami
Hi,
A thread on the McAfee forum refers to this and those who replied about this issue with FF10 said it actually works, see https://community.mcafee.com/message/226187
Hope this helps, Michelle
Tanga eyano oyo ndenge esengeli 👍 1All Replies (4)
Solution eye oponami
Hi,
A thread on the McAfee forum refers to this and those who replied about this issue with FF10 said it actually works, see https://community.mcafee.com/message/226187
Hope this helps, Michelle
I don't know what ScriptScanner does, but I think it's always a good idea to update Firefox to eliminate known vulnerabilities, particularly if it's your main browser. You can see what security problem were fixed in Firefox 10.0.2 (and earlier versions) on this page: https://www.mozilla.org/security/known-vulnerabilities/firefox.html
According to the end of this long forum thread, there's a good chance it will still work (based on experience with the previous release): McAfee Communities: McAfee ScriptScan for Firefox 14.4.0.
However, it has been reported that the McAfee add-ons can cause Firefox to use much more memory. If you notice a performance slow-down, consider disabling them. More info: The McAfee Site Advisor add-on has an appalling memory leak | Nicholas Nethercote.
Hope this helps.
However mcafee launched a newer version of plugin which fixed memory leak issue
Michelle, jscher, and Swarnava
I went ahead and installed the update, and indeed ScriptScan 14.4.1 did not get disabled. (Site Advisor also still works.) Don't know about the remaining memory leak issues. I'll consider that another problem to be solved by Mozilla, in time.
All three answers were helpful in resolving my issue. I just happened to clicked michelle's first. Thanks to all of you!
-nipohc
Ezalaki modifié