Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

You have disabled my Kaspersky security. I WANT IT ENABLED. Please do it or tell me how to do it in language understandable to an Oxford science graduate, ie me

more options

Why have you done this ridiculous thing? You've put me in danger.

Why have you done this ridiculous thing? You've put me in danger.

All Replies (1)

more options

IMO, a pretty poor "security application" if it allows programs that don't have root privileges disable it.

I assume that you are referring to a Kaspersky add-on for Firefox, which was disabled during the Firefox 43 update. Firefox 43 has a new "signing" feature that doesn't allow unsigned extensions to be installed or be enabled in Firefox. A program that was announced all the way back in Feb 2015; and the enabling of which has been pushed-back from Firefox 40 to 43, due to lax response by too many 3rd party add-on developers, So now the "signing" queue is quite long.


There is a temporary override that each user can enable.

https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox#w_what-can-i-do-if-firefox-disables-an-installed-unsigned-add-on

Override add-on signing (advanced users): You can override this setting by changing the xpinstall.signatures.required preference to false in the Firefox Configuration Editor (about:config typed in the URL bar). Support is not available for any changes made with the Configuration Editor so please do this at your own risk.

Note: That pref will be gone in Firefox 44 (Release slated for Jan 26. 2016) so user's of currently un-signed extensions should contact the developers of those extensions and prod them into getting their act together & get their extensions signed by Mozilla. Otherwise the users of those extensions will be SOL come the release of Firefox 44. Mozilla has already pushed back the version in which this new security feature was to be enabled from Firefox 40 to 44. I doubt if there will be any further reprieve.