This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

Firefox has disabled Kaspersky and Logitech, how do I re-enable them?

  • 1 การตอบกลับ
  • 2 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย the-edmeister

more options

In Firefox Add-On it's telling me that both Kasperky Protection and Logitech Setpoint can not be verified for use in Firefox and have been disable. The info goes on about 'signing', but I cannot understand what it's telling me how how to re-enable Kaspersky and Logitech.

In Firefox Add-On it's telling me that both Kasperky Protection and Logitech Setpoint can not be verified for use in Firefox and have been disable. The info goes on about 'signing', but I cannot understand what it's telling me how how to re-enable Kaspersky and Logitech.

การตอบกลับทั้งหมด (1)

more options

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.